<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agentic-Coding | Bas Nijholt</title><link>https://www.nijho.lt/tag/agentic-coding/</link><atom:link href="https://www.nijho.lt/tag/agentic-coding/index.xml" rel="self" type="application/rss+xml"/><description>Agentic-Coding</description><generator>Hugo</generator><language>en-us</language><copyright>© 2026</copyright><lastBuildDate>Sun, 11 Oct 2026 00:00:00 +0000</lastBuildDate><image><url>https://www.nijho.lt/media/icon_hu_408a8f6cef43e327.png</url><title>Agentic-Coding</title><link>https://www.nijho.lt/tag/agentic-coding/</link></image><item><title>Giving models the tools they were trained with can make them worse</title><link>https://www.nijho.lt/post/native-harness-tools/</link><pubDate>Sun, 11 Oct 2026 00:00:00 +0000</pubDate><guid isPermaLink="false">/post/native-harness-tools/</guid><description>&lt;p&gt;A few nights ago, lying in bed, I had what felt like a galaxy-brain idea.&#10;I dictated it into my watch so I would still remember it in the morning.&lt;/p&gt;&#10;&lt;p&gt;Every frontier model learns to solve coding tasks with tools through reinforcement learning (RL), and I assume that training happens inside its vendor&amp;rsquo;s own coding agent: Anthropic&amp;rsquo;s models in Claude Code, and OpenAI&amp;rsquo;s models in Codex.&#10;That is a big assumption, since the labs do not publish their training environments, but it makes business sense: they sell those agents, so they have every reason to make their models work best in them.&#10;Every other harness, like &lt;a href="https://github.com/badlogic/pi-mono" target="_blank" rel="noopener"&gt;pi&lt;/a&gt;, &lt;a href="https://opencode.ai/" target="_blank" rel="noopener"&gt;opencode&lt;/a&gt;, or my own &lt;a href="https://www.nijho.lt/post/mindroom/"&gt;MindRoom&lt;/a&gt;, gives the model a set of tools of its own design for running commands and editing files.&#10;The models are usually smart enough to figure those out, but not always.&#10;Sometimes a model assumes an edit tool works like the one it was trained with, and uses it wrong.&#10;This summer, that happened to Claude Opus 4.8 in pi, which I come back to &lt;a href="#why-i-believed-it"&gt;below&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;So the idea was simple: in MindRoom, give each model the same shell and file-editing tools as its native harness, and switch them automatically depending on which model is answering.&#10;Claude would see Claude Code&amp;rsquo;s &lt;code&gt;Bash&lt;/code&gt;, &lt;code&gt;Read&lt;/code&gt;, &lt;code&gt;Edit&lt;/code&gt;, and &lt;code&gt;Write&lt;/code&gt;.&#10;GPT would see Codex&amp;rsquo;s &lt;code&gt;exec_command&lt;/code&gt; and &lt;code&gt;apply_patch&lt;/code&gt;.&#10;And because the smallest agents do surprisingly well, I would go one step further: a minimal agent whose only tool is the shell each model knows from its training.&lt;/p&gt;&#10;&lt;p&gt;I was beyond excited.&#10;I could not really share that excitement locally, because my wife did not care, so I am sharing it with the internet instead.&lt;/p&gt;&#10;&lt;p&gt;Then I measured it against MindRoom&amp;rsquo;s own tools, and the familiar ones did not make the models more efficient.&#10;With only Codex&amp;rsquo;s tools, GPT-6 Astra did 84% more work, taking more steps and reading and writing more along the way, and used 59% more tokens.&#10;With Claude Code&amp;rsquo;s tools, Claude Sonnet 5.5 did 15% more work, and Claude only came out a few tokens cheaper because the descriptions I wrote for those tools are slightly shorter than MindRoom&amp;rsquo;s.&#10;Only one model clearly worked more efficiently with its own tools: Claude Opus 4.8, the model from the pi story.&#10;The models seem to generalize beyond the environment they were trained in, and what still matters is how much the agent sends with every request.&lt;/p&gt;&#10;&lt;aside class="callout callout-note"&gt;&lt;svg class="ico" viewBox="0 0 256 256" aria-hidden="true"&gt;&lt;path d="M128,24A104,104,0,1,0,232,128,104.11,104.11,0,0,0,128,24Zm0,192a88,88,0,1,1,88-88A88.1,88.1,0,0,1,128,216Zm16-40a8,8,0,0,1-8,8,16,16,0,0,1-16-16V128a8,8,0,0,1,0-16,16,16,0,0,1,16,16v40A8,8,0,0,1,144,176ZM112,84a12,12,0,1,1,12,12A12,12,0,0,1,112,84Z"/&gt;&lt;/svg&gt;&lt;div&gt;&lt;p&gt;&lt;strong&gt;What I found&lt;/strong&gt;&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Compared with MindRoom&amp;rsquo;s own tools, the familiar ones did not make the models more efficient: with only Codex&amp;rsquo;s tools, GPT-6 Astra and Sol did 60 to 84% more work and used 43 to 59% more tokens.&lt;/li&gt;&#10;&lt;li&gt;With Claude Code&amp;rsquo;s tools, Claude Sonnet 5.5 did 15% more work and Opus 5.5 about the same; they only came out a few tokens cheaper because the descriptions I wrote for those tools are shorter than MindRoom&amp;rsquo;s.&lt;/li&gt;&#10;&lt;li&gt;Only Claude Opus 4.8, the model whose edits kept failing in pi, clearly worked more efficiently with its own tools.&lt;/li&gt;&#10;&lt;li&gt;What matters is how much the agent sends with every request: a minimal agent with one shell tool and a 12-line prompt used 58 to 76% fewer tokens than the same agent in standard mode on these short tasks.&lt;/li&gt;&#10;&lt;li&gt;Giving that minimal agent each model&amp;rsquo;s own shell tool did not make it better.&lt;/li&gt;&#10;&lt;/ul&gt;&lt;/div&gt;&lt;/aside&gt;&#10;&lt;details class="toc" open&gt;&lt;summary&gt;Table of contents&lt;/summary&gt;&lt;nav id="TableOfContents"&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#what-a-harness-is"&gt;What a harness is&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#why-i-believed-it"&gt;Why I believed it&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#smaller-agents-do-better"&gt;Smaller agents do better&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#models-should-know-their-own-tools-best"&gt;Models should know their own tools best&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#what-i-built"&gt;What I built&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#how-i-measured-it"&gt;How I measured it&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#native-tools-dont-make-todays-models-more-efficient"&gt;Native tools don&amp;rsquo;t make today&amp;rsquo;s models more efficient&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#older-models-only-opus-48-did-better-with-them"&gt;Older models: only Opus 4.8 did better with them&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#what-does-matter-what-the-agent-sends"&gt;What does matter: what the agent sends&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#fewer-tools"&gt;Fewer tools&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#minimal-mode-one-shell-tool-and-a-12-line-prompt"&gt;Minimal mode: one shell tool and a 12-line prompt&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#minimal-mode-with-each-models-native-shell-tool"&gt;Minimal mode with each model&amp;rsquo;s native shell tool&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#what-this-does-and-does-not-show"&gt;What this does and does not show&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#what-happens-to-the-pull-request"&gt;What happens to the pull request&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#why-this-excites-me"&gt;Why this excites me&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#appendix-how-i-measured-and-the-numbers-behind-the-charts"&gt;Appendix: how I measured, and the numbers behind the charts&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10;&lt;/nav&gt;&lt;/details&gt;&#10;&#10;&lt;h2 id="what-a-harness-is"&gt;What a harness is &lt;a class="anchor" href="#what-a-harness-is" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;&amp;ldquo;Harness&amp;rdquo; gets thrown around a lot, but there is no magic in it.&#10;Every coding agent talks to the model the same way: each request contains a system prompt, the definition of every tool the model may call, and the conversation so far.&#10;When the model answers with a tool call, the harness runs the tool, adds the result to the conversation, and sends everything again.&lt;/p&gt;&#10;&lt;figure class="harness-diagram" style="max-width: 460px; margin: 2rem auto;"&gt;&#10;&lt;svg viewBox="0 0 380 470" role="img" aria-label="One request holds the system prompt, the tool definitions, and the conversation so far. The model answers with a tool call, the harness runs it, adds the result to the conversation, and sends the whole request again." style="width: 100%; height: auto; font-family: system-ui, sans-serif;"&gt;&#10;&lt;defs&gt;&lt;marker id="harness-arrow" viewBox="0 0 8 8" refX="7" refY="4" markerWidth="7" markerHeight="7" orient="auto-start-reverse"&gt;&lt;path d="M0,0 L8,4 L0,8 z" fill="currentColor"/&gt;&lt;/marker&gt;&lt;/defs&gt;&#10;&lt;rect x="10" y="10" width="250" height="210" rx="10" fill="none" stroke="currentColor" stroke-opacity="0.45"/&gt;&#10;&lt;text x="22" y="32" font-size="14" font-weight="700" fill="currentColor"&gt;One request to the model&lt;/text&gt;&#10;&lt;rect x="22" y="44" width="226" height="48" rx="6" fill="#97bbf5" fill-opacity="0.45"/&gt;&#10;&lt;text x="34" y="64" font-size="13" font-weight="600" fill="currentColor"&gt;System prompt&lt;/text&gt;&#10;&lt;text x="34" y="81" font-size="11" fill="currentColor" fill-opacity="0.8"&gt;who the agent is, how it should work&lt;/text&gt;&#10;&lt;rect x="22" y="100" width="226" height="48" rx="6" fill="#97bbf5" fill-opacity="0.45"/&gt;&#10;&lt;text x="34" y="120" font-size="13" font-weight="600" fill="currentColor"&gt;Tool definitions&lt;/text&gt;&#10;&lt;text x="34" y="137" font-size="11" fill="currentColor" fill-opacity="0.8"&gt;name, description, and arguments&lt;/text&gt;&#10;&lt;rect x="22" y="156" width="226" height="52" rx="6" fill="#4269d0" fill-opacity="0.35"/&gt;&#10;&lt;text x="34" y="177" font-size="13" font-weight="600" fill="currentColor"&gt;Conversation so far&lt;/text&gt;&#10;&lt;text x="34" y="194" font-size="11" fill="currentColor" fill-opacity="0.8"&gt;the task, every tool call, every result&lt;/text&gt;&#10;&lt;path d="M268 46 h6 v100 h-6" fill="none" stroke="currentColor" stroke-opacity="0.6"/&gt;&#10;&lt;text x="281" y="88" font-size="11" fill="currentColor"&gt;the same on&lt;/text&gt;&#10;&lt;text x="281" y="102" font-size="11" fill="currentColor"&gt;every request&lt;/text&gt;&#10;&lt;path d="M268 158 h6 v48 h-6" fill="none" stroke="currentColor" stroke-opacity="0.6"/&gt;&#10;&lt;text x="281" y="170" font-size="11" fill="currentColor"&gt;grows with&lt;/text&gt;&#10;&lt;text x="281" y="184" font-size="11" fill="currentColor"&gt;every step&lt;/text&gt;&#10;&lt;line x1="135" y1="220" x2="135" y2="246" stroke="currentColor" marker-end="url(#harness-arrow)"/&gt;&#10;&lt;rect x="85" y="250" width="100" height="40" rx="20" fill="currentColor" fill-opacity="0.1" stroke="currentColor" stroke-opacity="0.45"/&gt;&#10;&lt;text x="135" y="275" font-size="13" font-weight="700" text-anchor="middle" fill="currentColor"&gt;Model&lt;/text&gt;&#10;&lt;line x1="186" y1="270" x2="214" y2="270" stroke="currentColor" stroke-opacity="0.6" marker-end="url(#harness-arrow)"/&gt;&#10;&lt;text x="220" y="274" font-size="11" fill="currentColor" fill-opacity="0.8"&gt;or a final answer&lt;/text&gt;&#10;&lt;line x1="135" y1="290" x2="135" y2="318" stroke="currentColor" marker-end="url(#harness-arrow)"/&gt;&#10;&lt;rect x="35" y="322" width="200" height="46" rx="6" fill="none" stroke="currentColor" stroke-opacity="0.45"/&gt;&#10;&lt;text x="47" y="341" font-size="13" font-weight="600" fill="currentColor"&gt;A tool call&lt;/text&gt;&#10;&lt;text x="47" y="358" font-size="11" fill="currentColor" fill-opacity="0.8" font-family="ui-monospace, monospace"&gt;Bash: ls data/&lt;/text&gt;&#10;&lt;line x1="135" y1="368" x2="135" y2="394" stroke="currentColor" marker-end="url(#harness-arrow)"/&gt;&#10;&lt;rect x="35" y="398" width="200" height="46" rx="6" fill="none" stroke="currentColor" stroke-opacity="0.45"/&gt;&#10;&lt;text x="47" y="417" font-size="13" font-weight="600" fill="currentColor"&gt;The harness runs it&lt;/text&gt;&#10;&lt;text x="47" y="434" font-size="11" fill="currentColor" fill-opacity="0.8"&gt;and adds the result&lt;/text&gt;&#10;&lt;path d="M235 421 H355 V199 H264" fill="none" stroke="currentColor" stroke-dasharray="4 3" marker-end="url(#harness-arrow)"/&gt;&#10;&lt;text x="347" y="300" font-size="11" fill="currentColor" text-anchor="middle" transform="rotate(-90 347 300)"&gt;sent again, all of it&lt;/text&gt;&#10;&lt;/svg&gt;&#10;&lt;figcaption&gt;What a coding agent sends with every step. The light parts are the same every time; only the conversation grows.&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;So from the model&amp;rsquo;s side, a harness is three things: its system prompt, its tool definitions, and what comes back when a tool runs.&#10;The first two are just text, so they are easy to copy, and the tool definitions are effectively the harness&amp;rsquo;s API: change them, and the model sees a different harness.&#10;The third is code, which takes more work to copy.&lt;/p&gt;&#10;&lt;p&gt;Because every request resends everything, a task&amp;rsquo;s tokens come in two parts.&#10;The fixed part is what the agent sends before anything happens: its system prompt, its tool definitions, and the task, which every request resends.&#10;The work is everything the steps add on top: the model&amp;rsquo;s replies, the tool results, and the growing conversation that every later request resends too.&#10;When I say below that a model did more work, I mean that second part.&lt;/p&gt;&#10;&lt;h2 id="why-i-believed-it"&gt;Why I believed it &lt;a class="anchor" href="#why-i-believed-it" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Two things convinced me: how well the smallest agents do, and what goes wrong when a model meets unfamiliar tools.&lt;/p&gt;&#10;&lt;h3 id="smaller-agents-do-better"&gt;Smaller agents do better &lt;a class="anchor" href="#smaller-agents-do-better" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Pi made its name by being small.&#10;When Mario Zechner &lt;a href="https://mariozechner.at/posts/2025-11-30-pi-coding-agent/" target="_blank" rel="noopener"&gt;introduced pi&lt;/a&gt; last November, its system prompt and tool definitions together came in below 1,000 tokens, and it had four tools: &lt;code&gt;read&lt;/code&gt;, &lt;code&gt;write&lt;/code&gt;, &lt;code&gt;edit&lt;/code&gt;, and &lt;code&gt;bash&lt;/code&gt;.&#10;He also wrote that &amp;ldquo;pi does not and will not support MCP&amp;rdquo;, the Model Context Protocol through which most agents load outside tools.&#10;And he pointed to Terminus 2, a minimal agent from the Terminal-Bench team, which was &amp;ldquo;holding its own against agents with far more sophisticated tooling&amp;rdquo;.&lt;/p&gt;&#10;&lt;p&gt;In August, DeepSeek released &lt;a href="https://github.com/deepseek-ai/deepseek-harness" target="_blank" rel="noopener"&gt;DeepSeek Harness&lt;/a&gt;, which was &lt;a href="https://news.ycombinator.com/item?id=49285244" target="_blank" rel="noopener"&gt;all over Hacker News&lt;/a&gt; and the local AI subreddits I read.&#10;Its standard setup comes with a full set of tools.&#10;But for benchmarks, DeepSeek &lt;a href="https://github.com/deepseek-ai/deepseek-harness/blob/d743267388641bc76f17c45ce8b4c231aed1d32c/BENCHMARK.md" target="_blank" rel="noopener"&gt;points to its minimal profile&lt;/a&gt;.&#10;In early September, that profile had &lt;a href="https://github.com/deepseek-ai/deepseek-harness/blob/63795eaa5cba78cc0a92d95fccd8db5523d7f050/packages/bundle/sdk-minimal/README.md#L78-L84" target="_blank" rel="noopener"&gt;exactly one tool, a persistent &lt;code&gt;bash&lt;/code&gt;, and a one-line system prompt&lt;/a&gt;: &amp;ldquo;You are a helpful software engineer assistant.&amp;rdquo;&#10;(Ten days later, it already had a second tool, &lt;code&gt;working_directory&lt;/code&gt;; staying that small seems to be hard.)&#10;That is what inspired the minimal mode I added to MindRoom in September, which gives an agent a short prompt and a single &lt;code&gt;bash&lt;/code&gt; tool.&lt;/p&gt;&#10;&lt;h3 id="models-should-know-their-own-tools-best"&gt;Models should know their own tools best &lt;a class="anchor" href="#models-should-know-their-own-tools-best" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;The case that got me thinking about this was Claude Opus 4.8 in pi.&#10;In July, a pi user reported that &lt;a href="https://github.com/earendil-works/pi/issues/6278" target="_blank" rel="noopener"&gt;about 20% of its edits failed in some sessions&lt;/a&gt;.&#10;Pi&amp;rsquo;s &lt;code&gt;edit&lt;/code&gt; tool takes a list of replacements, and Opus 4.8 kept adding made-up fields to them, like &lt;code&gt;in_file&lt;/code&gt;, &lt;code&gt;matchCase&lt;/code&gt;, or &lt;code&gt;newText2&lt;/code&gt;.&#10;Claude Sonnet 5 did it too, while Opus 4.7 and older Claude models never did in the same tests.&lt;/p&gt;&#10;&lt;p&gt;Armin Ronacher, one of pi&amp;rsquo;s maintainers, &lt;a href="https://github.com/earendil-works/pi/issues/6278#issuecomment-4883362982" target="_blank" rel="noopener"&gt;dug into it&lt;/a&gt; and compared it with what Claude Code does with the tool calls it receives.&#10;It turns out that Claude Code quietly repairs a lot of them:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;It accepts several names for the same argument, like &lt;code&gt;old_str&lt;/code&gt; and &lt;code&gt;old_string&lt;/code&gt;.&lt;/li&gt;&#10;&lt;li&gt;It parses an argument that arrives as a string when it should be an object.&lt;/li&gt;&#10;&lt;li&gt;It fixes broken &lt;code&gt;\uXXXX&lt;/code&gt; escapes in strings.&lt;/li&gt;&#10;&lt;li&gt;It drops fields it does not know.&lt;/li&gt;&#10;&lt;li&gt;When it cannot parse a call at all, it asks the model to try again.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;His hypothesis is that RL itself might be the cause.&#10;If a model is trained in a harness that absorbs these mistakes, a slightly wrong tool call still completes the task and still gets rewarded, so nothing teaches the model not to make it.&#10;Pi &lt;a href="https://github.com/earendil-works/pi/commit/a1b336d73e13b53949ff629800081185d3e4694e" target="_blank" rel="noopener"&gt;now ignores unknown fields too&lt;/a&gt;, just like Claude Code.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#10;&lt;p&gt;Then pi itself strayed from its minimal roots.&#10;Pi 1.0 came out on October 1 and &lt;a href="https://earendil.com/posts/pi-1-0/" target="_blank" rel="noopener"&gt;added MCP after all&lt;/a&gt;.&#10;&lt;a href="https://www.theregister.com/ai-and-ml/2026/10/02/pi-coding-agent-pulls-a-180-and-adds-mcp-support/5300678" target="_blank" rel="noopener"&gt;The Register&lt;/a&gt; called it a 180.&#10;On &lt;a href="https://news.ycombinator.com/item?id=49926069" target="_blank" rel="noopener"&gt;Hacker News&lt;/a&gt; and &lt;a href="https://www.reddit.com/r/LocalLLaMA/comments/1wvffcr/pi_10_released_mcp_support_now_included_by_default/" target="_blank" rel="noopener"&gt;r/LocalLLaMA&lt;/a&gt;, people worried that &lt;a href="https://news.ycombinator.com/item?id=49926549" target="_blank" rel="noopener"&gt;&amp;ldquo;Pi&amp;rsquo;s days as a nice minimal agent TUI are numbered&amp;rdquo;&lt;/a&gt;.&#10;What struck me was how the maintainers explained it.&#10;&lt;a href="https://news.ycombinator.com/item?id=49926377" target="_blank" rel="noopener"&gt;Armin Ronacher&lt;/a&gt; wrote that the models &amp;ldquo;are trained on their respective harnesses and we&amp;rsquo;re not here to fight their behavior&amp;rdquo;, and &lt;a href="https://news.ycombinator.com/item?id=49926840" target="_blank" rel="noopener"&gt;Mario Zechner&lt;/a&gt; that &amp;ldquo;we follow what the models are trained on&amp;rdquo;.&#10;That is exactly the native-tools half of my plan.&lt;/p&gt;&#10;&lt;p&gt;My plan combined both: a minimal agent, with each model&amp;rsquo;s native shell as its only tool.&#10;Terminal-Bench also said something I chose to ignore: agents like Terminus 2 do well with tools no model was trained on.&#10;I did not believe that part.&#10;In opencode and pi, I had repeatedly seen models get the edit tool wrong, so I assumed the benchmarks did not carry over to real work.&#10;My belief that a model works best in the harness it was trained in was that strong: I expected the native tools to help, and to help most in a minimal agent with nothing but a shell.&lt;/p&gt;&#10;&lt;h2 id="what-i-built"&gt;What I built &lt;a class="anchor" href="#what-i-built" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;MindRoom is my open-source platform for AI agents that live in Matrix chat rooms, where several agents can work together.&#10;Its agents get shell and file tools under MindRoom&amp;rsquo;s own names, like &lt;code&gt;run_shell_command&lt;/code&gt;, &lt;code&gt;read_file&lt;/code&gt;, and &lt;code&gt;edit_file&lt;/code&gt;.&#10;In &lt;a href="https://github.com/mindroom-ai/mindroom/pull/2766" target="_blank" rel="noopener"&gt;this pull request&lt;/a&gt;, I added what I call tool dialects, which show a model those tools in the shape of the coding agent it was trained in.&lt;/p&gt;&#10;&lt;div class="table-wrap"&gt;&#10;&lt;table&gt;&#10;&lt;thead&gt;&#10;&lt;tr&gt;&#10;&lt;th&gt;Model&lt;/th&gt;&#10;&lt;th&gt;Sees&lt;/th&gt;&#10;&lt;th&gt;Instead of&lt;/th&gt;&#10;&lt;/tr&gt;&#10;&lt;/thead&gt;&#10;&lt;tbody&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude&lt;/td&gt;&#10;&lt;td&gt;&lt;code&gt;Bash&lt;/code&gt;, &lt;code&gt;BashOutput&lt;/code&gt;, &lt;code&gt;KillShell&lt;/code&gt;, &lt;code&gt;Read&lt;/code&gt;, &lt;code&gt;Edit&lt;/code&gt;, and &lt;code&gt;Write&lt;/code&gt;, as in Claude Code&lt;/td&gt;&#10;&lt;td&gt;&lt;code&gt;run_shell_command&lt;/code&gt;, &lt;code&gt;check_shell_command&lt;/code&gt;, &lt;code&gt;kill_shell_command&lt;/code&gt;, &lt;code&gt;read_file&lt;/code&gt;, &lt;code&gt;edit_file&lt;/code&gt;, and &lt;code&gt;write_file&lt;/code&gt;&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT&lt;/td&gt;&#10;&lt;td&gt;&lt;code&gt;exec_command&lt;/code&gt;, &lt;code&gt;write_stdin&lt;/code&gt;, and a freeform &lt;code&gt;apply_patch&lt;/code&gt; that takes the patch as plain text, as in Codex, and a &lt;code&gt;kill_shell_command&lt;/code&gt; that takes Codex&amp;rsquo;s &lt;code&gt;session_id&lt;/code&gt;&lt;/td&gt;&#10;&lt;td&gt;&lt;code&gt;run_shell_command&lt;/code&gt;, &lt;code&gt;check_shell_command&lt;/code&gt;, &lt;code&gt;kill_shell_command&lt;/code&gt;, &lt;code&gt;edit_file&lt;/code&gt;, and &lt;code&gt;write_file&lt;/code&gt;&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;Inside MindRoom, nothing changes: approvals, hooks, and the stored history keep MindRoom&amp;rsquo;s names, and the translation only happens on the way to and from the model.&#10;That gives MindRoom a property I like a lot: a conversation can switch from Claude to GPT halfway through, and each model sees the earlier tool calls in its own shape, as if it had made them in its own harness.&lt;/p&gt;&#10;&lt;p&gt;Matching the native harness exactly turned out to be a stretch, though.&#10;Codex has no tool for reading files, so in the pull request, GPT keeps MindRoom&amp;rsquo;s &lt;code&gt;read_file&lt;/code&gt;, and both keep MindRoom&amp;rsquo;s &lt;code&gt;grep&lt;/code&gt;, &lt;code&gt;find_files&lt;/code&gt;, and &lt;code&gt;ls&lt;/code&gt;, which makes each native set a mix.&#10;For the main comparison, I removed those extra tools, so each model saw only the tools of its own harness.&#10;The tools have the same names and arguments as in Claude Code and Codex, but I wrote short descriptions of my own, because Claude Code&amp;rsquo;s are not openly licensed.&#10;What they return is MindRoom&amp;rsquo;s output, and the system prompt is MindRoom&amp;rsquo;s too.&#10;So keep in mind for everything below: I tested the names and shapes of the tools, not the whole harness.&lt;/p&gt;&#10;&lt;details&gt;&#10; &lt;summary&gt;How the translation works&lt;/summary&gt;&#10; &lt;ul&gt;&#10;&lt;li&gt;Codex&amp;rsquo;s &lt;code&gt;apply_patch&lt;/code&gt; is freeform: the model writes the patch as plain text instead of JSON arguments. I ported Codex&amp;rsquo;s patch parser and the code that applies patches, together with Codex&amp;rsquo;s own test cases, so a patch from a Codex-trained model applies exactly as it would in Codex. Its description comes from Codex too, which is openly licensed.&lt;/li&gt;&#10;&lt;li&gt;A switched model sees earlier calls in its own shape only for the tools its own harness also has, like the shell: an edit made with Claude Code&amp;rsquo;s &lt;code&gt;Edit&lt;/code&gt; stays an &lt;code&gt;edit_file&lt;/code&gt; call for GPT, which has no matching tool.&lt;/li&gt;&#10;&lt;li&gt;An earlier version of the pull request also rewrote every tool result to look like the native one. That was a lot of fragile code, so I removed it before I measured anything.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&#10;&lt;/details&gt;&#10;&#10;&lt;h2 id="how-i-measured-it"&gt;How I measured it &lt;a class="anchor" href="#how-i-measured-it" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;I used 12 terminal tasks from an evaluation suite I built for MindRoom, like writing a report from a CSV file, finding the commit that broke a check, or fixing failing tests.&lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt;&#10;A hidden check graded each result, and every setup ran every task three times.&#10;Almost every run passed, so the interesting number is how many tokens the agent needed to get there, cached input included, and cheaper in what follows means fewer tokens.&lt;sup id="fnref:3"&gt;&lt;a href="#fn:3" class="footnote-ref" role="doc-noteref"&gt;3&lt;/a&gt;&lt;/sup&gt;&#10;The tool comparisons ran through MindRoom&amp;rsquo;s OpenAI-compatible API; minimal mode, which only works in chat, ran through Matrix.&#10;I tested five current models, Claude Opus 5.5 and Sonnet 5.5, and GPT-6 Astra, GPT-6.1 Sol, and GPT-6 Luna, and later &lt;a href="#older-models-only-opus-48-did-better-with-them"&gt;five older ones&lt;/a&gt;.&#10;The current Claude models ran with adaptive thinking, where the model decides when to think.&#10;I called the GPT models from MindRoom through OpenAI&amp;rsquo;s Codex backend, the endpoint the Codex CLI uses, so no run used Codex itself; with no reasoning effort set, the backend picks one.&lt;/p&gt;&#10;&lt;details&gt;&#10; &lt;summary&gt;Details of the setup&lt;/summary&gt;&#10; &lt;ul&gt;&#10;&lt;li&gt;A small harness sent each task to MindRoom&amp;rsquo;s OpenAI-compatible API as a new conversation, and a hidden check graded the result in a separate container without network access. Every task ran three times per configuration, so each number in this post comes from 36 runs.&lt;/li&gt;&#10;&lt;li&gt;The agent&amp;rsquo;s commands ran in a Docker container, the way MindRoom runs agents it does not fully trust.&lt;/li&gt;&#10;&lt;li&gt;With adaptive thinking, the current Claude models thought before 15 to 25% of their replies, with MindRoom&amp;rsquo;s tools and with the native ones.&lt;/li&gt;&#10;&lt;li&gt;I ran the GPT models through OpenAI&amp;rsquo;s Codex backend, the endpoint the Codex CLI uses, and sent no reasoning effort, so the backend picked one. The GPT-6 models barely reasoned on these tasks: in those runs, only 4 to 12% of their requests had any reasoning tokens, and then 7 to 234 of them.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&#10;&lt;/details&gt;&#10;&#10;&lt;h2 id="native-tools-dont-make-todays-models-more-efficient"&gt;Native tools don&amp;rsquo;t make today&amp;rsquo;s models more efficient &lt;a class="anchor" href="#native-tools-dont-make-todays-models-more-efficient" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;To make the comparison fair, I gave each model only the tools of its own harness, against MindRoom&amp;rsquo;s matching set.&lt;sup id="fnref:4"&gt;&lt;a href="#fn:4" class="footnote-ref" role="doc-noteref"&gt;4&lt;/a&gt;&lt;/sup&gt;&#10;For Claude, that is a shell and tools to read, edit, and write files; for GPT, a shell and Codex&amp;rsquo;s &lt;code&gt;apply_patch&lt;/code&gt;, against MindRoom&amp;rsquo;s tools to edit and write files.&lt;/p&gt;&#10;&lt;figure class="plot-figure"&gt;&#10; &lt;div class="plot-container" role="img" aria-label="Change in tokens per task when each model uses its native harness tools instead of MindRoom&amp;rsquo;s, with 95% confidence intervals: with only the harness&amp;rsquo;s own tools against MindRoom&amp;rsquo;s matching set, and with the mixed set in the pull request. Hover for values." data-plot-module="/post/native-harness-tools/plots.js" data-plot-name="fairCurrent"&gt;&lt;/div&gt;&#10; &lt;figcaption&gt;Change in tokens per task when each model uses its native harness tools instead of MindRoom&amp;rsquo;s, with 95% confidence intervals: with only the harness&amp;rsquo;s own tools against MindRoom&amp;rsquo;s matching set, and with the mixed set in the pull request. Hover for values.&lt;/figcaption&gt;&#10; &lt;noscript&gt;This chart needs JavaScript.&lt;/noscript&gt;&#10;&lt;/figure&gt;&#10;&#10;&lt;script type="module" src="https://www.nijho.lt/js/plot.7cb86dc2e3ef25b56bc93730b2620745a7f02b5715de87f94e61908f60e51690.js" integrity="sha256-fLhtwuPvJbVryTcwsmIHRafwK1cV3of5TmGQj2DlFpA=" crossorigin="anonymous"&gt;&lt;/script&gt;&#10;&#10;&#10;&lt;p&gt;Claude got 6 to 13% cheaper with Claude Code&amp;rsquo;s tools, but only because the definitions I wrote for them are about 480 tokens shorter than MindRoom&amp;rsquo;s, and every request resends them; the tools themselves saved nothing, and Sonnet 5.5 even did 15% more work with them.&#10;It never even touched the file tools: Opus 5.5 and Sonnet 5.5 did everything in the shell, with either set.&lt;/p&gt;&#10;&lt;p&gt;GPT-6 Astra and Sol got much more expensive, while Luna barely changed.&#10;With only Codex&amp;rsquo;s tools, GPT-6 Astra did 84% more work and used 59% more tokens.&#10;It called &lt;code&gt;apply_patch&lt;/code&gt; 30 times, as a separate step for edits it otherwise made inside its shell commands, and every extra step resends the whole conversation so far.&#10;I expected the opposite: these are the tools I assumed these models were trained on, so I thought they would need fewer and more confident steps.&#10;The mixed set, the lighter rows, points the same way.&lt;/p&gt;&#10;&lt;p&gt;The tool mistakes I wanted to prevent did not happen with MindRoom&amp;rsquo;s tools at all: with its matching set, none of the five models made a single tool error.&#10;The only errors came from the mixed set: next to Codex&amp;rsquo;s tools, Luna had to guess how MindRoom&amp;rsquo;s &lt;code&gt;read_file&lt;/code&gt; resolves paths, and got it wrong seven times.&lt;/p&gt;&#10;&lt;details&gt;&#10; &lt;summary&gt;The numbers behind this section&lt;/summary&gt;&#10; &lt;p&gt;&lt;strong&gt;Fixed part and work.&lt;/strong&gt;&#10;Every request to a model sends the whole conversation so far, plus the definition of every tool the model can use.&#10;So I split each task&amp;rsquo;s tokens in two.&#10;The fixed part is the first request&amp;rsquo;s input, which holds the system prompt, the tool definitions, and the task, times the number of requests.&#10;The work is everything else: tool results and the model&amp;rsquo;s replies, counted again with every later request that resends them, so it also grows with the number of steps.&#10;Providers cache most of the fixed part between requests and charge much less for cached input, so it costs less than its share of the tokens suggests.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Only the harness&amp;rsquo;s own tools.&lt;/strong&gt;&#10;With Claude Code&amp;rsquo;s tools, Opus 5.5 used 13% fewer tokens [95% CI −19 to −6%] and Sonnet 5.5 6% fewer [−10 to −1%].&#10;Both came from the definitions: the Claude Code-style set I wrote is about 480 tokens shorter, while the work on top of it grew by 7% [−7 to +23%] and 15% [+7 to +25%].&#10;With Codex&amp;rsquo;s tools, GPT-6 Astra used 59% more tokens [+53 to +65%] and GPT-6.1 Sol 43% more [+33 to +52%].&#10;They called &lt;code&gt;apply_patch&lt;/code&gt; 30 and 22 times, where with MindRoom&amp;rsquo;s tools they made only 3 and 6 calls to the file tools, so they needed 4.7 and 4.4 requests per task instead of 3.5 and 3.6 and did 84% [+73 to +96%] and 60% [+44 to +76%] more work.&#10;GPT-6 Luna used about the same with either set, +3% [−8 to +15%], and called &lt;code&gt;apply_patch&lt;/code&gt; only 8 times.&#10;The pass rates stayed within one or two runs of each other, and no model made a tool error with either set.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;The mixed set, as it is in the pull request.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;figure class="plot-figure"&gt;&#10; &lt;div class="plot-container" role="img" aria-label="Change in tokens per task when each model uses its native harness tools instead of MindRoom&amp;rsquo;s, with 95% confidence intervals. The second row caps the native shell output at the last 100 lines, MindRoom&amp;rsquo;s shell default. Hover for values." data-plot-module="/post/native-harness-tools/plots.js" data-plot-name="nativeDelta"&gt;&lt;/div&gt;&#10; &lt;figcaption&gt;Change in tokens per task when each model uses its native harness tools instead of MindRoom&amp;rsquo;s, with 95% confidence intervals. The second row caps the native shell output at the last 100 lines, MindRoom&amp;rsquo;s shell default. Hover for values.&lt;/figcaption&gt;&#10; &lt;noscript&gt;This chart needs JavaScript.&lt;/noscript&gt;&#10;&lt;/figure&gt;&#10;&lt;script type="module" src="https://www.nijho.lt/js/plot.7cb86dc2e3ef25b56bc93730b2620745a7f02b5715de87f94e61908f60e51690.js" integrity="sha256-fLhtwuPvJbVryTcwsmIHRafwK1cV3of5TmGQj2DlFpA=" crossorigin="anonymous"&gt;&lt;/script&gt;&#10;&lt;p&gt;With Claude Code&amp;rsquo;s tools, both Claude models used about 9% fewer tokens.&#10;With Codex&amp;rsquo;s tools, GPT-6 Astra used 31% more tokens and GPT-6.1 Sol 19% more.&#10;An earlier run of the same experiment, before some unrelated fixes in the pull request, gave almost the same numbers: 33% more for Astra and 15% more for Sol.&#10;For GPT-6 Luna, the difference was too small to tell apart from noise.&#10;The pass rates barely moved: Opus, Sonnet, and Sol passed all 36 runs with either set of tools, and Astra failed one run in some configurations.&#10;Luna passed 33 runs with MindRoom&amp;rsquo;s tools and 35 with Codex&amp;rsquo;s; in the earlier run it was the other way around, 35 against 32, so I would not read anything into it either.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;It is not the longer output.&lt;/strong&gt;&#10;MindRoom&amp;rsquo;s own shell tool returns the last 100 lines of a command&amp;rsquo;s output by default.&#10;For the native tools, I returned everything up to 50 KiB, because that is closer to what Claude Code and Codex do.&#10;So I ran everything again with the native tools capped at the same 100 lines, the second row in the chart above.&#10;The cap barely changes anything: Astra still uses 26% more tokens, Sol 15% more, and the Claude models still save about 8%.&#10;The models hardly ever print more than 100 lines anyway: in the uncapped run, 3 of Astra&amp;rsquo;s 91 shell results and 3 of Sol&amp;rsquo;s 93 were longer than that, and none of Claude&amp;rsquo;s 220.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Where the tokens went with the mixed set.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;figure class="plot-figure"&gt;&#10; &lt;div class="plot-container" role="img" aria-label="Tokens per task with MindRoom&amp;rsquo;s shell and file tools and with the native ones, split into the fixed part (light) and the work the model did on top of it (dark). Hover for the number of requests." data-plot-module="/post/native-harness-tools/plots.js" data-plot-name="tokenSplit"&gt;&lt;/div&gt;&#10; &lt;figcaption&gt;Tokens per task with MindRoom&amp;rsquo;s shell and file tools and with the native ones, split into the fixed part (light) and the work the model did on top of it (dark). Hover for the number of requests.&lt;/figcaption&gt;&#10; &lt;noscript&gt;This chart needs JavaScript.&lt;/noscript&gt;&#10;&lt;/figure&gt;&#10;&lt;script type="module" src="https://www.nijho.lt/js/plot.7cb86dc2e3ef25b56bc93730b2620745a7f02b5715de87f94e61908f60e51690.js" integrity="sha256-fLhtwuPvJbVryTcwsmIHRafwK1cV3of5TmGQj2DlFpA=" crossorigin="anonymous"&gt;&lt;/script&gt;&#10;&lt;p&gt;Claude did not work any differently with Claude Code&amp;rsquo;s tools.&#10;It never called a file tool with either set, did everything in the shell, and made about the same number of requests.&#10;Its work changed by 5% or less, and almost all of its savings come from the fixed part: the Claude Code-style definitions I wrote are about 480 tokens shorter than MindRoom&amp;rsquo;s.&lt;/p&gt;&#10;&lt;p&gt;GPT did work differently.&#10;With Codex&amp;rsquo;s tools, Astra and Sol edited files with &lt;code&gt;apply_patch&lt;/code&gt; 17 and 15 times, where with MindRoom&amp;rsquo;s tools they made only 3 and 5 calls to the file tools and did the rest from the shell.&#10;Each patch is a request of its own, which accounts for their 0.3 to 0.5 extra requests per task.&#10;They also did 51% and 24% more work.&#10;And Codex&amp;rsquo;s tools take about 130 more tokens to describe than MindRoom&amp;rsquo;s, because &lt;code&gt;apply_patch&lt;/code&gt; costs about 270 more than &lt;code&gt;edit_file&lt;/code&gt; and &lt;code&gt;write_file&lt;/code&gt; together, so the fixed part grew as well.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;The mistakes.&lt;/strong&gt;&#10;None of the five models made a single tool error with MindRoom&amp;rsquo;s tools in its 36 runs.&#10;Partly, the models rarely needed the file tools: the Claude models never called one, and of the GPT models, only Luna used them often.&#10;The only model that made tool errors was Luna, and only with the Codex tools: 7 errors in 36 runs, all of them &lt;code&gt;read_file&lt;/code&gt; calls with a path relative to the directory Luna had just given &lt;code&gt;exec_command&lt;/code&gt;.&#10;The made-up fields in pi always appeared inside its nested list of replacements, where the model has to write the JSON for each replacement itself.&#10;MindRoom&amp;rsquo;s &lt;code&gt;edit_file&lt;/code&gt; is flat, like Claude Code&amp;rsquo;s &lt;code&gt;Edit&lt;/code&gt;: a path, the old text, and the new text.&#10;So I suspected that keeping the tools as simple as the native ones matters more than matching their exact names.&lt;/p&gt;&#10;&#10;&lt;/details&gt;&#10;&#10;&lt;h2 id="older-models-only-opus-48-did-better-with-them"&gt;Older models: only Opus 4.8 did better with them &lt;a class="anchor" href="#older-models-only-opus-48-did-better-with-them" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The pi story made me wonder whether this used to be different, since Opus 4.8 struggled with pi&amp;rsquo;s edit tool while Opus 4.7 did not.&#10;So I ran the same comparisons on older models that are still available: Claude Opus 4.7, Opus 4.8, and Sonnet 5, and GPT-5.5 and GPT-5.6 Sol.&lt;/p&gt;&#10;&lt;figure class="plot-figure"&gt;&#10; &lt;div class="plot-container" role="img" aria-label="Change in tokens per task when the older models use their native harness tools instead of MindRoom&amp;rsquo;s, with 95% confidence intervals: with only the harness&amp;rsquo;s own tools against MindRoom&amp;rsquo;s matching set, and with the mixed set in the pull request. Opus 4.7 and 4.8 ran without thinking, Sonnet 5 with adaptive thinking, and GPT with the effort Codex picks. Hover for values." data-plot-module="/post/native-harness-tools/plots.js" data-plot-name="fairOlder"&gt;&lt;/div&gt;&#10; &lt;figcaption&gt;Change in tokens per task when the older models use their native harness tools instead of MindRoom&amp;rsquo;s, with 95% confidence intervals: with only the harness&amp;rsquo;s own tools against MindRoom&amp;rsquo;s matching set, and with the mixed set in the pull request. Opus 4.7 and 4.8 ran without thinking, Sonnet 5 with adaptive thinking, and GPT with the effort Codex picks. Hover for values.&lt;/figcaption&gt;&#10; &lt;noscript&gt;This chart needs JavaScript.&lt;/noscript&gt;&#10;&lt;/figure&gt;&#10;&#10;&lt;script type="module" src="https://www.nijho.lt/js/plot.7cb86dc2e3ef25b56bc93730b2620745a7f02b5715de87f94e61908f60e51690.js" integrity="sha256-fLhtwuPvJbVryTcwsmIHRafwK1cV3of5TmGQj2DlFpA=" crossorigin="anonymous"&gt;&lt;/script&gt;&#10;&#10;&#10;&lt;p&gt;With only each harness&amp;rsquo;s own tools, the older models did not prefer their native tools either, except for one.&#10;The exception is the model from the pi story: Opus 4.8 did 17% less work and used 19% fewer tokens with Claude Code&amp;rsquo;s tools, reading files through Bash instead of with a separate tool.&#10;With the mixed set, the older Claude models seemed to prefer Claude Code&amp;rsquo;s tools, using 22 to 36% fewer tokens, but that came from the extra tools the mixed set keeps from MindRoom, &lt;code&gt;grep&lt;/code&gt;, &lt;code&gt;find_files&lt;/code&gt;, and &lt;code&gt;ls&lt;/code&gt;: next to MindRoom&amp;rsquo;s other tools, those made the older Claude models take more steps and read more, and next to Claude Code&amp;rsquo;s tools, the models hardly touched them.&#10;And on the pi story itself: Opus 4.8 and Sonnet 5, the two models that made up fields in pi, made 111 edits with MindRoom&amp;rsquo;s &lt;code&gt;edit_file&lt;/code&gt;, which takes a single path, old text, and new text, and none of them failed.&lt;/p&gt;&#10;&lt;p&gt;With only each harness&amp;rsquo;s own tools, the GPT-5 models did about the same with either set, and unlike GPT-6 Astra and Sol, they barely used &lt;code&gt;apply_patch&lt;/code&gt;.&#10;So reaching for its native editing tool, and paying for it, is new in that generation.&lt;/p&gt;&#10;&lt;p&gt;Of the ten models I tested, familiar tools clearly made only one more efficient, the one that started it.&#10;The others did as well or better with tools they were presumably not trained on: they seem to generalize beyond the environment they were trained in.&lt;/p&gt;&#10;&lt;details&gt;&#10; &lt;summary&gt;The numbers behind this section&lt;/summary&gt;&#10; &lt;p&gt;&lt;strong&gt;Only the harness&amp;rsquo;s own tools.&lt;/strong&gt;&#10;With Claude Code&amp;rsquo;s tools, Opus 4.7 used 3% fewer tokens [−12 to +6%], Opus 4.8 19% fewer [−26 to −11%], and Sonnet 5 7% fewer [−29 to +23%], a noisy result.&#10;Opus 4.8 did 17% less work [−29 to −4%] on top of the shorter definitions, while the other older models&amp;rsquo; work changed by −5 to +13%, none of it clearly; Opus 4.8 called MindRoom&amp;rsquo;s &lt;code&gt;read_file&lt;/code&gt; 27 times, but never Claude Code&amp;rsquo;s &lt;code&gt;Read&lt;/code&gt;.&#10;With Codex&amp;rsquo;s tools, GPT-5.5 used 5% more [−5 to +16%] and GPT-5.6 Sol 3% more [−4 to +11%]; they called &lt;code&gt;apply_patch&lt;/code&gt; only 3 and 9 times, where with MindRoom&amp;rsquo;s tools they made 20 and 16 calls to the file tools.&#10;The pass rates stayed within one or two runs of each other.&#10;None of the older models made a tool error with MindRoom&amp;rsquo;s matching set; with Codex&amp;rsquo;s, GPT-5.5 sent garbled working directories to &lt;code&gt;exec_command&lt;/code&gt; 11 times.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Why the mixed set made them look different.&lt;/strong&gt;&#10;The only difference between the two tests is that the mixed set adds MindRoom&amp;rsquo;s &lt;code&gt;grep&lt;/code&gt;, &lt;code&gt;find_files&lt;/code&gt;, and &lt;code&gt;ls&lt;/code&gt; to both sides.&#10;Next to MindRoom&amp;rsquo;s other tools, the older Claude models called &lt;code&gt;ls&lt;/code&gt; and &lt;code&gt;grep&lt;/code&gt; 20, 9, and 3 times, took 0.3 to 0.9 more requests per task, and did 35 to 38% more work than without them.&#10;Next to Claude Code&amp;rsquo;s tools, they called them once in total.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;The older models with the mixed set.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;figure class="plot-figure"&gt;&#10; &lt;div class="plot-container" role="img" aria-label="Change in tokens per task when each model uses its native harness tools instead of MindRoom&amp;rsquo;s, with 95% confidence intervals, oldest models first in each family. Each model&amp;rsquo;s reasoning mode is in parentheses: Opus 4.7 and 4.8 do not think, the other Claude models think adaptively, and GPT uses the effort Codex picks. Hover for values." data-plot-module="/post/native-harness-tools/plots.js" data-plot-name="generations"&gt;&lt;/div&gt;&#10; &lt;figcaption&gt;Change in tokens per task when each model uses its native harness tools instead of MindRoom&amp;rsquo;s, with 95% confidence intervals, oldest models first in each family. Each model&amp;rsquo;s reasoning mode is in parentheses: Opus 4.7 and 4.8 do not think, the other Claude models think adaptively, and GPT uses the effort Codex picks. Hover for values.&lt;/figcaption&gt;&#10; &lt;noscript&gt;This chart needs JavaScript.&lt;/noscript&gt;&#10;&lt;/figure&gt;&#10;&lt;script type="module" src="https://www.nijho.lt/js/plot.7cb86dc2e3ef25b56bc93730b2620745a7f02b5715de87f94e61908f60e51690.js" integrity="sha256-fLhtwuPvJbVryTcwsmIHRafwK1cV3of5TmGQj2DlFpA=" crossorigin="anonymous"&gt;&lt;/script&gt;&#10;&lt;p&gt;Opus 4.7, Opus 4.8, and Sonnet 5 used 22 to 36% fewer tokens with Claude Code&amp;rsquo;s tools.&#10;Unlike the 5.5 models, they also made fewer requests and did 26 to 45% less work on top of the fixed part.&#10;GPT-5.6 Sol used 15% fewer tokens with Codex&amp;rsquo;s tools and did 27% less work, and GPT-5.5 used about the same.&#10;One generation later, the GPT-6 models use up to 31% more with Codex&amp;rsquo;s tools, and the Claude 5.5 models mostly save what the shorter definitions save.&#10;The pass rates stayed within one or two runs of each other for every model.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;How they used the file tools.&lt;/strong&gt;&#10;With MindRoom&amp;rsquo;s tools, the older Claude models called &lt;code&gt;read_file&lt;/code&gt; 24, 29, and 44 times; with Claude Code&amp;rsquo;s, they called &lt;code&gt;Read&lt;/code&gt; only 3, 1, and 6 times and read files through Bash instead.&#10;GPT-5.6 Sol needed 9 patches where it had made 32 calls to &lt;code&gt;edit_file&lt;/code&gt; and &lt;code&gt;write_file&lt;/code&gt;.&#10;Opus 4.8 and Sonnet 5 made 37 and 21 calls to MindRoom&amp;rsquo;s flat &lt;code&gt;edit_file&lt;/code&gt;, and none of them failed.&#10;That does not prove that pi&amp;rsquo;s nested list caused pi&amp;rsquo;s failures, because I never gave them a nested edit tool, but a flat one did not trigger them.&#10;Their few tool errors were different ones: Sonnet 5 twice polled a background command that did not exist, GPT-5.5 and GPT-5.6 Sol each had one edit whose old text did not match, and GPT-5.5 sent garbled working directories to Codex&amp;rsquo;s &lt;code&gt;exec_command&lt;/code&gt; seven times.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Only the shell tools.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;figure class="plot-figure"&gt;&#10; &lt;div class="plot-container" role="img" aria-label="Change in tokens per task when the older models use their native harness tools instead of MindRoom&amp;rsquo;s, with 95% confidence intervals: with shell and file tools, and with only the shell tools. Opus 4.7 and 4.8 ran without thinking, Sonnet 5 with adaptive thinking, and GPT with the effort Codex picks. Hover for values." data-plot-module="/post/native-harness-tools/plots.js" data-plot-name="olderShell"&gt;&lt;/div&gt;&#10; &lt;figcaption&gt;Change in tokens per task when the older models use their native harness tools instead of MindRoom&amp;rsquo;s, with 95% confidence intervals: with shell and file tools, and with only the shell tools. Opus 4.7 and 4.8 ran without thinking, Sonnet 5 with adaptive thinking, and GPT with the effort Codex picks. Hover for values.&lt;/figcaption&gt;&#10; &lt;noscript&gt;This chart needs JavaScript.&lt;/noscript&gt;&#10;&lt;/figure&gt;&#10;&lt;script type="module" src="https://www.nijho.lt/js/plot.7cb86dc2e3ef25b56bc93730b2620745a7f02b5715de87f94e61908f60e51690.js" integrity="sha256-fLhtwuPvJbVryTcwsmIHRafwK1cV3of5TmGQj2DlFpA=" crossorigin="anonymous"&gt;&lt;/script&gt;&#10;&lt;p&gt;The native set mixes a model&amp;rsquo;s own tools with some of MindRoom&amp;rsquo;s, such as &lt;code&gt;grep&lt;/code&gt;, &lt;code&gt;ls&lt;/code&gt;, and, for GPT, &lt;code&gt;read_file&lt;/code&gt;, so I also ran the older models with only the shell tools, in MindRoom&amp;rsquo;s shape and in the native one.&#10;Opus 4.7 then used 10% fewer tokens with the native shell, GPT-5.6 Sol 6% fewer, and GPT-5.5 the same, and almost all of that came from shorter definitions.&#10;Opus 4.8 used 23% fewer tokens, made fewer requests, and did 16% less work.&#10;Sonnet 5&amp;rsquo;s result is too noisy to read: in one run, the native shell returned a 50 KB output early on, and resending it with every later request made that run cost 12 times the median; its median run used 9% fewer tokens with the native shell.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;The reasoning settings.&lt;/strong&gt;&#10;Opus 4.7 and 4.8 do not think unless you ask them to, and Sonnet 5 thought before 42% of its replies, against 15 to 25% for the 5.5 models at the same adaptive setting.&#10;The GPT-5 models reasoned before 59 to 76% of their requests, while the GPT-6 models reasoned before only 4 to 12%.&#10;With adaptive thinking and the mixed set, Opus 4.7 and 4.8 thought before 26 to 36% of their replies, and still used 35% and 20% fewer tokens with Claude Code&amp;rsquo;s tools.&#10;For that test, I set &lt;code&gt;thinking&lt;/code&gt; to &lt;code&gt;adaptive&lt;/code&gt; in the model&amp;rsquo;s &lt;code&gt;extra_kwargs&lt;/code&gt;, since these models reject a fixed thinking budget.&lt;/p&gt;&#10;&lt;p&gt;I also ran one current model of each family, Claude Sonnet 5.5 and GPT-6 Astra, at low and at high reasoning effort.&#10;For Astra, I set &lt;code&gt;reasoning_effort&lt;/code&gt; to &lt;code&gt;low&lt;/code&gt; or &lt;code&gt;high&lt;/code&gt;; for Sonnet 5.5, &lt;code&gt;output_config.effort&lt;/code&gt;, which is how the Claude 5.5 models take a reasoning effort.&lt;/p&gt;&#10;&lt;figure class="plot-figure"&gt;&#10; &lt;div class="plot-container" role="img" aria-label="Change in tokens per task when Claude Sonnet 5.5 and GPT-6 Astra use their native harness tools instead of MindRoom&amp;rsquo;s, at each reasoning effort, with 95% confidence intervals. With no effort set, Sonnet uses adaptive thinking, and Astra the effort Codex picks. Hover for the tokens per task." data-plot-module="/post/native-harness-tools/plots.js" data-plot-name="effortChange"&gt;&lt;/div&gt;&#10; &lt;figcaption&gt;Change in tokens per task when Claude Sonnet 5.5 and GPT-6 Astra use their native harness tools instead of MindRoom&amp;rsquo;s, at each reasoning effort, with 95% confidence intervals. With no effort set, Sonnet uses adaptive thinking, and Astra the effort Codex picks. Hover for the tokens per task.&lt;/figcaption&gt;&#10; &lt;noscript&gt;This chart needs JavaScript.&lt;/noscript&gt;&#10;&lt;/figure&gt;&#10;&lt;script type="module" src="https://www.nijho.lt/js/plot.7cb86dc2e3ef25b56bc93730b2620745a7f02b5715de87f94e61908f60e51690.js" integrity="sha256-fLhtwuPvJbVryTcwsmIHRafwK1cV3of5TmGQj2DlFpA=" crossorigin="anonymous"&gt;&lt;/script&gt;&#10;&lt;p&gt;Both models passed all 36 runs at every effort with either set of tools, except for one run that Astra failed with MindRoom&amp;rsquo;s tools at its default effort.&#10;A higher effort made Codex&amp;rsquo;s tools worse for GPT. At high effort, Astra made 4.5 requests per task with Codex&amp;rsquo;s tools against 3.6 with MindRoom&amp;rsquo;s, and used 45% more tokens.&#10;Even at high effort, though, Astra reasoned before only 10 to 12% of its requests, against 4 to 7% at its default, far below the GPT-5 models.&#10;For Claude, the native tools stayed cheaper at every level, and saved the most at low effort, 19%, where Sonnet thought before only 3 to 4% of its replies.&#10;Sonnet thought about as often at its default as at high effort, so I would not read much into the difference between those two.&lt;/p&gt;&#10;&#10;&lt;/details&gt;&#10;&#10;&lt;h2 id="what-does-matter-what-the-agent-sends"&gt;What does matter: what the agent sends &lt;a class="anchor" href="#what-does-matter-what-the-agent-sends" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;My next guess was the other half of my plan, a smaller agent.&#10;Every request to the model resends the system prompt and the definition of every tool, so an agent with a shorter prompt and fewer tools sends less with every step.&lt;/p&gt;&#10;&lt;h3 id="fewer-tools"&gt;Fewer tools &lt;a class="anchor" href="#fewer-tools" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Fewer tools did help.&#10;With only MindRoom&amp;rsquo;s shell tools and none of its file tools, the agent used about a third fewer tokens and passed about as many runs.&#10;A shell-only agent is also where I still expected the native tools to matter most, because every step goes through the one tool whose shape the model knows best.&#10;They did not: GPT used the same number of tokens with Codex&amp;rsquo;s shell tools, and Claude saved only what its shorter descriptions save.&lt;/p&gt;&#10;&lt;details&gt;&#10; &lt;summary&gt;The numbers behind this section&lt;/summary&gt;&#10; &lt;figure class="plot-figure"&gt;&#10; &lt;div class="plot-container" role="img" aria-label="Change in tokens per task, with 95% confidence intervals: with only MindRoom&amp;rsquo;s shell tools instead of all of MindRoom&amp;rsquo;s tools, and with only the native shell tools instead of MindRoom&amp;rsquo;s. Hover for values." data-plot-module="/post/native-harness-tools/plots.js" data-plot-name="shellOnly"&gt;&lt;/div&gt;&#10; &lt;figcaption&gt;Change in tokens per task, with 95% confidence intervals: with only MindRoom&amp;rsquo;s shell tools instead of all of MindRoom&amp;rsquo;s tools, and with only the native shell tools instead of MindRoom&amp;rsquo;s. Hover for values.&lt;/figcaption&gt;&#10; &lt;noscript&gt;This chart needs JavaScript.&lt;/noscript&gt;&#10;&lt;/figure&gt;&#10;&lt;script type="module" src="https://www.nijho.lt/js/plot.7cb86dc2e3ef25b56bc93730b2620745a7f02b5715de87f94e61908f60e51690.js" integrity="sha256-fLhtwuPvJbVryTcwsmIHRafwK1cV3of5TmGQj2DlFpA=" crossorigin="anonymous"&gt;&lt;/script&gt;&#10;&lt;p&gt;With only MindRoom&amp;rsquo;s three shell tools, for running, checking, and stopping a command, and none of its file tools, the agent used 27 to 41% fewer tokens.&#10;It passed about as many runs: Luna passed 31 instead of 33, too small a difference to tell apart, and the other four models passed all 36.&lt;/p&gt;&#10;&lt;p&gt;For the native shape, I gave Claude only Claude Code&amp;rsquo;s &lt;code&gt;Bash&lt;/code&gt;, &lt;code&gt;BashOutput&lt;/code&gt;, and &lt;code&gt;KillShell&lt;/code&gt;, and GPT only Codex&amp;rsquo;s &lt;code&gt;exec_command&lt;/code&gt; and &lt;code&gt;write_stdin&lt;/code&gt;, with MindRoom&amp;rsquo;s &lt;code&gt;kill_shell_command&lt;/code&gt; in Codex&amp;rsquo;s style.&#10;For GPT, the total did not move: Astra, Sol, and Luna used the same number of tokens, within 2%, and made the same number of requests.&#10;Codex&amp;rsquo;s shell tools alone take about 130 fewer tokens to describe than MindRoom&amp;rsquo;s, and GPT spent about as much on extra work.&#10;Claude Sonnet 5.5 used 18% fewer tokens and Claude Opus 5.5 6% fewer, mostly because the Claude Code-style shell tools are shorter to describe than MindRoom&amp;rsquo;s.&lt;/p&gt;&#10;&#10;&lt;/details&gt;&#10;&#10;&lt;h3 id="minimal-mode-one-shell-tool-and-a-12-line-prompt"&gt;Minimal mode: one shell tool and a 12-line prompt &lt;a class="anchor" href="#minimal-mode-one-shell-tool-and-a-12-line-prompt" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;MindRoom&amp;rsquo;s &lt;a href="https://docs.mindroom.chat/tools/agent-cli/" target="_blank" rel="noopener"&gt;minimal mode&lt;/a&gt;, modeled on DeepSeek&amp;rsquo;s minimal profile, takes this all the way.&#10;The agent gets a 12-line prompt and a single &lt;code&gt;bash&lt;/code&gt; tool instead of its normal prompt and tools.&#10;Its instructions, skills, context files, and memory move behind a command-line program inside that shell, which it can call when it needs them.&#10;Minimal mode only works in chat, so I ran this comparison in Matrix conversations, against the same agent in standard mode with only its shell tools.&#10;A chat adds context about the room to every request, but even so, the minimal agent used 21 to 52% fewer tokens than the shell-only agent through MindRoom&amp;rsquo;s API.&lt;/p&gt;&#10;&lt;p&gt;The difference starts before the model does anything.&#10;For Claude Sonnet 5.5, the prompt and tool definitions sent with every request shrink from 4,285 tokens to 661.&lt;sup id="fnref:5"&gt;&lt;a href="#fn:5" class="footnote-ref" role="doc-noteref"&gt;5&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#10;&lt;figure class="plot-figure"&gt;&#10; &lt;div class="plot-container" role="img" aria-label="What every request carries besides the conversation: the system prompt and the tool definitions, in standard and in minimal mode, from each provider&amp;rsquo;s own token counts. Hover for values." data-plot-module="/post/native-harness-tools/plots.js" data-plot-name="promptParts"&gt;&lt;/div&gt;&#10; &lt;figcaption&gt;What every request carries besides the conversation: the system prompt and the tool definitions, in standard and in minimal mode, from each provider&amp;rsquo;s own token counts. Hover for values.&lt;/figcaption&gt;&#10; &lt;noscript&gt;This chart needs JavaScript.&lt;/noscript&gt;&#10;&lt;/figure&gt;&#10;&#10;&lt;script type="module" src="https://www.nijho.lt/js/plot.7cb86dc2e3ef25b56bc93730b2620745a7f02b5715de87f94e61908f60e51690.js" integrity="sha256-fLhtwuPvJbVryTcwsmIHRafwK1cV3of5TmGQj2DlFpA=" crossorigin="anonymous"&gt;&lt;/script&gt;&#10;&#10;&#10;&lt;figure class="plot-figure"&gt;&#10; &lt;div class="plot-container" role="img" aria-label="Tokens per task in Matrix conversations: the same agent with only MindRoom&amp;rsquo;s shell tools, in standard mode and in minimal mode with its single bash tool, split into the fixed part (light) and the work the model did on top of it (dark). Hover for values." data-plot-module="/post/native-harness-tools/plots.js" data-plot-name="minimalSplit"&gt;&lt;/div&gt;&#10; &lt;figcaption&gt;Tokens per task in Matrix conversations: the same agent with only MindRoom&amp;rsquo;s shell tools, in standard mode and in minimal mode with its single bash tool, split into the fixed part (light) and the work the model did on top of it (dark). Hover for values.&lt;/figcaption&gt;&#10; &lt;noscript&gt;This chart needs JavaScript.&lt;/noscript&gt;&#10;&lt;/figure&gt;&#10;&#10;&lt;script type="module" src="https://www.nijho.lt/js/plot.7cb86dc2e3ef25b56bc93730b2620745a7f02b5715de87f94e61908f60e51690.js" integrity="sha256-fLhtwuPvJbVryTcwsmIHRafwK1cV3of5TmGQj2DlFpA=" crossorigin="anonymous"&gt;&lt;/script&gt;&#10;&#10;&#10;&lt;p&gt;Each bar splits a task&amp;rsquo;s tokens into the fixed part, the prompt and tool definitions resent with every request, and the work the model did on top of it.&#10;The minimal agent used 58 to 76% fewer tokens than the same agent in standard mode with only its shell tools, for every model.&#10;Most of that is input the provider had cached and bills at a fraction of the price, so the bill shrinks less than the token count does: counting only uncached input and output, the minimal agent used 16 to 42% fewer tokens.&#10;And the model did not pay for it with extra work: the dark part of the bars stayed about the same or shrank, except for Luna&amp;rsquo;s.&#10;I had also hoped that the smaller agent would need less to do the task itself, but only GPT-6 Astra and Sol did, with slightly fewer steps and about a quarter less output; Claude worked exactly the same in both modes.&lt;/p&gt;&#10;&lt;p&gt;These tasks are short, three or four requests each, which is why the prompt weighs so much.&#10;I tried to make them harder so they would take more steps, but the models were so good that they only took about 50% more requests, and for the two models I tried, Claude Sonnet 5.5 and GPT-6 Astra, the pattern stayed the same: Sonnet did the same work in both modes, and Astra less in minimal mode.&#10;For the models that save steps, I see no reason why longer tasks would erase that gain: every step saved also saves resending the conversation, so on long tasks it counts for more.&#10;In a long session, the growing conversation dominates and the prompt&amp;rsquo;s share of the tokens shrinks, but its saving per request stays: about 3,600 tokens for Claude and 2,200 for GPT.&#10;And a real agent&amp;rsquo;s prompt carries far more instructions, skills, and memory than this test agent&amp;rsquo;s, so it saves more per request, although fetching them through the shell when needed costs requests of its own.&lt;/p&gt;&#10;&lt;details&gt;&#10; &lt;summary&gt;The numbers behind this section&lt;/summary&gt;&#10; &lt;p&gt;&lt;strong&gt;Why Matrix.&lt;/strong&gt;&#10;Minimal mode only works in chat conversations, so I ran it through Matrix, next to the same agent with only its shell tools in standard mode.&#10;Each run got a fresh chat room with only the agent, named &lt;code&gt;coder&lt;/code&gt;, and MindRoom&amp;rsquo;s router, which handles commands like &lt;code&gt;!mode&lt;/code&gt;; for minimal mode, I switched the room over with &lt;code&gt;!mode coder minimal&lt;/code&gt; before sending the task.&#10;In a Matrix conversation, the agent also gets context about the room and the conversation, so it uses more tokens than through the API: on the same code, with only the shell tools, Claude Opus 5.5 used 22,192 tokens per task in Matrix against 12,904 through the API.&#10;That is why I compare minimal mode with standard mode in Matrix.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;The prompt.&lt;/strong&gt;&#10;In standard mode, the system prompt is 2,295 tokens for Claude Sonnet 5.5 and 1,463 for GPT-6 Astra, and the tool definitions, the shell tools and one for inviting MindRoom&amp;rsquo;s router, add another 1,990 and 867.&#10;In minimal mode, the system prompt is 152 and 97 tokens, and the single &lt;code&gt;bash&lt;/code&gt; tool adds 509 and 72.&#10;This test agent&amp;rsquo;s standard prompt is about 100 lines only because its own configuration is one role line and one instruction; a real agent&amp;rsquo;s prompt also carries its instructions, skills, context files, and memory, and can run to hundreds of lines, while its minimal prompt stays at 12.&#10;The model receives all of that, plus the task and the room&amp;rsquo;s context, again with every request, so it adds up: in standard mode, about 80% of all tokens were this fixed part.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;The result.&lt;/strong&gt;&#10;Its first request dropped from about 4,600 to 1,000 input tokens for Claude, and from about 2,600 to 410 for GPT.&#10;Counting only the uncached input and the output, the minimal agent used 16 to 42% fewer tokens.&#10;Even with the extra context of a Matrix conversation, it used fewer tokens than the agent with only MindRoom&amp;rsquo;s shell tools through the API on the same code: 21 to 52% fewer.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Is that a fair comparison?&lt;/strong&gt;&#10;A shorter prompt saves tokens even if the model then has to work harder, so the real question is whether it had to.&#10;Mostly, it did not: the work stayed the same for both Claude models (1% and 3% less), and went down for Astra and Sol (38% and 13% less), which also needed fewer requests, about 3.0 per task instead of 3.3 to 3.4.&#10;Luna is the exception: it made more requests and did 40% more work in minimal mode, but the shorter prompt still more than paid for that.&#10;Counted per task without the resent conversation, the Claude models wrote and added to the conversation the same in both modes, Astra and Sol wrote about a quarter less and needed 0.2 to 0.4 fewer requests, and Luna added 33% more, mostly longer command output.&#10;Three of the five models failed one more run in minimal mode, mostly on the same script-writing task that other configurations also miss now and then.&#10;That is too small to tell apart here, but I will keep an eye on it with harder tasks.&lt;/p&gt;&#10;&#10;&lt;/details&gt;&#10;&#10;&lt;h3 id="minimal-mode-with-each-models-native-shell-tool"&gt;Minimal mode with each model&amp;rsquo;s native shell tool &lt;a class="anchor" href="#minimal-mode-with-each-models-native-shell-tool" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;That leaves the combination I had in mind from the start: the minimal agent, with each model&amp;rsquo;s native shell tool as its only tool.&#10;I patched minimal mode so that its single tool appears as Claude Code&amp;rsquo;s &lt;code&gt;Bash&lt;/code&gt; for Claude and as Codex&amp;rsquo;s &lt;code&gt;exec_command&lt;/code&gt; for GPT, with the same 12-line prompt.&lt;sup id="fnref:6"&gt;&lt;a href="#fn:6" class="footnote-ref" role="doc-noteref"&gt;6&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#10;&lt;figure class="plot-figure"&gt;&#10; &lt;div class="plot-container" role="img" aria-label="Change in tokens per task in minimal mode when its single tool is the model&amp;rsquo;s native shell tool, Claude Code&amp;rsquo;s Bash or Codex&amp;rsquo;s exec_command, instead of MindRoom&amp;rsquo;s bash, with 95% confidence intervals. The second row cuts the native tool&amp;rsquo;s output to the last 100 lines, MindRoom&amp;rsquo;s bash default. Hover for values." data-plot-module="/post/native-harness-tools/plots.js" data-plot-name="minimalNative"&gt;&lt;/div&gt;&#10; &lt;figcaption&gt;Change in tokens per task in minimal mode when its single tool is the model&amp;rsquo;s native shell tool, Claude Code&amp;rsquo;s Bash or Codex&amp;rsquo;s exec_command, instead of MindRoom&amp;rsquo;s bash, with 95% confidence intervals. The second row cuts the native tool&amp;rsquo;s output to the last 100 lines, MindRoom&amp;rsquo;s bash default. Hover for values.&lt;/figcaption&gt;&#10; &lt;noscript&gt;This chart needs JavaScript.&lt;/noscript&gt;&#10;&lt;/figure&gt;&#10;&#10;&lt;script type="module" src="https://www.nijho.lt/js/plot.7cb86dc2e3ef25b56bc93730b2620745a7f02b5715de87f94e61908f60e51690.js" integrity="sha256-fLhtwuPvJbVryTcwsmIHRafwK1cV3of5TmGQj2DlFpA=" crossorigin="anonymous"&gt;&lt;/script&gt;&#10;&#10;&#10;&lt;p&gt;It did not make the minimal agent better for any model.&#10;For Claude, it made little difference: Sonnet used about the same, and Opus a little more.&#10;For GPT, it was clearly worse, mostly because &lt;code&gt;exec_command&lt;/code&gt; hands back a command&amp;rsquo;s whole output, and in an agent that sends so little else, a few long outputs weigh a lot.&#10;With its output cut to 100 lines, &lt;code&gt;bash&lt;/code&gt;&amp;rsquo;s default and the light rows in the chart, only Sol still clearly used more; Astra&amp;rsquo;s and Luna&amp;rsquo;s smaller increases could be chance.&lt;/p&gt;&#10;&lt;p&gt;So the whole effect of the combination came from its minimal half: models that were trained with a carefully designed set of tools did best with one tool and almost no prompt, and the tool&amp;rsquo;s native shape did not make it better.&lt;/p&gt;&#10;&lt;details&gt;&#10; &lt;summary&gt;The numbers behind this section&lt;/summary&gt;&#10; &lt;p&gt;The single native tool only runs commands, but no current model ever polled or stopped a command in any of these runs, so it lacked nothing they used.&#10;I ran it next to minimal mode with MindRoom&amp;rsquo;s own &lt;code&gt;bash&lt;/code&gt; on the same code, and once more with the native tool&amp;rsquo;s output cut to the last 100 lines.&#10;That is &lt;code&gt;bash&lt;/code&gt;&amp;rsquo;s default, which the GPT models set themselves on every call, more often lower than higher; in the end, the capped native tool and &lt;code&gt;bash&lt;/code&gt; returned about as much, except for Astra, whose &lt;code&gt;bash&lt;/code&gt; results were twice as long.&lt;/p&gt;&#10;&lt;p&gt;For Claude, Sonnet used 4% fewer tokens with the native tool and Opus 7% more.&#10;For GPT, it was 34 to 46% more tokens, mostly because &lt;code&gt;exec_command&lt;/code&gt; returns a command&amp;rsquo;s whole output, so the models read 39 to 50 lines per result instead of 20 to 36.&#10;Cut to 100 lines, the native tool cost GPT 5 to 15% more, but only Sol&amp;rsquo;s increase is clearly more than chance; part of it is the definition, which takes about 90 more tokens than &lt;code&gt;bash&lt;/code&gt; on every request.&#10;In minimal mode, the agent sends so little else that a few long outputs weigh much more than through the API: the cap cut Astra&amp;rsquo;s tokens by about 20% here, against 4% there.&#10;Claude rarely printed more than 100 lines, so I would not read anything into the gap between its two native rows.&#10;The pass rates differed by at most a few runs, too few to tell apart.&lt;/p&gt;&#10;&#10;&lt;/details&gt;&#10;&#10;&lt;h2 id="what-this-does-and-does-not-show"&gt;What this does and does not show &lt;a class="anchor" href="#what-this-does-and-does-not-show" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;I tested the names and arguments of the tools, not whole harnesses. Claude Code and Codex also have their own tool descriptions, system prompts, and output formats, Codex has an interactive terminal, and RL trains all of that together. The full harness might still help today&amp;rsquo;s models; matching only the tools did not.&lt;/li&gt;&#10;&lt;li&gt;The tasks are easy and short: 97% of all runs passed, with three to seven requests per task on average. Harder, longer tasks might separate the tool sets on success, not only on cost.&lt;/li&gt;&#10;&lt;li&gt;With 36 runs per configuration, a 15 to 30% difference in tokens is clear, but a difference of one or two passed runs is not.&lt;/li&gt;&#10;&lt;li&gt;I tune MindRoom&amp;rsquo;s agent setup on other tasks from the same 12 families, and a note on working habits from that tuning sits in the shell tool&amp;rsquo;s description. Both tool sets carry the same note, so it should not favor either.&lt;/li&gt;&#10;&lt;li&gt;The confidence intervals cover run-to-run variation on these 12 tasks, not the choice of tasks. Resampling the tasks as well widens them: GPT-6 Astra&amp;rsquo;s +59%, for example, becomes +38 to +81%, and Sonnet 5.5&amp;rsquo;s 6% saving becomes indistinguishable from none. Astra and Sol still used more tokens with Codex&amp;rsquo;s tools on every one of the 12 tasks, and the minimal agent used fewer on every task, for every model.&lt;/li&gt;&#10;&lt;li&gt;Most runs used each model&amp;rsquo;s standard reasoning mode, which differs between generations: adaptive thinking for Sonnet 5 and the 5.5 models, none for Opus 4.7 and 4.8, and the effort Codex picks for GPT. I tried other settings on four models: two current ones at low and high effort, and Opus 4.7 and 4.8 with adaptive thinking. The pattern held at every effort: Astra used 27 to 45% more tokens with Codex&amp;rsquo;s tools, and Sonnet 5.5 stayed slightly cheaper with Claude Code&amp;rsquo;s.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="what-happens-to-the-pull-request"&gt;What happens to the pull request &lt;a class="anchor" href="#what-happens-to-the-pull-request" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The pull request is still unmerged, and given these results, I am not sure I will merge it at all.&#10;For today&amp;rsquo;s models, the native tools either cost more, as Codex&amp;rsquo;s did for GPT-6 Astra and Sol, or, as Claude Code&amp;rsquo;s did for Claude, only saved the few tokens of the shorter descriptions I wrote for them, which MindRoom&amp;rsquo;s own tools could get too.&#10;The one model that clearly did better with its own tools, Claude Opus 4.8, is a generation behind.&#10;What I will do is use minimal mode a lot more, with MindRoom&amp;rsquo;s own &lt;code&gt;bash&lt;/code&gt;.&lt;/p&gt;&#10;&lt;h2 id="why-this-excites-me"&gt;Why this excites me &lt;a class="anchor" href="#why-this-excites-me" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Half of my plan was wrong, and I am happy about that.&#10;The minimal-harness, DeepSeek-style half held up; the native-tools half did not.&#10;The benchmarks I did not believe were right, at least for these models.&#10;It suggests that these models generalize much better than I gave them credit for.&#10;They were trained with one specific set of tools, and on these tasks they did just as well with tools they had presumably never seen in training, as long as those tools were simple, like an edit tool that takes one path, the old text, and the new text.&#10;Only Opus 4.8, the model that started all this, still did better with its native tools.&#10;What matters more than familiarity is how much the agent sends with every request: the prompt and the definition of every tool.&lt;/p&gt;&#10;&lt;p&gt;It also changes how I think about who gets to build the best agents.&#10;If models only worked well in the harness they were trained in, the labs would own the best agents by default.&#10;Instead, at least the skill of using unfamiliar tools seems to carry over to other harnesses.&#10;I suspect the same holds one level up, for how several agents work together.&#10;The labs presumably train their models in their own harness, but if what the models learn transfers this well, a harness built outside the labs, like MindRoom, could get just as good at letting agents collaborate.&#10;That is still a hunch, and testing it is what I want to do next.&lt;/p&gt;&#10;&lt;h2 id="appendix-how-i-measured-and-the-numbers-behind-the-charts"&gt;Appendix: how I measured, and the numbers behind the charts &lt;a class="anchor" href="#appendix-how-i-measured-and-the-numbers-behind-the-charts" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;All scripts, the tasks, and one row per trial, with its reasoning setting, are &lt;a href="https://github.com/basnijholt/nijho.lt/tree/main/content/post/native-harness-tools/reproduce" target="_blank" rel="noopener"&gt;on GitHub next to this post&amp;rsquo;s source&lt;/a&gt;.&lt;/p&gt;&#10;&lt;details&gt;&#10; &lt;summary&gt;Show the setup and every configuration&lt;/summary&gt;&#10; &lt;p&gt;&lt;strong&gt;Setup&lt;/strong&gt;&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Each configuration ran as a separate MindRoom instance with one agent and a fresh Docker container for its commands. The model, the tools, and everything else were fixed in that instance&amp;rsquo;s configuration.&lt;/li&gt;&#10;&lt;li&gt;The tool comparisons ran through MindRoom&amp;rsquo;s OpenAI-compatible API on the pull request at commit &lt;code&gt;d73aafb51&lt;/code&gt;: the matching sets, the mixed sets with whole and with 100-line output, and both shell-only setups. The capped run changed only the output limit of the native shell tools.&lt;/li&gt;&#10;&lt;li&gt;The minimal-mode runs and their standard-mode comparison ran through Matrix on MindRoom&amp;rsquo;s main branch at release &lt;code&gt;v2026.10.228&lt;/code&gt;, whose shell tools lack two arguments the pull request added, a working directory and a wait. A shell-only run through the API on that release used within 3% of the pull request&amp;rsquo;s tokens for every model except Luna, which used 8% fewer.&lt;/li&gt;&#10;&lt;li&gt;The combination ran through Matrix on the pull request with an experiment patch that shows minimal mode&amp;rsquo;s single tool in the model&amp;rsquo;s own dialect. On that code, minimal mode with MindRoom&amp;rsquo;s &lt;code&gt;bash&lt;/code&gt; used within 10% of its tokens on main for every model.&lt;/li&gt;&#10;&lt;li&gt;Tokens per task are the input and output tokens of every model request in that task, from MindRoom&amp;rsquo;s per-request usage logs. The work is what is left after subtracting the fixed part, the first request&amp;rsquo;s input times the number of requests.&lt;/li&gt;&#10;&lt;li&gt;The confidence intervals come from resampling the three runs of each task 5,000 times, keeping the mix of tasks fixed.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Each cell shows passed runs out of 36, then tokens per task; the work columns show how much the work changed with the native tools.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Matching sets: each harness&amp;rsquo;s own tools against MindRoom&amp;rsquo;s matching set (pull request, through MindRoom&amp;rsquo;s API)&lt;/strong&gt;&lt;/p&gt;&#10;&lt;div class="table-wrap"&gt;&#10;&lt;table&gt;&#10;&lt;thead&gt;&#10;&lt;tr&gt;&#10;&lt;th&gt;Model&lt;/th&gt;&#10;&lt;th&gt;Reasoning&lt;/th&gt;&#10;&lt;th&gt;MindRoom&amp;rsquo;s set&lt;/th&gt;&#10;&lt;th&gt;Harness&amp;rsquo;s own set&lt;/th&gt;&#10;&lt;th&gt;Work with the harness&amp;rsquo;s set&lt;/th&gt;&#10;&lt;/tr&gt;&#10;&lt;/thead&gt;&#10;&lt;tbody&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Opus 5.5&lt;/td&gt;&#10;&lt;td&gt;adaptive thinking&lt;/td&gt;&#10;&lt;td&gt;36/36 · 15,661&lt;/td&gt;&#10;&lt;td&gt;35/36 · 13,628 (−13%)&lt;/td&gt;&#10;&lt;td&gt;+7%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Sonnet 5.5&lt;/td&gt;&#10;&lt;td&gt;adaptive thinking&lt;/td&gt;&#10;&lt;td&gt;36/36 · 14,606&lt;/td&gt;&#10;&lt;td&gt;36/36 · 13,764 (−6%)&lt;/td&gt;&#10;&lt;td&gt;+15%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6 Astra&lt;/td&gt;&#10;&lt;td&gt;Codex&amp;rsquo;s choice&lt;/td&gt;&#10;&lt;td&gt;36/36 · 7,041&lt;/td&gt;&#10;&lt;td&gt;36/36 · 11,206 (+59%)&lt;/td&gt;&#10;&lt;td&gt;+84%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6.1 Sol&lt;/td&gt;&#10;&lt;td&gt;Codex&amp;rsquo;s choice&lt;/td&gt;&#10;&lt;td&gt;36/36 · 7,292&lt;/td&gt;&#10;&lt;td&gt;36/36 · 10,417 (+43%)&lt;/td&gt;&#10;&lt;td&gt;+60%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6 Luna&lt;/td&gt;&#10;&lt;td&gt;Codex&amp;rsquo;s choice&lt;/td&gt;&#10;&lt;td&gt;35/36 · 8,425&lt;/td&gt;&#10;&lt;td&gt;34/36 · 8,638 (+3%)&lt;/td&gt;&#10;&lt;td&gt;−5%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Opus 4.7&lt;/td&gt;&#10;&lt;td&gt;no thinking&lt;/td&gt;&#10;&lt;td&gt;34/36 · 24,398&lt;/td&gt;&#10;&lt;td&gt;33/36 · 23,564 (−3%)&lt;/td&gt;&#10;&lt;td&gt;+13%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Opus 4.8&lt;/td&gt;&#10;&lt;td&gt;no thinking&lt;/td&gt;&#10;&lt;td&gt;33/36 · 24,103&lt;/td&gt;&#10;&lt;td&gt;34/36 · 19,593 (−19%)&lt;/td&gt;&#10;&lt;td&gt;−17%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Sonnet 5&lt;/td&gt;&#10;&lt;td&gt;adaptive thinking&lt;/td&gt;&#10;&lt;td&gt;33/36 · 29,781&lt;/td&gt;&#10;&lt;td&gt;35/36 · 27,833 (−7%)&lt;/td&gt;&#10;&lt;td&gt;+9%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-5.5&lt;/td&gt;&#10;&lt;td&gt;Codex&amp;rsquo;s choice&lt;/td&gt;&#10;&lt;td&gt;35/36 · 10,819&lt;/td&gt;&#10;&lt;td&gt;35/36 · 11,353 (+5%)&lt;/td&gt;&#10;&lt;td&gt;+2%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-5.6 Sol&lt;/td&gt;&#10;&lt;td&gt;Codex&amp;rsquo;s choice&lt;/td&gt;&#10;&lt;td&gt;36/36 · 10,624&lt;/td&gt;&#10;&lt;td&gt;34/36 · 10,991 (+3%)&lt;/td&gt;&#10;&lt;td&gt;−5%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;For Claude, both sets have a shell and tools to read, edit, and write files; for GPT, a shell and Codex&amp;rsquo;s &lt;code&gt;apply_patch&lt;/code&gt; against MindRoom&amp;rsquo;s tools to edit and write files. Neither has MindRoom&amp;rsquo;s &lt;code&gt;grep&lt;/code&gt;, &lt;code&gt;find_files&lt;/code&gt;, or &lt;code&gt;ls&lt;/code&gt;.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Mixed sets: native tools against MindRoom&amp;rsquo;s tools (pull request, through MindRoom&amp;rsquo;s API; Claude with adaptive thinking, GPT with the effort Codex picks)&lt;/strong&gt;&lt;/p&gt;&#10;&lt;div class="table-wrap"&gt;&#10;&lt;table&gt;&#10;&lt;thead&gt;&#10;&lt;tr&gt;&#10;&lt;th&gt;Model&lt;/th&gt;&#10;&lt;th&gt;MindRoom&amp;rsquo;s tools&lt;/th&gt;&#10;&lt;th&gt;Native tools&lt;/th&gt;&#10;&lt;th&gt;Native tools, 100-line output&lt;/th&gt;&#10;&lt;th&gt;Work with native tools&lt;/th&gt;&#10;&lt;/tr&gt;&#10;&lt;/thead&gt;&#10;&lt;tbody&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Opus 5.5&lt;/td&gt;&#10;&lt;td&gt;36/36 · 18,943&lt;/td&gt;&#10;&lt;td&gt;36/36 · 17,244 (−9%)&lt;/td&gt;&#10;&lt;td&gt;36/36 · 17,410 (−8%)&lt;/td&gt;&#10;&lt;td&gt;+5%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Sonnet 5.5&lt;/td&gt;&#10;&lt;td&gt;36/36 · 17,765&lt;/td&gt;&#10;&lt;td&gt;36/36 · 16,237 (−9%)&lt;/td&gt;&#10;&lt;td&gt;36/36 · 16,399 (−8%)&lt;/td&gt;&#10;&lt;td&gt;−4%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6 Astra&lt;/td&gt;&#10;&lt;td&gt;35/36 · 8,250&lt;/td&gt;&#10;&lt;td&gt;36/36 · 10,807 (+31%)&lt;/td&gt;&#10;&lt;td&gt;35/36 · 10,399 (+26%)&lt;/td&gt;&#10;&lt;td&gt;+51%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6.1 Sol&lt;/td&gt;&#10;&lt;td&gt;36/36 · 8,873&lt;/td&gt;&#10;&lt;td&gt;36/36 · 10,534 (+19%)&lt;/td&gt;&#10;&lt;td&gt;36/36 · 10,239 (+15%)&lt;/td&gt;&#10;&lt;td&gt;+24%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6 Luna&lt;/td&gt;&#10;&lt;td&gt;33/36 · 12,003&lt;/td&gt;&#10;&lt;td&gt;35/36 · 11,532 (−4%)&lt;/td&gt;&#10;&lt;td&gt;36/36 · 10,816 (−10%)&lt;/td&gt;&#10;&lt;td&gt;+15%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;&lt;strong&gt;Older models, mixed sets: native tools against MindRoom&amp;rsquo;s tools (pull request, through MindRoom&amp;rsquo;s API)&lt;/strong&gt;&lt;/p&gt;&#10;&lt;div class="table-wrap"&gt;&#10;&lt;table&gt;&#10;&lt;thead&gt;&#10;&lt;tr&gt;&#10;&lt;th&gt;Model&lt;/th&gt;&#10;&lt;th&gt;Reasoning&lt;/th&gt;&#10;&lt;th&gt;MindRoom&amp;rsquo;s tools&lt;/th&gt;&#10;&lt;th&gt;Native tools&lt;/th&gt;&#10;&lt;th&gt;Work with native tools&lt;/th&gt;&#10;&lt;/tr&gt;&#10;&lt;/thead&gt;&#10;&lt;tbody&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Opus 4.7&lt;/td&gt;&#10;&lt;td&gt;no thinking&lt;/td&gt;&#10;&lt;td&gt;34/36 · 33,140&lt;/td&gt;&#10;&lt;td&gt;33/36 · 25,793 (−22%)&lt;/td&gt;&#10;&lt;td&gt;−26%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Opus 4.8&lt;/td&gt;&#10;&lt;td&gt;no thinking&lt;/td&gt;&#10;&lt;td&gt;33/36 · 32,219&lt;/td&gt;&#10;&lt;td&gt;34/36 · 23,843 (−26%)&lt;/td&gt;&#10;&lt;td&gt;−32%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Sonnet 5&lt;/td&gt;&#10;&lt;td&gt;adaptive thinking&lt;/td&gt;&#10;&lt;td&gt;33/36 · 42,349&lt;/td&gt;&#10;&lt;td&gt;34/36 · 27,120 (−36%)&lt;/td&gt;&#10;&lt;td&gt;−45%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-5.5&lt;/td&gt;&#10;&lt;td&gt;Codex&amp;rsquo;s choice&lt;/td&gt;&#10;&lt;td&gt;34/36 · 15,007&lt;/td&gt;&#10;&lt;td&gt;36/36 · 14,419 (−4%)&lt;/td&gt;&#10;&lt;td&gt;−11%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-5.6 Sol&lt;/td&gt;&#10;&lt;td&gt;Codex&amp;rsquo;s choice&lt;/td&gt;&#10;&lt;td&gt;36/36 · 15,062&lt;/td&gt;&#10;&lt;td&gt;35/36 · 12,809 (−15%)&lt;/td&gt;&#10;&lt;td&gt;−27%&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;&lt;strong&gt;Older models, only the shell tools: native shape against MindRoom&amp;rsquo;s (pull request, through MindRoom&amp;rsquo;s API; Opus 4.7 and 4.8 without thinking, Sonnet 5 with adaptive thinking, GPT with the effort Codex picks)&lt;/strong&gt;&lt;/p&gt;&#10;&lt;div class="table-wrap"&gt;&#10;&lt;table&gt;&#10;&lt;thead&gt;&#10;&lt;tr&gt;&#10;&lt;th&gt;Model&lt;/th&gt;&#10;&lt;th&gt;MindRoom&amp;rsquo;s shell&lt;/th&gt;&#10;&lt;th&gt;Native shell&lt;/th&gt;&#10;&lt;/tr&gt;&#10;&lt;/thead&gt;&#10;&lt;tbody&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Opus 4.7&lt;/td&gt;&#10;&lt;td&gt;33/36 · 17,518&lt;/td&gt;&#10;&lt;td&gt;33/36 · 15,714 (−10%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Opus 4.8&lt;/td&gt;&#10;&lt;td&gt;35/36 · 19,183&lt;/td&gt;&#10;&lt;td&gt;33/36 · 14,686 (−23%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Sonnet 5&lt;/td&gt;&#10;&lt;td&gt;33/36 · 22,624&lt;/td&gt;&#10;&lt;td&gt;33/36 · 28,354 (+25%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-5.5&lt;/td&gt;&#10;&lt;td&gt;36/36 · 9,056&lt;/td&gt;&#10;&lt;td&gt;36/36 · 9,046 (0%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-5.6 Sol&lt;/td&gt;&#10;&lt;td&gt;36/36 · 9,171&lt;/td&gt;&#10;&lt;td&gt;34/36 · 8,658 (−6%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;Sonnet 5&amp;rsquo;s native mean comes from one run that cost 271,106 tokens, after a 50 KB command output; its median is 9% lower with the native shell.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Opus 4.7 and 4.8 with adaptive thinking, mixed sets: native tools against MindRoom&amp;rsquo;s tools (pull request, through MindRoom&amp;rsquo;s API)&lt;/strong&gt;&lt;/p&gt;&#10;&lt;div class="table-wrap"&gt;&#10;&lt;table&gt;&#10;&lt;thead&gt;&#10;&lt;tr&gt;&#10;&lt;th&gt;Model&lt;/th&gt;&#10;&lt;th&gt;Thinking replies&lt;/th&gt;&#10;&lt;th&gt;MindRoom&amp;rsquo;s tools&lt;/th&gt;&#10;&lt;th&gt;Native tools&lt;/th&gt;&#10;&lt;/tr&gt;&#10;&lt;/thead&gt;&#10;&lt;tbody&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Opus 4.7&lt;/td&gt;&#10;&lt;td&gt;26% and 31%&lt;/td&gt;&#10;&lt;td&gt;35/36 · 35,610&lt;/td&gt;&#10;&lt;td&gt;33/36 · 23,090 (−35%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Opus 4.8&lt;/td&gt;&#10;&lt;td&gt;36% and 30%&lt;/td&gt;&#10;&lt;td&gt;33/36 · 25,269&lt;/td&gt;&#10;&lt;td&gt;33/36 · 20,130 (−20%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;&lt;strong&gt;Reasoning effort, mixed sets: native tools against MindRoom&amp;rsquo;s tools (pull request, through MindRoom&amp;rsquo;s API)&lt;/strong&gt;&lt;/p&gt;&#10;&lt;div class="table-wrap"&gt;&#10;&lt;table&gt;&#10;&lt;thead&gt;&#10;&lt;tr&gt;&#10;&lt;th&gt;Model&lt;/th&gt;&#10;&lt;th&gt;Reasoning effort&lt;/th&gt;&#10;&lt;th&gt;MindRoom&amp;rsquo;s tools&lt;/th&gt;&#10;&lt;th&gt;Native tools&lt;/th&gt;&#10;&lt;/tr&gt;&#10;&lt;/thead&gt;&#10;&lt;tbody&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Sonnet 5.5&lt;/td&gt;&#10;&lt;td&gt;low&lt;/td&gt;&#10;&lt;td&gt;36/36 · 15,154&lt;/td&gt;&#10;&lt;td&gt;36/36 · 12,330 (−19%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Sonnet 5.5&lt;/td&gt;&#10;&lt;td&gt;default&lt;/td&gt;&#10;&lt;td&gt;36/36 · 17,765&lt;/td&gt;&#10;&lt;td&gt;36/36 · 16,237 (−9%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Sonnet 5.5&lt;/td&gt;&#10;&lt;td&gt;high&lt;/td&gt;&#10;&lt;td&gt;36/36 · 18,286&lt;/td&gt;&#10;&lt;td&gt;36/36 · 15,630 (−15%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6 Astra&lt;/td&gt;&#10;&lt;td&gt;low&lt;/td&gt;&#10;&lt;td&gt;36/36 · 8,361&lt;/td&gt;&#10;&lt;td&gt;36/36 · 10,627 (+27%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6 Astra&lt;/td&gt;&#10;&lt;td&gt;default&lt;/td&gt;&#10;&lt;td&gt;35/36 · 8,250&lt;/td&gt;&#10;&lt;td&gt;36/36 · 10,807 (+31%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6 Astra&lt;/td&gt;&#10;&lt;td&gt;high&lt;/td&gt;&#10;&lt;td&gt;36/36 · 8,934&lt;/td&gt;&#10;&lt;td&gt;36/36 · 12,918 (+45%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;&lt;strong&gt;Only the shell tools (pull request, through MindRoom&amp;rsquo;s API; Claude with adaptive thinking, GPT with the effort Codex picks)&lt;/strong&gt;&lt;/p&gt;&#10;&lt;div class="table-wrap"&gt;&#10;&lt;table&gt;&#10;&lt;thead&gt;&#10;&lt;tr&gt;&#10;&lt;th&gt;Model&lt;/th&gt;&#10;&lt;th&gt;All of MindRoom&amp;rsquo;s tools&lt;/th&gt;&#10;&lt;th&gt;MindRoom&amp;rsquo;s shell only&lt;/th&gt;&#10;&lt;th&gt;Native shell only&lt;/th&gt;&#10;&lt;/tr&gt;&#10;&lt;/thead&gt;&#10;&lt;tbody&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Opus 5.5&lt;/td&gt;&#10;&lt;td&gt;36/36 · 18,943&lt;/td&gt;&#10;&lt;td&gt;36/36 · 12,926 (−32%)&lt;/td&gt;&#10;&lt;td&gt;36/36 · 12,202 (−6%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Sonnet 5.5&lt;/td&gt;&#10;&lt;td&gt;36/36 · 17,765&lt;/td&gt;&#10;&lt;td&gt;36/36 · 12,455 (−30%)&lt;/td&gt;&#10;&lt;td&gt;36/36 · 10,168 (−18%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6 Astra&lt;/td&gt;&#10;&lt;td&gt;35/36 · 8,250&lt;/td&gt;&#10;&lt;td&gt;36/36 · 6,025 (−27%)&lt;/td&gt;&#10;&lt;td&gt;36/36 · 6,052 (0%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6.1 Sol&lt;/td&gt;&#10;&lt;td&gt;36/36 · 8,873&lt;/td&gt;&#10;&lt;td&gt;36/36 · 6,195 (−30%)&lt;/td&gt;&#10;&lt;td&gt;36/36 · 6,177 (0%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6 Luna&lt;/td&gt;&#10;&lt;td&gt;33/36 · 12,003&lt;/td&gt;&#10;&lt;td&gt;31/36 · 7,118 (−41%)&lt;/td&gt;&#10;&lt;td&gt;34/36 · 7,018 (−1%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;MindRoom&amp;rsquo;s shell alone is compared with all of MindRoom&amp;rsquo;s tools, and the native shell with MindRoom&amp;rsquo;s shell.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Minimal mode against standard mode (main branch, through Matrix, shell tools only; Claude with adaptive thinking, GPT with the effort Codex picks)&lt;/strong&gt;&lt;/p&gt;&#10;&lt;div class="table-wrap"&gt;&#10;&lt;table&gt;&#10;&lt;thead&gt;&#10;&lt;tr&gt;&#10;&lt;th&gt;Model&lt;/th&gt;&#10;&lt;th&gt;Standard mode&lt;/th&gt;&#10;&lt;th&gt;Minimal mode&lt;/th&gt;&#10;&lt;/tr&gt;&#10;&lt;/thead&gt;&#10;&lt;tbody&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Opus 5.5&lt;/td&gt;&#10;&lt;td&gt;36/36 · 22,192&lt;/td&gt;&#10;&lt;td&gt;36/36 · 8,030 (−64%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Sonnet 5.5&lt;/td&gt;&#10;&lt;td&gt;35/36 · 22,448&lt;/td&gt;&#10;&lt;td&gt;34/36 · 7,828 (−65%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6 Astra&lt;/td&gt;&#10;&lt;td&gt;36/36 · 11,429&lt;/td&gt;&#10;&lt;td&gt;36/36 · 2,798 (−76%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6.1 Sol&lt;/td&gt;&#10;&lt;td&gt;36/36 · 11,070&lt;/td&gt;&#10;&lt;td&gt;35/36 · 3,370 (−70%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6 Luna&lt;/td&gt;&#10;&lt;td&gt;35/36 · 12,568&lt;/td&gt;&#10;&lt;td&gt;34/36 · 5,219 (−58%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;&lt;strong&gt;Minimal mode: the native tool against MindRoom&amp;rsquo;s &lt;code&gt;bash&lt;/code&gt; (pull request with the experiment patch, through Matrix; Claude with adaptive thinking, GPT with the effort Codex picks)&lt;/strong&gt;&lt;/p&gt;&#10;&lt;div class="table-wrap"&gt;&#10;&lt;table&gt;&#10;&lt;thead&gt;&#10;&lt;tr&gt;&#10;&lt;th&gt;Model&lt;/th&gt;&#10;&lt;th&gt;MindRoom&amp;rsquo;s &lt;code&gt;bash&lt;/code&gt;&lt;/th&gt;&#10;&lt;th&gt;Native tool&lt;/th&gt;&#10;&lt;th&gt;Native tool, 100-line output&lt;/th&gt;&#10;&lt;/tr&gt;&#10;&lt;/thead&gt;&#10;&lt;tbody&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Opus 5.5&lt;/td&gt;&#10;&lt;td&gt;36/36 · 8,058&lt;/td&gt;&#10;&lt;td&gt;36/36 · 8,654 (+7%)&lt;/td&gt;&#10;&lt;td&gt;36/36 · 9,123 (+13%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;Claude Sonnet 5.5&lt;/td&gt;&#10;&lt;td&gt;34/36 · 7,787&lt;/td&gt;&#10;&lt;td&gt;34/36 · 7,514 (−4%)&lt;/td&gt;&#10;&lt;td&gt;34/36 · 8,000 (+3%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6 Astra&lt;/td&gt;&#10;&lt;td&gt;35/36 · 3,071&lt;/td&gt;&#10;&lt;td&gt;36/36 · 4,173 (+36%)&lt;/td&gt;&#10;&lt;td&gt;36/36 · 3,359 (+9%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6.1 Sol&lt;/td&gt;&#10;&lt;td&gt;34/36 · 3,103&lt;/td&gt;&#10;&lt;td&gt;33/36 · 4,150 (+34%)&lt;/td&gt;&#10;&lt;td&gt;36/36 · 3,575 (+15%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;GPT-6 Luna&lt;/td&gt;&#10;&lt;td&gt;34/36 · 4,697&lt;/td&gt;&#10;&lt;td&gt;34/36 · 6,849 (+46%)&lt;/td&gt;&#10;&lt;td&gt;32/36 · 4,926 (+5%)&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;One of Luna&amp;rsquo;s runs with the whole native output counts for passes but not for tokens: the provider reported no usage for one of its requests.&lt;/p&gt;&#10;&#10;&lt;/details&gt;&#10;&#10;&lt;div class="footnotes" role="doc-endnotes"&gt;&#10;&lt;hr&gt;&#10;&lt;ol&gt;&#10;&lt;li id="fn:1"&gt;&#10;&lt;p&gt;Armin also found that Anthropic&amp;rsquo;s strict tool mode, which restricts the model&amp;rsquo;s output to the tool&amp;rsquo;s schema, made these failures disappear in his tests. Pi later turned it on for Claude models, and a pi user then &lt;a href="https://github.com/earendil-works/pi/issues/10074#issuecomment-6000381416" target="_blank" rel="noopener"&gt;linked a different problem to it&lt;/a&gt;: in that user&amp;rsquo;s logs, 9.5% of Claude&amp;rsquo;s edits had mangled &lt;code&gt;\u&lt;/code&gt; escapes for non-ASCII text, such as Korean, with strict mode on, and 1.5% with it off.&amp;#160;&lt;a href="#fnref:1" class="footnote-backref" role="doc-backlink"&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#10;&lt;/li&gt;&#10;&lt;li id="fn:2"&gt;&#10;&lt;p&gt;The 12 tasks come from 12 families: a CSV report, finding the commit that broke a check, renaming an API across a package, counting errors in log files, fixing failing tests, finding files, extracting fields from JSON, writing a shell script, editing a configuration file, counting matching lines in very long command output, unpacking nested archives, and deduplicating and merging data files. I tune MindRoom&amp;rsquo;s agent setup on other instances of these families, and these 12 were held out from that.&amp;#160;&lt;a href="#fnref:2" class="footnote-backref" role="doc-backlink"&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#10;&lt;/li&gt;&#10;&lt;li id="fn:3"&gt;&#10;&lt;p&gt;Claude and GPT count tokens differently, so compare the numbers within one model, not across models. Cached input counts in full here, although providers bill it at a fraction of the price, so a bill changes less than the token count.&amp;#160;&lt;a href="#fnref:3" class="footnote-backref" role="doc-backlink"&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#10;&lt;/li&gt;&#10;&lt;li id="fn:4"&gt;&#10;&lt;p&gt;MindRoom&amp;rsquo;s toolkits accept &lt;code&gt;exclude_tools&lt;/code&gt;, so both sets drop MindRoom&amp;rsquo;s &lt;code&gt;grep&lt;/code&gt;, &lt;code&gt;find_files&lt;/code&gt;, and &lt;code&gt;ls&lt;/code&gt;, and for GPT also &lt;code&gt;read_file&lt;/code&gt;, since Codex reads files through the shell. Both keep their shell&amp;rsquo;s tools for checking on and stopping a background command, which no model used in the matching-set runs.&amp;#160;&lt;a href="#fnref:4" class="footnote-backref" role="doc-backlink"&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#10;&lt;/li&gt;&#10;&lt;li id="fn:5"&gt;&#10;&lt;p&gt;Anthropic adds its own instructions for tool use to every request that has tools, which is why MindRoom&amp;rsquo;s single &lt;code&gt;bash&lt;/code&gt; tool costs Claude 509 tokens. I measured all of these numbers by sending each part on its own and reading the input tokens the provider reported.&amp;#160;&lt;a href="#fnref:5" class="footnote-backref" role="doc-backlink"&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#10;&lt;/li&gt;&#10;&lt;li id="fn:6"&gt;&#10;&lt;p&gt;The patch is with this post&amp;rsquo;s reproduction scripts. It shows minimal mode&amp;rsquo;s single tool as MindRoom&amp;rsquo;s canonical run function, which the tool dialect then presents as &lt;code&gt;Bash&lt;/code&gt; or &lt;code&gt;exec_command&lt;/code&gt;; nothing else about minimal mode changes.&amp;#160;&lt;a href="#fnref:6" class="footnote-backref" role="doc-backlink"&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#10;&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/div&gt;&#10;</description></item><item><title>How to start with AI</title><link>https://www.nijho.lt/post/how-to-start-with-ai/</link><pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate><guid isPermaLink="false">/post/how-to-start-with-ai/</guid><description>&lt;p&gt;Recently, on a train, I sat near someone typing code by hand for hours.&#10;At the same time, I was orchestrating more than ten agents just by talking to my phone.&#10;I felt like I was living in a different world.&#10;It made me realize my own bias.&#10;I had just assumed that by now everyone would have AI write their code.&lt;/p&gt;&#10;&lt;p&gt;So maybe I shouldn&amp;rsquo;t be surprised that I still get asked: &amp;ldquo;how do I start with AI?&amp;rdquo; or &amp;ldquo;how do I start with coding agents?&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;There is a lot of noise, and a lot of pretense, about very specific workflows.&#10;Multi-agent loops, agent and sub-agent graphs, carefully tuned rule files.&#10;None of that is useful for 99% of people.&lt;/p&gt;&#10;&lt;p&gt;You don&amp;rsquo;t need skills.&#10;You don&amp;rsquo;t need an &lt;code&gt;AGENTS.md&lt;/code&gt;.&#10;You don&amp;rsquo;t need anything except the app itself.&#10;You just need to ask questions, and be critical of the answers.&lt;/p&gt;&#10;&lt;p&gt;Most of my examples come from code, because that is where I use AI the most.&#10;But the advice is the same whether you write software or not.&lt;/p&gt;&#10;&lt;aside class="callout callout-note"&gt;&lt;svg class="ico" viewBox="0 0 256 256" aria-hidden="true"&gt;&lt;path d="M128,24A104,104,0,1,0,232,128,104.11,104.11,0,0,0,128,24Zm0,192a88,88,0,1,1,88-88A88.1,88.1,0,0,1,128,216Zm16-40a8,8,0,0,1-8,8,16,16,0,0,1-16-16V128a8,8,0,0,1,0-16,16,16,0,0,1,16,16v40A8,8,0,0,1,144,176ZM112,84a12,12,0,1,1,12,12A12,12,0,0,1,112,84Z"/&gt;&lt;/svg&gt;&lt;div&gt;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt;&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Install Claude or ChatGPT. The app if you want to chat, Claude Code or Codex in your terminal if you write code. It takes 30 seconds. No setup.&lt;/li&gt;&#10;&lt;li&gt;Ask it everything, and be critical of what comes back. Don&amp;rsquo;t do anything it could do itself, and tell it so.&lt;/li&gt;&#10;&lt;li&gt;Use the best model. Cheap models are often not cheaper on real work.&lt;/li&gt;&#10;&lt;li&gt;Trust it in proportion to how measurable the outcome is.&lt;/li&gt;&#10;&lt;li&gt;Have its work reviewed in a fresh context, by the same model and by another one. Watch for scope creep.&lt;/li&gt;&#10;&lt;li&gt;Skills, multi-agent loops and the rest come later, if ever.&lt;/li&gt;&#10;&lt;/ol&gt;&lt;/div&gt;&lt;/aside&gt;&#10;&lt;details class="toc" open&gt;&lt;summary&gt;Table of contents&lt;/summary&gt;&lt;nav id="TableOfContents"&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#1-install-it-and-thats-it"&gt;1. Install it, and that&amp;rsquo;s it&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#2-ask-it-everything-"&gt;2. Ask it everything 🥩&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#3-use-the-best-model"&gt;3. Use the best model&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#4-decide-how-much-to-trust-it"&gt;4. Decide how much to trust it&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#5-talk-to-it-then-make-it-review-itself"&gt;5. Talk to it, then make it review itself&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#6-what-about-skills-and-multi-agent-loops"&gt;6. What about skills and multi-agent loops?&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#7-if-you-write-code"&gt;7. If you write code&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#tests-are-cheap-now-so-ask-for-them"&gt;Tests are cheap now, so ask for them&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-code-is-the-spec"&gt;The code is the spec&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#review-against-your-own-criteria"&gt;Review against your own criteria&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#cross-model-review-needs-two-installs"&gt;Cross-model review needs two installs&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#a-good-ai-engineer-is-just-a-good-engineer"&gt;A good AI engineer is just a good engineer&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#your-role-changed-it-didnt-disappear"&gt;Your role changed, it didn&amp;rsquo;t disappear&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#this-post-has-an-expiry-date"&gt;This post has an expiry date&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10;&lt;/nav&gt;&lt;/details&gt;&#10;&#10;&lt;h2 id="1-install-it-and-thats-it"&gt;1. Install it, and that&amp;rsquo;s it &lt;a class="anchor" href="#1-install-it-and-thats-it" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Getting started is downloading the ChatGPT or Claude app, or literally a one-liner to install Claude Code or Codex if you write code.&#10;Maybe you log in, or click a button to get access.&#10;That&amp;rsquo;s the whole setup.&#10;&amp;ldquo;I need to take time to learn how to use it&amp;rdquo; was never a real barrier.&#10;The interface is trivial: text in, text out.&#10;Everything else is optional.&lt;/p&gt;&#10;&lt;p&gt;I open agents in projects of mine that have never seen any AI, and seconds later they know the entire thing.&#10;The frontier models have much better taste than they used to.&#10;In an established codebase they just follow the existing style.&#10;If you point one at a codebase that is a bunch of crap, it might still produce a bunch of crap.&#10;But even there it does better than it used to.&lt;/p&gt;&#10;&lt;p&gt;I used to give different advice.&#10;In &lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;On agentic coding&lt;/a&gt;, a year ago, I told you to create a &lt;code&gt;CLAUDE.md&lt;/code&gt; in every project root with your preferences.&#10;(Today that would be an &lt;code&gt;AGENTS.md&lt;/code&gt;, which all the major agents read.)&#10;I still use them, but not everywhere, and you don&amp;rsquo;t need one to get started.&#10;There is even &lt;a href="https://arxiv.org/abs/2602.11988" target="_blank" rel="noopener"&gt;research&lt;/a&gt; showing that repository-level context files don&amp;rsquo;t generally improve the task success rate of coding agents, while raising the cost by over 20%.&#10;They help when you have non-standard practices the agent can&amp;rsquo;t guess.&#10;A list of standard rules or an overview of the repository does not.&lt;/p&gt;&#10;&lt;h2 id="2-ask-it-everything-"&gt;2. Ask it everything 🥩 &lt;a class="anchor" href="#2-ask-it-everything-" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The real change is a mindset, not a tool.&lt;/p&gt;&#10;&lt;p&gt;When you run into a problem, the old reflex is to Google it.&#10;The new reflex is to ask the AI about everything.&#10;Asking also means asking it to do things.&#10;Most of what I type is a description of what I want done, and why.&#10;Give it the context you would give a colleague.&lt;/p&gt;&#10;&lt;p&gt;When the agent says &amp;ldquo;now you need to run the tests,&amp;rdquo; no.&#10;Everything it can do, you let it do.&#10;If the AI tells you what to do when it could do it itself, you are just a &lt;strong&gt;meat proxy&lt;/strong&gt;, and you are wasting your own time.&lt;/p&gt;&#10;&lt;p&gt;It is genuinely absurd how good it has gotten.&#10;My mom sent me a photo of &lt;a href="https://www.nijho.lt/post/mindroom/"&gt;MindRoom&lt;/a&gt; crashing in her browser, a screen full of minified JavaScript.&#10;I sent the photo to my agent.&#10;The answer: the Google Translate extension was interfering with the page.&#10;It wrote the fix too.&lt;/p&gt;&#10;&lt;p&gt;The people who still don&amp;rsquo;t use it are, I think, in one of two groups.&#10;Some had a bad experience once, years ago, and never tried again.&#10;That experience is badly out of date.&#10;Others, and I suspect it&amp;rsquo;s a large group, avoid AI on principle.&#10;This post won&amp;rsquo;t change their minds, but it might make starting easier for everyone else.&lt;/p&gt;&#10;&lt;h2 id="3-use-the-best-model"&gt;3. Use the best model &lt;a class="anchor" href="#3-use-the-best-model" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Another very common question: shouldn&amp;rsquo;t I use a cheaper model to save money?&#10;When you&amp;rsquo;re starting out, my answer is to use the best one.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Your time almost certainly costs more than the tokens.&lt;/strong&gt;&#10;For an engineer, it certainly does.&#10;Continuously deciding &amp;ldquo;do I need the smartest model for this, or the weakest one?&amp;rdquo; is itself not efficient.&#10;A useful check when a session costs $50: what would this have cost you without AI?&#10;If you would have done it anyway, the answer is almost always way more.&#10;(If you only did it because AI made it possible, the comparison gets harder.)&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Cheaper per token is not cheaper per task.&lt;/strong&gt;&#10;A cheaper model does not necessarily get to the solution in fewer tokens.&#10;On hard problems it typically uses way more.&lt;/p&gt;&#10;&lt;p&gt;My favorite way to see this is &lt;a href="https://artificialanalysis.ai/" target="_blank" rel="noopener"&gt;Artificial Analysis&lt;/a&gt;&amp;rsquo;s intelligence index versus &lt;strong&gt;cost per task&lt;/strong&gt;, which accounts for both the price and how many tokens a model burns.&#10;Here are Claude Opus 5.5 and Claude Sonnet 5.5 at each reasoning effort:&lt;/p&gt;&#10;&lt;figure class="plot-figure"&gt;&#10; &lt;div class="plot-container" role="img" aria-label="Artificial Analysis Intelligence Index versus the average cost of one of its tasks, for each reasoning effort, as of 2026-10-08. Hover for the output tokens per task." data-plot-module="/post/how-to-start-with-ai/plots.js" data-plot-name="costPerTask"&gt;&lt;/div&gt;&#10; &lt;figcaption&gt;Artificial Analysis Intelligence Index versus the average cost of one of its tasks, for each reasoning effort, as of 2026-10-08. Hover for the output tokens per task.&lt;/figcaption&gt;&#10; &lt;noscript&gt;This chart needs JavaScript.&lt;/noscript&gt;&#10;&lt;/figure&gt;&#10;&#10;&lt;script type="module" src="https://www.nijho.lt/js/plot.7cb86dc2e3ef25b56bc93730b2620745a7f02b5715de87f94e61908f60e51690.js" integrity="sha256-fLhtwuPvJbVryTcwsmIHRafwK1cV3of5TmGQj2DlFpA=" crossorigin="anonymous"&gt;&lt;/script&gt;&#10;&#10;&#10;&lt;p&gt;Sonnet costs half as much per token.&#10;But at max effort it scores 56, the same as Opus at xhigh, and costs $5.46 per task against Opus&amp;rsquo;s $3.46.&#10;It just uses a lot more tokens: about 197,000 output tokens per task versus 66,000.&#10;Above a score of about 47, the Opus line is both higher and further to the left.&lt;/p&gt;&#10;&lt;p&gt;So for simple tasks, the cheaper model is cheaper.&#10;For difficult work, it is sometimes the same price, often takes longer, and can cost more, because it burns through so many more tokens.&#10;And a worse answer gets more expensive later, because somebody has to fix it.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Don&amp;rsquo;t put reasoning effort on max.&lt;/strong&gt;&#10;Going from xhigh to max on Opus buys 1.6 points for 73% more money.&#10;On Sonnet it is 2.7 times the cost.&#10;I default to xhigh myself, which is probably overkill for half of what I do.&lt;/p&gt;&#10;&lt;h2 id="4-decide-how-much-to-trust-it"&gt;4. Decide how much to trust it &lt;a class="anchor" href="#4-decide-how-much-to-trust-it" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;When I started, I read every single line of code it wrote and had so many comments.&#10;By now I trust the output much more, because I&amp;rsquo;ve seen it.&#10;The scope I hand over has grown with that trust.&#10;&lt;a href="https://chat.mindroom.chat/canvases/" target="_blank" rel="noopener"&gt;Canvases in MindRoom Chat&lt;/a&gt;, interactive pages an agent can show you next to the conversation, felt like a half-year project.&#10;I built it in a day, on my phone.&lt;/p&gt;&#10;&lt;p&gt;How closely I look depends on how important the result is and how measurable it is.&#10;The core of a project, the part everything relies on: there I want to understand precisely what&amp;rsquo;s going on.&#10;An integration that fetches my email from some external API, something written a million times whose outcome is easy to check: I don&amp;rsquo;t read the code.&#10;When I see that it works, I believe it.&#10;The same goes outside code: an answer you can check in a minute needs less scrutiny than one you can&amp;rsquo;t check at all.&lt;/p&gt;&#10;&lt;figure&gt;&lt;img src="https://www.nijho.lt/post/how-to-start-with-ai/trust-tree.svg" alt="A tree with three large blue core nodes at the top and six small grey leaf nodes at the bottom. The core is labeled: everything depends on it, read it and understand it. The leaves are labeled: nothing depends on them, check that they work." loading="lazy" data-zoomable&gt;&lt;/figure&gt;&#10;&lt;p&gt;This is also why expertise still matters.&#10;When I scroll through a large piece of code, I can judge its complexity at a glance.&#10;When it explains something in a field I know, I can tell when it&amp;rsquo;s wrong and call bullshit.&#10;In a field I don&amp;rsquo;t know, I can&amp;rsquo;t, so I spend much more time validating to reach the same level of trust.&#10;Match your scrutiny to your expertise.&lt;/p&gt;&#10;&lt;h2 id="5-talk-to-it-then-make-it-review-itself"&gt;5. Talk to it, then make it review itself &lt;a class="anchor" href="#5-talk-to-it-then-make-it-review-itself" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;I start by telling it what I want, usually by voice.&#10;I just ramble.&#10;It is so good at language that even when I go off track and talk incoherently, it almost always understands what I mean.&#10;And sometimes it pushes back: &amp;ldquo;I understand what you mean, but that approach is bad because of this, I&amp;rsquo;d do it this way.&amp;rdquo;&#10;Sometimes it says we could do it either way, and I say: let&amp;rsquo;s try both.&lt;/p&gt;&#10;&lt;p&gt;In almost all cases, AI can now deliver what you asked for in a single prompt, and it will actually work.&#10;The question is whether it&amp;rsquo;s actually good, and whether it meets your standards.&#10;So before you accept anything, have it reviewed.&lt;/p&gt;&#10;&lt;p&gt;For me, the review has to come from a fresh context that never saw the conversation that produced the work.&#10;A new session, or a sub-agent, that only sees the result.&#10;That can be the same model or a different one.&#10;I do both: the same model in a fresh context, and other models, until they agree it&amp;rsquo;s good.&#10;That sounds like a lot of setup, but it isn&amp;rsquo;t.&#10;In a chat app, it can be as simple as pasting the answer into a new chat, or into the other company&amp;rsquo;s app, and asking what&amp;rsquo;s wrong with it.&lt;/p&gt;&#10;&lt;p&gt;Whatever you use, also tell it to &lt;strong&gt;be mindful of scope creep.&lt;/strong&gt;&#10;A review will always find something.&#10;Very often it&amp;rsquo;s an edge case that looks real in isolation but can never happen in your actual situation.&#10;Ask whether each finding is realistic before you let it build more.&lt;/p&gt;&#10;&lt;h2 id="6-what-about-skills-and-multi-agent-loops"&gt;6. What about skills and multi-agent loops? &lt;a class="anchor" href="#6-what-about-skills-and-multi-agent-loops" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Yes, I use those things.&#10;No, you don&amp;rsquo;t need them to start.&lt;/p&gt;&#10;&lt;p&gt;I never sit down and think &amp;ldquo;now I need to develop a skill.&amp;rdquo;&#10;I do something with the agent a couple of times, realize I&amp;rsquo;m going to keep repeating it, and then say: &amp;ldquo;let&amp;rsquo;s make a skill out of this, and make it self-evolving.&amp;rdquo;&#10;A skill is just a procedure you want to repeat.&#10;You only know what to put in it after you&amp;rsquo;ve repeated it.&#10;(In &lt;a href="https://docs.mindroom.chat/skills/#automatic-skill-learning" target="_blank" rel="noopener"&gt;MindRoom&lt;/a&gt;, an agent can even do this on its own: with automatic skill learning turned on, it reviews its recent work in the background and turns repeated workflows into skills.)&lt;/p&gt;&#10;&lt;p&gt;My own set of skills is public as &lt;a href="https://github.com/basnijholt/baspowers" target="_blank" rel="noopener"&gt;baspowers&lt;/a&gt;, which started as a fork of &lt;a href="https://github.com/obra/superpowers" target="_blank" rel="noopener"&gt;superpowers&lt;/a&gt;.&#10;Some of its skills came from &lt;a href="https://github.com/basnijholt/baspowers#how-the-delivery-skills-were-made" target="_blank" rel="noopener"&gt;mining more than ten thousand session logs&lt;/a&gt; of my agent history for procedures I kept repeating, then A/B testing each one with and without the skill.&#10;An A/B test sounds like a lot of work, but you can ask the agent to run it for you, and tell it which other models to test with.&#10;Four of the ten candidates were dropped because the agents already did the right thing without them.&#10;The rule I ended up with: &lt;strong&gt;keep only skills that change behavior.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;Sometimes they really do.&#10;In one test, agents wrote a failing test before fixing a bug in 0 of 32 runs without my &lt;a href="https://github.com/basnijholt/baspowers/tree/main/skills/test-driven-development" target="_blank" rel="noopener"&gt;test-driven development skill&lt;/a&gt;, and in 32 of 32 runs with it.&#10;That matters when agents run on their own for hours.&#10;It does not matter for your first week of asking questions.&lt;/p&gt;&#10;&lt;p&gt;I also run cross-model reviews in loops, which is useful when I have ten things running at once.&#10;But I keep updating those setups, because each new model makes parts of them unnecessary.&#10;My &lt;a href="https://github.com/mindroom-ai/mindroom/blob/main/.claude/skills/pr-review/SKILL.md" target="_blank" rel="noopener"&gt;PR review skill&lt;/a&gt; used to make agents fix every nitpick.&#10;Now the models are good enough that it will forever find something, even after a hundred rounds, so I had to change it: it now only blocks on issues with a realistic scenario.&lt;/p&gt;&#10;&lt;p&gt;That is the problem with copying someone&amp;rsquo;s elaborate workflow.&#10;It encodes the weaknesses of last year&amp;rsquo;s models and the habits of one person.&#10;Start with nothing, and add things once you notice you keep repeating them.&lt;/p&gt;&#10;&lt;h2 id="7-if-you-write-code"&gt;7. If you write code &lt;a class="anchor" href="#7-if-you-write-code" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;A few things only apply to software.&lt;/p&gt;&#10;&lt;h3 id="tests-are-cheap-now-so-ask-for-them"&gt;Tests are cheap now, so ask for them &lt;a class="anchor" href="#tests-are-cheap-now-so-ask-for-them" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;&amp;ldquo;Set up the actual live system, end to end (don&amp;rsquo;t touch production!), run it with real data, crash it at different points in the middle.&amp;rdquo;&#10;All the random things you would check yourself if you had infinite time.&#10;Have it write a lot of tests.&#10;More tests is better, even when some have limited value.&#10;What I care about is that the source code itself is clean.&lt;/p&gt;&#10;&lt;h3 id="the-code-is-the-spec"&gt;The code is the spec &lt;a class="anchor" href="#the-code-is-the-spec" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;A lot of people will disagree here, but I throw away design docs.&#10;What came out in the end was never what the doc said anyway.&#10;The code and the tests are the specification, because that&amp;rsquo;s also what the agent reads.&#10;The only thing I keep is what the code can&amp;rsquo;t say: why something was done a certain way.&#10;Documentation that conflicts with the code is the worst: the agent will start changing your code to match the docs without you noticing.&lt;/p&gt;&#10;&lt;h3 id="review-against-your-own-criteria"&gt;Review against your own criteria &lt;a class="anchor" href="#review-against-your-own-criteria" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;The questions I make it answer about its own work:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Is the code clean?&lt;/li&gt;&#10;&lt;li&gt;Does it fit well within the existing architecture?&lt;/li&gt;&#10;&lt;li&gt;Does it repeat itself?&lt;/li&gt;&#10;&lt;li&gt;Is it overengineered? Keep it simple, stupid.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="cross-model-review-needs-two-installs"&gt;Cross-model review needs two installs &lt;a class="anchor" href="#cross-model-review-needs-two-installs" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;As long as you have both Codex and Claude Code installed, you are essentially ready.&#10;Just tell the agent: &amp;ldquo;have Codex review this in a separate session and address what it finds.&amp;rdquo;&#10;It can usually figure out how to call the other command-line tool on its own.&#10;I personally built a worktree orchestration tool for this, &lt;a href="https://www.nijho.lt/post/parallel-agentic-coding/"&gt;&lt;code&gt;agent-cli dev&lt;/code&gt;&lt;/a&gt;, which comes with a skill that teaches the agent to use it.&#10;But honestly, that is not necessary anymore nowadays.&lt;/p&gt;&#10;&lt;h3 id="a-good-ai-engineer-is-just-a-good-engineer"&gt;A good AI engineer is just a good engineer &lt;a class="anchor" href="#a-good-ai-engineer-is-just-a-good-engineer" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;People ask me what makes a good agentic engineer.&#10;I&amp;rsquo;ve been saying the same thing for a long time: somebody who is literally a good engineer.&#10;Good engineering practices never went away.&#10;They are more important than ever: test-driven development, building things at the right level of abstraction, a proper architecture.&lt;/p&gt;&#10;&lt;p&gt;I think of engineering skill as a scale that runs from negative to positive.&#10;A good engineer removes work for others.&#10;A bad engineer creates work for others.&#10;Give the bad engineer AI, and they multiply their bad output, because AI is a multiplier.&lt;/p&gt;&#10;&lt;p&gt;Before AI, you could spend a year writing a few thousand lines of code, maybe a couple tens of thousands at most.&#10;You were intimately familiar with all of it, so you could get away with a somewhat worse architecture.&#10;Now you can produce a million lines of code in a year.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;&#10;There is no possible way you can keep up with all of it.&#10;If you want to build something lasting and robust, you need proper foundations.&#10;And that is where your opinions matter.&#10;You don&amp;rsquo;t need any setup to start, but you do need taste to build something that lasts.&#10;(I made a related point a year ago in &lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;On agentic coding&lt;/a&gt;: AI amplifies the experience you already have.)&lt;/p&gt;&#10;&lt;h3 id="your-role-changed-it-didnt-disappear"&gt;Your role changed, it didn&amp;rsquo;t disappear &lt;a class="anchor" href="#your-role-changed-it-didnt-disappear" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Some software engineers feel personally attacked by all this.&#10;I think you have to get over yourself.&#10;Your secret sauce was never knowing the syntax really well.&#10;Now you need to know what to build, and how it should be built.&lt;/p&gt;&#10;&lt;p&gt;And you need to be strict.&#10;You can produce thousands of lines a day, so be thoughtful about whether you want them in your codebase forever.&#10;Changing the color of a button takes one prompt.&#10;A difficult system needs more rigor, which means understanding the architecture and what it implies instead of reading every line.&lt;/p&gt;&#10;&lt;h2 id="this-post-has-an-expiry-date"&gt;This post has an expiry date &lt;a class="anchor" href="#this-post-has-an-expiry-date" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Right now I&amp;rsquo;d tell you to use Claude Opus 5.5.&#10;Just two weeks ago I was telling people to use GPT-6 Astra.&#10;Things change continuously, and in most cases you&amp;rsquo;ll be fine with either.&lt;/p&gt;&#10;&lt;p&gt;I&amp;rsquo;m also sure that a few weeks from now, I will no longer accept the model I&amp;rsquo;m praising today.&#10;Not because it can&amp;rsquo;t do the amazing things it does now.&#10;But because the next one will do even more amazing things that it can&amp;rsquo;t.&#10;With every new model, my workflow changes, and the amount of scope I hand over per task grows dramatically.&lt;/p&gt;&#10;&lt;p&gt;That&amp;rsquo;s why I don&amp;rsquo;t recommend building an elaborate setup first.&#10;Every skill, rule file and agent graph is tuned to the limitations of the model you have today.&#10;Those limitations are gone in a few months, and then the setup is dead weight.&#10;Asking it things is the one habit that survives every model change.&lt;/p&gt;&#10;&lt;p&gt;Install it today, use the best model, and ask it everything, including whether its own work is any good.&#10;The rest is optional, and probably temporary.&lt;/p&gt;&#10;&lt;div class="footnotes" role="doc-endnotes"&gt;&#10;&lt;hr&gt;&#10;&lt;ol&gt;&#10;&lt;li id="fn:1"&gt;&#10;&lt;p&gt;I wrote about 4.5 million lines of code this year, as counted by &lt;a href="https://github.com/basnijholt/trueloc" target="_blank" rel="noopener"&gt;trueloc&lt;/a&gt;, another tool of mine that counts every line added across all commits in my pull requests.&amp;#160;&lt;a href="#fnref:1" class="footnote-backref" role="doc-backlink"&gt;&amp;#x21a9;&amp;#xfe0e;&lt;/a&gt;&lt;/p&gt;&#10;&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/div&gt;&#10;</description></item><item><title>Removing the guardrails and letting my coding agents loose</title><link>https://www.nijho.lt/post/removing-guardrails/</link><pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate><guid isPermaLink="false">/post/removing-guardrails/</guid><description>&lt;p&gt;I have run coding agents in YOLO mode since I started using them in May 2025.&#10;I think it is the only way to parallelize work.&#10;Sometimes I have ten agents running at the same time, and clicking &amp;ldquo;approve&amp;rdquo; on every command they run would make that impossible.&lt;/p&gt;&#10;&lt;p&gt;What makes me comfortable with it is that models tend to do what you ask, and that you can keep them in an environment where they cannot do much harm.&#10;I don&amp;rsquo;t keep secrets within their reach, and above all I have &lt;a href="https://www.nijho.lt/post/btrfs-to-zfs/"&gt;very good backups&lt;/a&gt;.&#10;The last piece is a small set of hooks that block the few things I never want an agent to do on its own.&lt;/p&gt;&#10;&lt;h2 id="why-hooks-and-not-agentsmd"&gt;Why hooks and not AGENTS.md &lt;a class="anchor" href="#why-hooks-and-not-agentsmd" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;My system prompt has always told agents not to force-push or merge PRs.&#10;Some of them did it anyway.&lt;/p&gt;&#10;&lt;p&gt;The first time I really noticed was with &lt;a href="https://www.nijho.lt/post/gemini-3-pro-first-impressions/"&gt;Gemini 3 Pro in November 2025&lt;/a&gt;, which merged my PR and force-pushed to &lt;code&gt;main&lt;/code&gt;.&#10;It happened a couple more times in the weeks after, as I parallelized more and asked more of the models.&#10;Three weeks later I had hooks for Claude Code and Gemini CLI that block these commands before they run.&#10;Codex did not support hooks yet.&#10;To my surprise, it did not need them: OpenAI&amp;rsquo;s models are extremely good at following instructions, and Codex never ignored an explicit rule in my &lt;code&gt;AGENTS.md&lt;/code&gt;.&#10;Codex supports hooks by now, so it runs the same ones as the others.&lt;/p&gt;&#10;&lt;p&gt;Claude has been worse at following rules, and Gemini far worse still: absolutely dogshit.&#10;I only try Gemini now and then, and I have been disappointed every time.&#10;By now I don&amp;rsquo;t even try the latest Google models anymore.&lt;/p&gt;&#10;&lt;p&gt;I don&amp;rsquo;t think agents are ever purposely malicious.&#10;They try to do what you asked, but they can misinterpret it, and then they force-push or merge something.&#10;A rule in a Markdown file is a hope; a hook actually stops the command.&#10;Not that a hook would stop a malicious agent: it could put the blocked command in a Bash script and run that instead.&#10;What the hook does is tell the agent why I don&amp;rsquo;t want it, because every block comes with a short explanation:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;git add -A is not allowed - add files explicitly to avoid adding unrelated untracked files&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The models are well aligned, so once they know my intention, they respect it.&lt;/p&gt;&#10;&lt;h2 id="what-i-block"&gt;What I block &lt;a class="anchor" href="#what-i-block" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;All hooks live in &lt;a href="https://github.com/basnijholt/dotfiles/tree/main/configs/claude/hooks" target="_blank" rel="noopener"&gt;my dotfiles&lt;/a&gt;, and I deliberately kept them simple.&#10;The detection logic is one Python module, &lt;a href="https://github.com/basnijholt/dotfiles/blob/main/configs/claude/hooks/git_guard.py" target="_blank" rel="noopener"&gt;&lt;code&gt;git_guard.py&lt;/code&gt;&lt;/a&gt;, and the Claude Code, Codex, and Gemini CLI hooks all import it.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;&lt;code&gt;git commit --amend&lt;/code&gt; and &lt;code&gt;git push --force&lt;/code&gt;.&lt;/strong&gt;&#10;The unit I review is a PR.&#10;When I review a PR, I know I have reviewed it up to a certain commit, and later I only look at the diff of the new commits.&#10;Rewriting history breaks that.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Pushing to &lt;code&gt;main&lt;/code&gt;.&lt;/strong&gt;&#10;Everything happens in PRs.&#10;Inside a PR I don&amp;rsquo;t care how messy the history gets.&#10;I want the agent to push very often, so no work gets lost, and every commit has to be green, so each one is a snapshot I can go back to.&#10;The agent maintains its own development of the feature, and I have not written a commit message myself in a long time.&#10;When the PR is done, I squash merge it.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;&lt;code&gt;gh pr merge&lt;/code&gt;.&lt;/strong&gt;&#10;The merge comes after my review, so it is mine to do.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;&lt;code&gt;git add -A&lt;/code&gt;.&lt;/strong&gt;&#10;I often have unrelated untracked or unstaged files lying around.&#10;I work in many open source repositories, and some of those files should not be public, like deployment plans.&#10;This is the only block without an override.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;&lt;code&gt;sleep&lt;/code&gt;.&lt;/strong&gt;&#10;This one is for Claude, and Opus 5 specifically, which I hate with a passion.&#10;It would run tests in the background and then &lt;code&gt;sleep 300&lt;/code&gt;, badly overestimating how long the tests take, when a blocking tool call returns exactly when they finish.&lt;/p&gt;&#10;&lt;h2 id="the-override"&gt;The override &lt;a class="anchor" href="#the-override" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Over time the models got more capable.&#10;I could parallelize more, and I trusted them to work on their own for longer.&#10;I noticed I was spending a significant fraction of my time clicking buttons and doing operations I had forbidden the agent to do, only to end up doing them myself.&lt;/p&gt;&#10;&lt;p&gt;So in July I added an override.&#10;When a hook blocks a command, the agent gets this hint:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;If (and only if) the user has explicitly approved this exact action,&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;re-run the command prefixed with EXPLICITLY_USER_APPROVED_HOOK_OVERRIDE=1 to override this block.&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Nothing checks whether I actually approved it.&#10;It is a soft gate, but it works because the agent now has to write down, in the command itself, that I approved the action.&#10;When it runs into the block without my approval, it becomes obvious to the agent that it has to ask me first.&lt;/p&gt;&#10;&lt;p&gt;&lt;code&gt;git add -A&lt;/code&gt; stays hard-blocked, and a chained command cannot carry an override past it: &lt;code&gt;EXPLICITLY_USER_APPROVED_HOOK_OVERRIDE=1 git commit --amend &amp;amp;&amp;amp; git add -A&lt;/code&gt; is still rejected.&lt;/p&gt;&#10;&lt;h2 id="when-the-override-was-used-without-approval"&gt;When the override was used without approval &lt;a class="anchor" href="#when-the-override-was-used-without-approval" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;It has happened, mostly with GPT-5.6 Sol, which I used a lot at the time.&lt;/p&gt;&#10;&lt;p&gt;It used to be that you had to keep your context window short, because auto-compaction was lossy and produced poor summaries.&#10;Since around GPT-5.3, compaction works well enough that I keep a session going for as long as I am working on the same feature.&#10;So I would ask the agent to merge a PR early on, start a follow-up PR in the same session, and after a compaction the agent concluded that it should merge the new PR too.&#10;It did, without my approval.&lt;/p&gt;&#10;&lt;p&gt;The other case was my &lt;a href="https://github.com/mindroom-ai/mindroom/blob/main/.claude/skills/pr-review/SKILL.md" target="_blank" rel="noopener"&gt;&lt;code&gt;pr-review&lt;/code&gt; skill&lt;/a&gt;, by far my favorite skill that I wrote myself.&#10;I would tell the agent to run it and squash merge the PR only if the review approved it.&#10;A few times, the review found problems, the agent fixed them, and then it merged.&#10;What I meant was: merge if it is approved right away, and otherwise wait for me.&#10;Now I spell that out and end with &amp;ldquo;otherwise, wait for my instructions.&amp;rdquo;&lt;/p&gt;&#10;&lt;h2 id="working-from-my-phone"&gt;Working from my phone &lt;a class="anchor" href="#working-from-my-phone" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The override matters most when I am away from my computer.&#10;On a month-long trip visiting family in Europe, I worked only from my phone, using &lt;a href="https://www.nijho.lt/post/agentic-mobile-workflow/"&gt;my mobile coding workflow&lt;/a&gt;.&#10;Typing commands in a terminal on a phone is inconvenient, so I would rather say what I want and let the agent do it, including the merge.&#10;I have also built end-to-end encrypted voice calls to my agents over Matrix with &lt;a href="https://www.nijho.lt/post/mindroom/"&gt;MindRoom&lt;/a&gt;, and I am moving more toward that kind of voice-driven workflow.&lt;/p&gt;&#10;&lt;h2 id="not-much-has-changed"&gt;Not much has changed &lt;a class="anchor" href="#not-much-has-changed" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;I recently reread &lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;my first post on agentic coding&lt;/a&gt; from August 2025, and very little in it is outdated.&#10;The models are more capable, and I give them much larger scopes, but the way I work is mostly the same.&#10;The hooks are the main thing I added, and the override is how I loosened them again.&lt;/p&gt;&#10;</description></item><item><title>The last btrfs machine: migrating my PC to ZFS</title><link>https://www.nijho.lt/post/btrfs-to-zfs/</link><pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate><guid isPermaLink="false">/post/btrfs-to-zfs/</guid><description>&lt;p&gt;My GPU machine was the last machine in my fleet still running btrfs.&#10;I &lt;a href="https://www.nijho.lt/post/local-ai-journey/"&gt;bought it for gaming&lt;/a&gt; (which never happened), and these days its dual RTX 3090s almost exclusively run &lt;a href="https://www.nijho.lt/post/llama-nixos/"&gt;local AI models&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;btrfs itself never failed me.&#10;When I set up NixOS on this machine for the first time, I had read enough forum threads to become convinced that ZFS and NixOS were a troublesome combination, so I picked btrfs to be safe.&#10;That belief was simply wrong.&#10;As I &lt;a href="https://www.nijho.lt/post/proxmox-to-nixos/"&gt;went full Nix&lt;/a&gt; and eventually &lt;a href="https://www.nijho.lt/post/truenas-to-nixos/"&gt;moved even my TrueNAS to NixOS&lt;/a&gt;, I learned there was no issue at all.&#10;I just had to figure out the right incantation to make ZFS work with boot drives, &lt;a href="https://github.com/nix-community/disko" target="_blank" rel="noopener"&gt;disko&lt;/a&gt;, and &lt;a href="https://github.com/nix-community/nixos-anywhere" target="_blank" rel="noopener"&gt;nixos-anywhere&lt;/a&gt;.&#10;My HP got ZFS first, that config grew into a shared disko module, and soon the whole fleet ran one pattern: NixOS on ZFS, snapshots and replication declared in code, and backups I can reason about.&lt;/p&gt;&#10;&lt;p&gt;Only the machine I sit at every day kept running on my old misconception, because a daily driver is exactly the one you do not casually reinstall.&lt;/p&gt;&#10;&lt;details class="toc" open&gt;&lt;summary&gt;Table of contents&lt;/summary&gt;&lt;nav id="TableOfContents"&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#why-touch-a-working-machine"&gt;Why touch a working machine&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-backup-that-wasnt"&gt;The backup that wasn&amp;rsquo;t&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#what-the-audit-found"&gt;What the audit found&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-plan-one-shared-disko-module"&gt;The plan: one shared disko module&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#rehearsing-in-a-vm-again"&gt;Rehearsing in a VM, again&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-recovery-kit"&gt;The recovery kit&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#trusting-the-backup-enough-to-wipe-the-disk"&gt;Trusting the backup enough to wipe the disk&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-fifth-question"&gt;The fifth question&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#restoring-in-stages"&gt;Restoring in stages&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#slimming-down-first"&gt;Slimming down first&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-cutover"&gt;The cutover&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#references"&gt;References&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10;&lt;/nav&gt;&lt;/details&gt;&#10;&#10;&lt;h2 id="why-touch-a-working-machine"&gt;Why touch a working machine &lt;a class="anchor" href="#why-touch-a-working-machine" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The operating system was already uniform.&#10;The filesystem was not, and that turned out to matter more than I expected.&lt;/p&gt;&#10;&lt;p&gt;The real trigger was that I got increasingly paranoid about an AI agent messing up my system.&#10;I run agentic AI in YOLO mode, exclusively.&#10;All day, every day, agents execute commands on this machine without asking me first.&#10;YOLO does not mean root, though: the agents run as my regular user, and the backup credentials live where only root can read them.&#10;An agent that could destroy the backup itself would make everything else in this post pointless.&#10;Meanwhile the stories keep coming in about even the most frontier models wiping someone&amp;rsquo;s home directory:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;GPT-5.6-Sol just accidentally deleted almost ALL of my Mac&amp;rsquo;s files. And this is why I trust Fable 1000x more.&lt;/p&gt;&#10;&lt;p&gt;— &lt;a href="https://x.com/mattshumer_/status/2075657271401390161" target="_blank" rel="noopener"&gt;@mattshumer_&lt;/a&gt;&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;The reaction is always about which model deserves more trust.&#10;I read these tweets differently.&#10;Give any agent enough sessions and it will eventually delete something important, the same way I do every few years with a tired &lt;code&gt;rm -rf&lt;/code&gt;.&#10;Whether that moment becomes a catastrophe or an inconvenience depends entirely on the restore path.&lt;/p&gt;&#10;&lt;p&gt;So I felt I needed to properly audit the way my backups were done.&#10;I want to be able to answer four questions about any machine I own:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;What exactly is in the backup?&lt;/li&gt;&#10;&lt;li&gt;What is &lt;em&gt;not&lt;/em&gt; in the backup, and did I choose that deliberately?&lt;/li&gt;&#10;&lt;li&gt;How big is a restore?&lt;/li&gt;&#10;&lt;li&gt;How long will it take?&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;h2 id="the-backup-that-wasnt"&gt;The backup that wasn&amp;rsquo;t &lt;a class="anchor" href="#the-backup-that-wasnt" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Asking &lt;span class="hover-tip" data-tooltip="What exactly is in the backup?" tabindex="0"&gt;question 1&lt;/span&gt; delivered an unpleasant answer within the hour: the backups had quietly stopped four months earlier.&#10;Two boring causes had stacked up: an interrupted prune left a stale repository lock, which the job could never clear because its own unlock step only ran &lt;em&gt;after&lt;/em&gt; a successful backup, and the repository URL still pointed at &lt;code&gt;truenas.local&lt;/code&gt;, a name that had stopped resolving &lt;a href="https://www.nijho.lt/post/truenas-to-nixos/"&gt;along the way&lt;/a&gt;.&#10;The last successful backup ran at 07:00 on March 22; the next one at 07:16 on July 22, after &lt;a href="https://github.com/basnijholt/dotfiles/commit/4d2a75efcb503b9ca2aabcbe8339be3e5a62d0ce" target="_blank" rel="noopener"&gt;the fix&lt;/a&gt;.&#10;Four months, almost to the minute.&#10;systemd logged the failure on every single run, nobody read it, and nothing escalated.&#10;I found out because I asked the question, not because anything told me.&lt;/p&gt;&#10;&lt;h2 id="what-the-audit-found"&gt;What the audit found &lt;a class="anchor" href="#what-the-audit-found" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;On the btrfs box, &lt;span class="hover-tip" data-tooltip="How big is a restore?" tabindex="0"&gt;question 3&lt;/span&gt; alone had three different answers depending on which tool I asked.&#10;&lt;code&gt;du&lt;/code&gt; counted reflinked copies at full size, so directories reported terabytes that physically did not exist.&#10;&lt;code&gt;df&lt;/code&gt; counted physical extents, which is honest about disk usage but tells you nothing about what a file-based restore will write.&#10;And restic reported the &lt;em&gt;apparent&lt;/em&gt; size of sparse VM images, which inflated the restore estimate to several times the disk.&lt;/p&gt;&#10;&lt;p&gt;When your storage layer gives you three sizes for the same data, you do not really understand your backup.&#10;You have a backup, and you have hope.&lt;/p&gt;&#10;&lt;p&gt;&lt;span class="hover-tip" data-tooltip="How long will it take?" tabindex="0"&gt;Question 4&lt;/span&gt; was no better.&#10;Because the PC was my only btrfs machine, it could not join &lt;a href="https://github.com/basnijholt/dotfiles/blob/0d6101c8e3f91a0845cb41adb3cda216f50917c8/configs/nixos/hosts/nas/replication.nix" target="_blank" rel="noopener"&gt;the ZFS snapshot replication the rest of the fleet uses&lt;/a&gt;, so its backups relied entirely on restic pushing to the NAS.&#10;Off-machine, note, but not off-site; &lt;span class="hover-tip" data-tooltip="What is not in the backup, and did I choose that deliberately?" tabindex="0"&gt;question 2&lt;/span&gt; turned out to apply to locations too, and closing that gap is its own project.&#10;restic is file-based: every run visits the metadata of every single file to find what changed.&#10;On this machine that meant close to a hundred million files per scan, which turned out to include some 600 GB of git worktrees stuffed with virtual environments and &lt;code&gt;node_modules&lt;/code&gt;.&#10;Each run took about an hour and a half, even when almost nothing had changed.&lt;/p&gt;&#10;&lt;p&gt;That scan time dictated my backup cadence.&#10;The timer ran hourly, which in practice meant back-to-back scanning all day to move a couple hundred megabytes of real changes, and I recently &lt;a href="https://github.com/basnijholt/dotfiles/commit/4f2401de725d5201d4daca0e67505ad2e6f6691a" target="_blank" rel="noopener"&gt;dropped it to every six hours&lt;/a&gt; to stop the madness.&#10;Either way, my most recent work existed only on the machine an agent was busy poking at.&lt;/p&gt;&#10;&lt;p&gt;The scanning is also not free for the hardware.&#10;Reads are gentle on an SSD compared to writes, but hourly scans of an hour and a half each kept the drive at full duty cycle and elevated temperature for most of every day.&#10;And drives stopped being cheap: I paid $227 for &lt;a href="https://www.nijho.lt/post/homelab/"&gt;a 4 TB NVMe drive&lt;/a&gt; in 2024, and the same drive lists for around $800 today.&#10;I would rather not run the experiment of what years of continuous scanning do to a drive I can no longer afford to replace.&lt;/p&gt;&#10;&lt;p&gt;btrfs has perfectly good snapshots of its own, but sending them off-site was never an option for me: snapshot replication needs the same filesystem on the receiving end, and my NAS speaks ZFS.&#10;With ZFS I can snapshot every few minutes and &lt;code&gt;zfs send&lt;/code&gt; the actual block storage: an incremental send streams exactly the blocks that changed since the last snapshot, without walking a single file.&#10;A hundred million files cost nothing when nobody has to visit them.&lt;/p&gt;&#10;&lt;p&gt;ZFS does not magically collapse those numbers into one.&#10;But it gives me the same semantics everywhere, including on the NAS pools that hold the backups themselves.&#10;Eight of my machines already share a single ZFS disk layout, defined in &lt;a href="https://github.com/basnijholt/dotfiles/blob/0d6101c8e3f91a0845cb41adb3cda216f50917c8/configs/nixos/common/disko-zfs.nix" target="_blank" rel="noopener"&gt;one shared disko module&lt;/a&gt;.&#10;The PC was the odd one out.&#10;This migration makes it nine machines with the exact same strategy, and one backup story to audit instead of one per machine.&lt;/p&gt;&#10;&lt;h2 id="the-plan-one-shared-disko-module"&gt;The plan: one shared disko module &lt;a class="anchor" href="#the-plan-one-shared-disko-module" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The Nix side was the easy part.&#10;The PC now imports the same shared disko module as the other eight machines, with one addition: a &lt;code&gt;swapSize&lt;/code&gt; parameter, because ZFS has no reliable swapfile story and the PC actually needs its 96 GB of swap.&lt;/p&gt;&#10;&lt;p&gt;The disk is &lt;a href="https://github.com/basnijholt/dotfiles/blob/8c0bc5faded40362ac01347682aaf2089562047d/configs/nixos/hosts/pc/disko.nix" target="_blank" rel="noopener"&gt;pinned by ID&lt;/a&gt;, not by device name:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-nix" data-lang="nix"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;device&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;&amp;#34;/dev/disk/by-id/nvme-Samsung_SSD_990_EVO_Plus_4TB_...&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This matters more than usual here.&#10;The PC dual-boots Windows from a second NVMe drive, and I want zero ambiguity about which of the two disks disko is allowed to erase.&lt;/p&gt;&#10;&lt;p&gt;The scary property of this migration is different from the NAS one.&#10;For the NAS, the whole point was that disko must &lt;em&gt;not&lt;/em&gt; touch the data pools.&#10;For the PC, the new ZFS pool goes on the &lt;strong&gt;same disk the data currently lives on&lt;/strong&gt;.&#10;No second disk, no local rollback, no btrfs to boot back into.&#10;From the moment disko runs, the restic repository on the NAS is the only road back.&lt;/p&gt;&#10;&lt;p&gt;That sentence is the reason most of this post is about verification.&lt;/p&gt;&#10;&lt;p&gt;The road back also has to survive the same agents that motivated all of this.&#10;The PC pushes its backups over sftp as a user that owns every file in the repository, which means a compromised PC could delete or encrypt its own safety net.&#10;So the NAS &lt;a href="https://github.com/basnijholt/dotfiles/blob/0d6101c8e3f91a0845cb41adb3cda216f50917c8/configs/nixos/hosts/nas/storage.nix#L128-L143" target="_blank" rel="noopener"&gt;snapshots the repository dataset on its own side&lt;/a&gt;, where the PC&amp;rsquo;s credentials cannot reach: two days of hourly ZFS snapshots and two weeks of dailies that only root on the NAS can destroy.&lt;/p&gt;&#10;&lt;h2 id="rehearsing-in-a-vm-again"&gt;Rehearsing in a VM, again &lt;a class="anchor" href="#rehearsing-in-a-vm-again" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The &lt;a href="https://www.nijho.lt/post/truenas-to-nixos/"&gt;NAS migration&lt;/a&gt; taught me to rehearse the destructive step in a VM, so the flake grew a &lt;a href="https://github.com/basnijholt/dotfiles/blob/8c0bc5faded40362ac01347682aaf2089562047d/configs/nixos/flake.nix#L110" target="_blank" rel="noopener"&gt;&lt;code&gt;pc-vmtest&lt;/code&gt; target&lt;/a&gt; and I ran the whole install through &lt;code&gt;nixos-anywhere --vm-test&lt;/code&gt;.&#10;Disko formatted a virtual disk, created the pool, installed the system, and booted it with swap active.&lt;/p&gt;&#10;&lt;p&gt;Passing that test proves the generated logic.&#10;It does not prove the backup, which is where the real risk lives.&lt;/p&gt;&#10;&lt;h2 id="the-recovery-kit"&gt;The recovery kit &lt;a class="anchor" href="#the-recovery-kit" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;A restore that starts with &amp;ldquo;first, log in to the dead machine and fetch the credentials&amp;rdquo; is not a restore plan.&#10;So everything a bare reinstall needs lives in a small recovery kit on two other machines in the house, permissions locked down: the restic password and SSH key that reach the repository, the staged restore script, a couple of verification scripts, and the PC&amp;rsquo;s SSH host keys.&#10;The host keys matter more than they look: the reinstalled machine comes back with its old identity, so no client complains and nothing in the fleet needs to be taught to trust a new machine.&#10;A munge key and a README round it out.&lt;/p&gt;&#10;&lt;h2 id="trusting-the-backup-enough-to-wipe-the-disk"&gt;Trusting the backup enough to wipe the disk &lt;a class="anchor" href="#trusting-the-backup-enough-to-wipe-the-disk" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;My recovery story has two layers.&#10;NixOS makes the &lt;em&gt;system&lt;/em&gt; disposable: every service, driver fix, and firewall rule is in git, so no agent can leave the machine in a state I cannot rebuild.&#10;Verified backups make the &lt;em&gt;data&lt;/em&gt; recoverable.&#10;This migration is the voluntary version of the tweets above: I am about to delete all of my PC&amp;rsquo;s files on purpose.&lt;/p&gt;&#10;&lt;p&gt;I did three verifications, each one converting an assumption into a fact.&#10;An AI agent did the tedious sweeps; I reviewed the evidence.&lt;/p&gt;&#10;&lt;p&gt;The first check was completeness.&#10;We walked everything on the machine &lt;em&gt;outside&lt;/em&gt; the backup paths, until every byte was accounted for.&#10;It was all re-downloadable caches, and the largest unexplained thing turned out to be restic&amp;rsquo;s own local cache.&#10;Everything outside the backup set is now &lt;em&gt;known&lt;/em&gt; disposable instead of &lt;em&gt;assumed&lt;/em&gt; disposable.&lt;/p&gt;&#10;&lt;p&gt;The second check was the restore path.&#10;A backup you have never restored from is a hypothesis.&#10;On a different machine, using only the recovery kit and no access to the PC at all, we restored a sample from the latest snapshot and compared hashes against the live system.&#10;The hashes matched byte for byte, and even the symlinks came back pointing at the right targets.&#10;A sample proves the path works, from credentials to symlink handling; reading back every byte is the third check&amp;rsquo;s job.&#10;The machine running the rehearsal had the kit and nothing else, so recovery provably does not depend on the machine being recovered.&lt;/p&gt;&#10;&lt;p&gt;The third check is the data itself.&#10;&lt;code&gt;restic check&lt;/code&gt; validates the repository structure without reading back the actual data blobs.&#10;Before the wipe, a &lt;code&gt;--read-data&lt;/code&gt; pass ran on the NAS, where the repository sits on local disk instead of behind the network.&#10;When the backup is the only rollback, I want its bits read back at least once.&lt;/p&gt;&#10;&lt;h2 id="the-fifth-question"&gt;The fifth question &lt;a class="anchor" href="#the-fifth-question" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The outage taught me a &lt;span class="hover-tip" data-tooltip="How do I find out when any of this stops working?" tabindex="0"&gt;fifth question&lt;/span&gt;: how do I find out when any of this stops working?&#10;All three checks above are point-in-time, and verification rots.&#10;So the NAS now &lt;a href="https://github.com/basnijholt/dotfiles/blob/0d6101c8e3f91a0845cb41adb3cda216f50917c8/configs/nixos/hosts/nas/replication.nix#L263-L285" target="_blank" rel="noopener"&gt;re-verifies every hour&lt;/a&gt;, from its own side of the sftp connection, that the newest snapshot in the repository is less than a day old, and pushes an alert to my phone when it is not.&#10;That catches every failure mode on the PC side, including &amp;ldquo;the timer is simply disabled.&amp;rdquo;&#10;The watcher itself is watched: the NAS pings an &lt;a href="https://github.com/basnijholt/dotfiles/blob/0d6101c8e3f91a0845cb41adb3cda216f50917c8/configs/nixos/hosts/nas/health.nix#L252-L280" target="_blank" rel="noopener"&gt;external dead-man&amp;rsquo;s switch&lt;/a&gt; every five minutes, so if the machine holding my only road back goes dark, the alert comes from outside the house.&lt;/p&gt;&#10;&lt;p&gt;While wiring this up we discovered that months of earlier NAS alerts had never arrived, because &lt;a href="https://github.com/basnijholt/dotfiles/blob/0d6101c8e3f91a0845cb41adb3cda216f50917c8/configs/nixos/hosts/nas/health.nix#L60-L67" target="_blank" rel="noopener"&gt;ntfy silently rejects message bodies over 4 KB&lt;/a&gt;.&#10;A notification you have never received is also a hypothesis.&lt;/p&gt;&#10;&lt;h2 id="restoring-in-stages"&gt;Restoring in stages &lt;a class="anchor" href="#restoring-in-stages" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The measured restore set came out to roughly 1 TB, and 99.9% of it is &lt;code&gt;/home&lt;/code&gt;.&#10;But two directories are 64% of that terabyte: Steam (430 GB of re-downloadable games) and my local-AI model collection (217 GB of GGUF files).&lt;/p&gt;&#10;&lt;p&gt;I do not need either of those to have a working machine.&#10;So the restore script now runs in stages:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;sudo ./restore_from_backup.sh stage1 &lt;span class="c1"&gt;# everything else → a fully working machine&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;sudo ./restore_from_backup.sh stage2 &lt;span class="c1"&gt;# Steam + models, whenever&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Stage 1 restores everything except the deferred paths, plus the system identity (host keys).&#10;Stage 2 can run days later, from the rebooted system, while I am already using the machine.&lt;/p&gt;&#10;&lt;p&gt;One detail I care about: stage 1 resolves &lt;code&gt;latest&lt;/code&gt; to a concrete snapshot ID and pins it to a file.&#10;Stage 2 reads the pin.&#10;My backups run every six hours, so without this, a timer firing between the stages would silently split the restore across two different snapshots.&lt;/p&gt;&#10;&lt;p&gt;The backup itself is untouched: Steam and the models are still in every snapshot.&#10;Only the restore order changed.&lt;/p&gt;&#10;&lt;h2 id="slimming-down-first"&gt;Slimming down first &lt;a class="anchor" href="#slimming-down-first" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The PC had also quietly become an Incus host for three LXC containers, including the &lt;a href="https://www.nijho.lt/post/mindroom/"&gt;MindRoom bots&lt;/a&gt; my family talks to every day.&#10;Before the migration, those containers moved to the NAS.&#10;That shrinks both the backup and the restore, and the family bots keep running while their old host is being wiped.&lt;/p&gt;&#10;&lt;aside class="callout callout-note"&gt;&lt;svg class="ico" viewBox="0 0 256 256" aria-hidden="true"&gt;&lt;path d="M128,24A104,104,0,1,0,232,128,104.11,104.11,0,0,0,128,24Zm0,192a88,88,0,1,1,88-88A88.1,88.1,0,0,1,128,216Zm16-40a8,8,0,0,1-8,8,16,16,0,0,1-16-16V128a8,8,0,0,1,0-16,16,16,0,0,1,16,16v40A8,8,0,0,1,144,176ZM112,84a12,12,0,1,1,12,12A12,12,0,0,1,112,84Z"/&gt;&lt;/svg&gt;&lt;div&gt;Moving the containers produced its own lesson in btrfs size confusion.&#10;One container that measured &amp;ldquo;about 250 GB&amp;rdquo; shipped over 590 GB across the network overnight, because a directory that every disk-usage probe had failed to measure turned out to hold 2.5 TB of reflink-inflated build dependencies.&#10;The rule I took away: a directory that has &lt;em&gt;never been successfully measured&lt;/em&gt; is a red alert, not a rounding error.&#10;That kind of confusion is part of why this migration exists.&lt;/div&gt;&lt;/aside&gt;&#10;&lt;h2 id="the-cutover"&gt;The cutover &lt;a class="anchor" href="#the-cutover" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The install followed the same phased &lt;code&gt;nixos-anywhere&lt;/code&gt; pattern as the NAS cutover, driven from another machine on the LAN: kexec into an installer running in RAM, stop, re-verify the target disk from inside the installer, and only then run the destructive disko/install phase.&#10;That checkpoint is the whole point: right up to the destructive phase, aborting was still cheap.&#10;The destructive part turned out to be the trivial part: from wiping the disk to booting the new system took less than twenty minutes.&lt;/p&gt;&#10;&lt;p&gt;The one surprise of the day was in the restore, and it was exactly the kind rehearsal is supposed to catch.&#10;Stage 1 would not start: the restore script runs restic as root, and a freshly installed root has no SSH identity and no known_hosts.&#10;The key it needed sat in the recovery kit inside my home directory.&#10;The rehearsal never hit this, because the rehearsal machine&amp;rsquo;s root had already talked to the NAS.&#10;A verified restore path can still depend on state you forgot you had.&lt;/p&gt;&#10;&lt;p&gt;Stage 1 restored 534 GiB across 4.5 million files in just over an hour and a half, at wire speed.&#10;The machine rebooted with its old host keys and its old &lt;code&gt;/home&lt;/code&gt;, and stage 2 started immediately.&#10;The plan said stage 2 could wait for days; it started the minute the machine was back, because once the machine works there is no reason left to wait.&#10;The deferred 648 GiB of games and models took six more hours in the background.&lt;/p&gt;&#10;&lt;p&gt;With that, the PC finally joins the fleet pattern it was locked out of: sanoid snapshots the pool every hour, so a tired &lt;code&gt;rm -rf&lt;/code&gt;, mine or an agent&amp;rsquo;s, now costs at most an hour of work and a rollback, and a daily syncoid run sends the changed blocks to the NAS.&#10;restic is on borrowed time.&#10;Its six-hour timer keeps running until I trust the new path, and then it stops: the repository stays on the NAS as the last file-level snapshots of the machine, but nothing will be added to it.&lt;/p&gt;&#10;&lt;p&gt;Aftercare was the same short list, written down instead of remembered: revert the temporary root-SSH commit the installer needed, and put the restic password back where the backup service expects it.&lt;/p&gt;&#10;&lt;p&gt;The slow work, as always, was not the cutover.&#10;The slow work was making the cutover boring.&lt;/p&gt;&#10;&lt;h2 id="references"&gt;References &lt;a class="anchor" href="#references" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/proxmox-to-nixos/"&gt;I&amp;rsquo;ve gone full Nix: Proxmox to NixOS + Incus&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/truenas-to-nixos/"&gt;Migrating from TrueNAS to NixOS&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/homelab/"&gt;My homelab&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/dotfiles/pull/16" target="_blank" rel="noopener"&gt;The btrfs→ZFS migration PR&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/dotfiles/pull/67" target="_blank" rel="noopener"&gt;The PR that closed the silent backup-monitoring failure modes&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/nix-community/disko" target="_blank" rel="noopener"&gt;disko&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/nix-community/nixos-anywhere" target="_blank" rel="noopener"&gt;nixos-anywhere&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://restic.net/" target="_blank" rel="noopener"&gt;restic&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/jimsalterjrs/sanoid" target="_blank" rel="noopener"&gt;Sanoid&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;</description></item><item><title>Migrating from TrueNAS to NixOS without losing data after the build-system rug pull</title><link>https://www.nijho.lt/post/truenas-to-nixos/</link><pubDate>Sun, 28 Jun 2026 00:00:00 +0000</pubDate><guid isPermaLink="false">/post/truenas-to-nixos/</guid><description>&lt;p&gt;TrueNAS was the last non-NixOS machine in my home lab.&lt;/p&gt;&#10;&lt;p&gt;I kept postponing it for a simpler reason: moving something with ~100 TiB of data feels scary.&#10;My NAS holds the big ZFS pools.&#10;It has the SMB shares, NFS exports, snapshots, replication tasks, encrypted datasets, Incus state, Docker workloads, and all the boring-but-important health checks that are easy to take for granted until something fails.&lt;/p&gt;&#10;&lt;p&gt;I had already migrated most of my machines from Proxmox to NixOS with Incus, as I wrote about in &lt;a href="https://www.nijho.lt/post/proxmox-to-nixos/"&gt;I&amp;rsquo;ve gone full Nix: Proxmox to NixOS + Incus&lt;/a&gt;.&#10;That migration made me increasingly intolerant of appliance-style infrastructure.&#10;If the important state lives in a database behind a web UI, I cannot review it in a pull request.&#10;If I change something while debugging, I cannot guarantee the change made it back into the source of truth.&#10;And if I let an AI agent help me, imperative systems become even more uncomfortable: an agent can run a hundred commands, succeed, and leave behind a system that nobody can reproduce.&#10;For the NAS specifically, that basically meant I did not dare touch the machine with an AI agent at all.&lt;/p&gt;&#10;&lt;p&gt;NixOS is different.&#10;The diff is the state.&#10;If an agent changes my infrastructure, I can review the patch.&#10;If the change is wrong, I can reject it.&#10;If it works, I can commit it.&lt;/p&gt;&#10;&lt;p&gt;TrueNAS was the last holdout.&#10;It had been itching for a while.&#10;Then the &lt;a href="https://forums.truenas.com/t/clearing-the-air-on-build-scripts/64357" target="_blank" rel="noopener"&gt;build-system rug pull&lt;/a&gt; made the decision easy.&lt;/p&gt;&#10;&lt;details class="toc" open&gt;&lt;summary&gt;Table of contents&lt;/summary&gt;&lt;nav id="TableOfContents"&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#the-itch-before-the-last-straw"&gt;The itch before the last straw&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-last-straw"&gt;The last straw&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#why-this-was-scarier-than-proxmox"&gt;Why this was scarier than Proxmox&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#giving-an-agent-the-keys-carefully"&gt;Giving an agent the keys, carefully&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-nixos-scaffold"&gt;The NixOS scaffold&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-disko-problem"&gt;The disko problem&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#rehearsing-the-dangerous-part-in-a-vm"&gt;Rehearsing the dangerous part in a VM&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-parts-that-are-not-just-storage"&gt;The parts that are not just storage&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#secrets-stay-out-of-the-repo"&gt;Secrets stay out of the repo&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#where-this-leaves-truenas"&gt;Where this leaves TrueNAS&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-cutover"&gt;The cutover&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#references"&gt;References&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10;&lt;/nav&gt;&lt;/details&gt;&#10;&#10;&lt;h2 id="the-itch-before-the-last-straw"&gt;The itch before the last straw &lt;a class="anchor" href="#the-itch-before-the-last-straw" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The build-system change was not the first thing that bothered me.&#10;It was just the last straw.&lt;/p&gt;&#10;&lt;p&gt;The deeper problem was that my TrueNAS setup had slowly become complicated in exactly the way I dislike.&#10;I had clicked many buttons in the UI over time:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;SMB shares&lt;/li&gt;&#10;&lt;li&gt;NFS exports&lt;/li&gt;&#10;&lt;li&gt;snapshot tasks&lt;/li&gt;&#10;&lt;li&gt;replication tasks&lt;/li&gt;&#10;&lt;li&gt;users and groups&lt;/li&gt;&#10;&lt;li&gt;encrypted datasets&lt;/li&gt;&#10;&lt;li&gt;apps and containers&lt;/li&gt;&#10;&lt;li&gt;Incus storage&lt;/li&gt;&#10;&lt;li&gt;old Jailmaker/systemd-nspawn state&lt;/li&gt;&#10;&lt;li&gt;alerting&lt;/li&gt;&#10;&lt;li&gt;UPS settings&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;TrueNAS can export and import its configuration.&#10;That is genuinely useful.&#10;But a database export is not the same thing as a configuration I can comfortably review.&#10;When I look at a TrueNAS backup, it is not obvious to me which settings I intentionally changed, which settings are defaults, which settings are historical leftovers, and which settings only exist because I clicked something while debugging two years ago.&lt;/p&gt;&#10;&lt;p&gt;One concrete example was NFS.&#10;I needed the &lt;code&gt;crossmnt&lt;/code&gt; export option so child datasets would show up correctly inside the Docker container host, but TrueNAS did not expose that option in the UI.&#10;So I had a periodic root cron job patching &lt;code&gt;/etc/exports&lt;/code&gt; after TrueNAS generated it.&#10;It worked, but it was exactly the kind of small appliance hack that made me uneasy: partly outside the UI, partly outside the exported configuration, and very easy to forget during a migration.&#10;In NixOS, that behavior is just part of the export line.&lt;/p&gt;&#10;&lt;p&gt;That is the exact discomfort that pushed me away from Proxmox.&#10;I do not want to remember what I clicked.&#10;I want the system to remember it as code.&lt;/p&gt;&#10;&lt;p&gt;The second itch was virtualization.&#10;My TrueNAS container story had already gone through one migration.&#10;For a while I used &lt;a href="https://github.com/Jip-Hop/jailmaker" target="_blank" rel="noopener"&gt;Jailmaker&lt;/a&gt;, which is a clever script around &lt;code&gt;systemd-nspawn&lt;/code&gt; for running Linux &amp;ldquo;jails&amp;rdquo; on TrueNAS SCALE.&#10;It worked well enough for what I needed at the time: a Debian environment where I could run Docker workloads close to the data.&#10;But it also reinforced the feeling that I was building a fairly custom server on top of an appliance OS.&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://www.truenas.com/docs/scale/25.04/" target="_blank" rel="noopener"&gt;TrueNAS 25.04 &amp;ldquo;Fangtooth&amp;rdquo;&lt;/a&gt; introduced experimental Containers, named Instances in the early 25.04 releases, and the &lt;a href="https://www.truenas.com/blog/truenas-fangtooth-25-04-1/" target="_blank" rel="noopener"&gt;25.04.1 announcement&lt;/a&gt; explicitly described Instances as being based on Incus, supporting both VMs and LXCs.&#10;That was interesting to me because the older TrueNAS VM system was libvirt-based, while Incus felt like a more coherent container/VM story.&#10;Then the &lt;a href="https://forums.truenas.com/t/truenas-virtualization-plans-for-25-04-2/46236" target="_blank" rel="noopener"&gt;TrueNAS virtualization plan for 25.04.2&lt;/a&gt; explained that Fangtooth&amp;rsquo;s Instances feature caused challenges for some users and that 25.04.2 would re-enable the older Virtualization VM path alongside Instances.&#10;The &lt;a href="https://forums.truenas.com/t/truenas-25-04-2-is-now-available/49165" target="_blank" rel="noopener"&gt;25.04.2 release announcement&lt;/a&gt; made that split official: Virtual Machines came back, while VMs created through the earlier Instances feature continued to appear under Containers.&lt;/p&gt;&#10;&lt;p&gt;For many people that churn was probably annoying.&#10;For me it was especially ironic.&#10;I had migrated from Jailmaker&amp;rsquo;s &lt;code&gt;systemd-nspawn&lt;/code&gt; setup to Incus, read up on &lt;a href="https://linuxcontainers.org/incus/" target="_blank" rel="noopener"&gt;Incus&lt;/a&gt;, got excited about it, started using it, and then became genuinely happy with it when I migrated from Proxmox to NixOS with Incus.&#10;Incus fit my mental model perfectly: a clean CLI, containers and VMs in one place, easy scripting, and a workflow that agents can inspect.&lt;/p&gt;&#10;&lt;p&gt;Then TrueNAS started moving away from that direction again.&#10;Forum discussion around the 25.04.2 and later virtualization plans made it clear that Incus was not the stable long-term abstraction I hoped it would be inside TrueNAS.&#10;In the long-running &lt;a href="https://forums.truenas.com/t/linux-jails-containers-vms-with-incus/23599?page=21" target="_blank" rel="noopener"&gt;Linux Jails with Incus thread&lt;/a&gt;, Kris Moore is quoted saying that Incus is being removed from the base system and that libvirt will handle the backend for VMs and LXC.&#10;That probably makes sense for TrueNAS.&#10;They have enterprise users, compatibility concerns, and a support matrix that is very different from mine.&lt;/p&gt;&#10;&lt;p&gt;But for me it meant the NAS was again becoming an appliance whose internal direction I had to follow.&#10;I had just escaped that with Proxmox.&#10;I did not want to do it again for the most important machine in my house.&lt;/p&gt;&#10;&lt;h2 id="the-last-straw"&gt;The last straw &lt;a class="anchor" href="#the-last-straw" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Then I saw Jeff Geerling mention TrueNAS&amp;rsquo;s recent &amp;ldquo;shady behavior&amp;rdquo; in a video, and I started looking into what had actually changed.&lt;/p&gt;&#10;&lt;p&gt;The short version is that iXsystems made part of the TrueNAS ecosystem closed source.&#10;Specifically, iXsystems moved the TrueNAS build scripts and related build infrastructure internal for the TrueNAS 27 line.&#10;Their forum post, &lt;a href="https://forums.truenas.com/t/clearing-the-air-on-build-scripts/64357" target="_blank" rel="noopener"&gt;Clearing the Air on Build Scripts&lt;/a&gt;, frames this as a practical build-system decision and says normal installation and updates remain unaffected.&#10;The old &lt;a href="https://github.com/truenas/scale-build" target="_blank" rel="noopener"&gt;&lt;code&gt;truenas/scale-build&lt;/code&gt;&lt;/a&gt; repository now says it is preserved historically and is no longer the maintained build system.&#10;Community reactions, for example &lt;a href="https://forums.truenas.com/t/truenas-closing-its-build-system-has-sparked-a-significant-trust-crisis-in-the-self-hosted-and-engineering-communities/64549" target="_blank" rel="noopener"&gt;this TrueNAS forum thread&lt;/a&gt;, understandably read this as a meaningful step away from fully open development.&lt;/p&gt;&#10;&lt;p&gt;Would I ever have built TrueNAS from source myself?&#10;Almost certainly not.&lt;/p&gt;&#10;&lt;p&gt;That misses the point.&#10;I also rarely compile my Linux kernel manually, yet I care deeply that the ecosystem is open enough that I &lt;em&gt;could&lt;/em&gt; understand, rebuild, inspect, and fork the pieces if necessary.&#10;For a storage appliance, trust matters more than convenience.&#10;The NAS is not a toy VM.&#10;It is the machine that owns my data.&lt;/p&gt;&#10;&lt;p&gt;That was the final push.&#10;The UI state bothered me.&#10;The virtualization churn bothered me.&#10;The build-system change made the decision obvious.&lt;/p&gt;&#10;&lt;h2 id="why-this-was-scarier-than-proxmox"&gt;Why this was scarier than Proxmox &lt;a class="anchor" href="#why-this-was-scarier-than-proxmox" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Migrating Proxmox to NixOS was scary in the normal infrastructure sense.&#10;I had containers and VMs to move, but the blast radius was understandable.&#10;I could export with &lt;code&gt;vzdump&lt;/code&gt;, import into Incus, and test a lot of it in virtual machines.&lt;/p&gt;&#10;&lt;p&gt;Migrating TrueNAS is a different kind of scary.&#10;The data is not a VM disk that I can casually copy around.&#10;The important thing is &lt;em&gt;not&lt;/em&gt; to recreate the data pools.&#10;The important thing is to &lt;strong&gt;not touch them&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;The target architecture is simple in principle:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-nix" data-lang="nix"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Conceptually:&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# - disko owns only the boot disk&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# - existing data pools are imported by name&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;boot&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;zfs&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;extraPools&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="s2"&gt;&amp;#34;ssd&amp;#34;&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="s2"&gt;&amp;#34;tank&amp;#34;&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="p"&gt;];&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The NixOS boot disk can be destroyed and recreated.&#10;The existing &lt;code&gt;tank&lt;/code&gt; and &lt;code&gt;ssd&lt;/code&gt; pools cannot.&lt;/p&gt;&#10;&lt;p&gt;This is the part where many migration guides become hand-wavy:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Install the new OS.&lt;/li&gt;&#10;&lt;li&gt;Import your ZFS pools.&lt;/li&gt;&#10;&lt;li&gt;Good luck.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;That is not enough for me.&#10;I could physically access the machine, but unplugging the relevant NVMe hardware would mean taking apart more of the box than I wanted to touch.&#10;So I treated the cutover as if the disks had to stay connected.&#10;And I absolutely did not want one typo in a disk path to become yet another meme in AI agent failures.&lt;/p&gt;&#10;&lt;h2 id="giving-an-agent-the-keys-carefully"&gt;Giving an agent the keys, carefully &lt;a class="anchor" href="#giving-an-agent-the-keys-carefully" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Without AI this would probably have become a week-long project that I would forever postpone.&#10;With AI, it felt plausible to get the first serious version done in a single sitting.&#10;My approach was to give GPT 5.5 in xhigh mode SSH access to the live TrueNAS box and tell it, repeatedly and very explicitly, not to change anything.&#10;To be clear, it had root access.&#10;At this point these models have become powerful enough that I trust them to follow explicit instructions.&#10;The safety boundary was instruction-following, narrow scope, and review.&lt;/p&gt;&#10;&lt;p&gt;Not &amp;ldquo;please be careful.&amp;rdquo;&#10;More like:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;You can inspect.&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;You cannot change anything.&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Do not start or stop services.&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Do not import or export pools.&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Do not load keys.&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Do not mount datasets.&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Read only.&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This is the part where people either nod along or think I have completely lost my mind.&#10;I think the distinction matters.&#10;I did not ask an agent to &amp;ldquo;migrate my NAS.&amp;rdquo;&#10;I asked it to inspect the current system, summarize the live state, compare that against my NixOS repository, and propose declarative config.&lt;/p&gt;&#10;&lt;p&gt;Then I reviewed the diffs.&#10;Then I asked for another review.&#10;Then another.&#10;The process was messier than one neat two-agent pass: build a scaffold, ask a model to attack it, compare that against the live TrueNAS state, refine the scaffold, and repeat.&#10;GPT 5.5 did most of the initial construction.&#10;Claude Opus 4.8 on max effort did one of the later independent cross-checks against the live system.&#10;By the end, I trusted the result because multiple independent reviews had converged on the same assumptions, and I understood the remaining differences.&#10;The loop felt like code review: inspect live state, turn the desired parts into Nix, review the diff, and ask another model to attack it.&#10;The scariest assumption got a VM test, and the destructive step stayed small.&lt;/p&gt;&#10;&lt;p&gt;Byte-for-byte TrueNAS cloning was never the target.&#10;I wanted every important behavior explicit: storage import, shares, snapshots, replication, Incus recovery, monitoring, and the few places where NixOS intentionally differs from the old appliance.&#10;At that point, the NixOS config reproduced the parts of TrueNAS I actually depended on, and the remaining differences were deliberate.&lt;/p&gt;&#10;&lt;p&gt;The agent was excellent at inventory:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Which pools exist&lt;/li&gt;&#10;&lt;li&gt;Which datasets are encrypted&lt;/li&gt;&#10;&lt;li&gt;Which NFS exports are live&lt;/li&gt;&#10;&lt;li&gt;Which SMB shares exist&lt;/li&gt;&#10;&lt;li&gt;Which users and numeric IDs matter&lt;/li&gt;&#10;&lt;li&gt;What Incus storage pool is in use&lt;/li&gt;&#10;&lt;li&gt;What replication tasks exist&lt;/li&gt;&#10;&lt;li&gt;What SMART/NUT/health monitoring exists&lt;/li&gt;&#10;&lt;li&gt;What host ID ZFS expects&lt;/li&gt;&#10;&lt;li&gt;Which disk is the current boot pool&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Preserving everything blindly would have been wrong.&#10;The useful parts became code, and the dangerous parts became explicit.&lt;/p&gt;&#10;&lt;h2 id="the-nixos-scaffold"&gt;The NixOS scaffold &lt;a class="anchor" href="#the-nixos-scaffold" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The resulting NixOS host is split into small files:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;hosts/nas/&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;├── default.nix&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;├── disko.nix&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;├── hardware-configuration.nix&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;├── health.nix&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;├── identity.nix&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;├── networking.nix&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;├── nfs.nix&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;├── replication.nix&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;├── samba.nix&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;├── storage.nix&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;├── virtualization.nix&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;├── CUTOVER.md&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;└── PLANNING.md&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This is exactly why I like NixOS.&#10;The migration stopped being a list of steps I needed to follow and became a &lt;a href="https://github.com/basnijholt/dotfiles/pull/61/" target="_blank" rel="noopener"&gt;pull request&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;The important storage boundary is:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;code&gt;disko.nix&lt;/code&gt; describes only the boot disk.&lt;/li&gt;&#10;&lt;li&gt;The data pools are imported by name.&lt;/li&gt;&#10;&lt;li&gt;ZFS force-import is disabled.&lt;/li&gt;&#10;&lt;li&gt;Boot-time encrypted credential prompts are disabled.&lt;/li&gt;&#10;&lt;li&gt;Encrypted datasets are unlocked manually after boot.&lt;/li&gt;&#10;&lt;li&gt;Sanoid/Syncoid replace TrueNAS snapshot and replication tasks.&lt;/li&gt;&#10;&lt;li&gt;SMB, NFS, Docker, Incus, SMART, ZED, NUT, Netdata, and exporters are all declared in code.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;The data pools are intentionally &lt;em&gt;not&lt;/em&gt; in disko.&#10;That is the entire point.&lt;/p&gt;&#10;&lt;aside class="callout callout-note"&gt;&lt;svg class="ico" viewBox="0 0 256 256" aria-hidden="true"&gt;&lt;path d="M128,24A104,104,0,1,0,232,128,104.11,104.11,0,0,0,128,24Zm0,192a88,88,0,1,1,88-88A88.1,88.1,0,0,1,128,216Zm16-40a8,8,0,0,1-8,8,16,16,0,0,1-16-16V128a8,8,0,0,1,0-16,16,16,0,0,1,16,16v40A8,8,0,0,1,144,176ZM112,84a12,12,0,1,1,12,12A12,12,0,0,1,112,84Z"/&gt;&lt;/svg&gt;&lt;div&gt;The host is called &lt;code&gt;nas&lt;/code&gt; because that is the role I want to keep.&#10;TrueNAS was the old implementation.&#10;NixOS becomes the new one, while preserving the services and data I actually need.&lt;/div&gt;&lt;/aside&gt;&#10;&lt;h2 id="the-disko-problem"&gt;The disko problem &lt;a class="anchor" href="#the-disko-problem" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;&lt;a href="https://github.com/nix-community/disko" target="_blank" rel="noopener"&gt;&lt;code&gt;disko&lt;/code&gt;&lt;/a&gt; is a fantastic tool.&#10;It lets you describe disks declaratively and then formats/partitions/mounts them.&#10;For a fresh NixOS install, it is exactly what I want.&lt;/p&gt;&#10;&lt;p&gt;This also fits how I install NixOS machines.&#10;I build a custom &lt;a href="https://github.com/basnijholt/dotfiles/blob/main/configs/nixos/installers/iso.nix" target="_blank" rel="noopener"&gt;installer ISO&lt;/a&gt;, put it on a USB stick, and boot from it.&#10;The image already has SSH enabled with my keys, flakes enabled, and the tooling needed to run the repo-defined &lt;code&gt;disko&lt;/code&gt; and &lt;code&gt;nixos-install&lt;/code&gt; flow.&#10;That turns the installer environment into part of the reviewed configuration, instead of another place where I have to remember which choices to make.&lt;/p&gt;&#10;&lt;p&gt;It is also exactly the tool that can ruin your day if pointed at the wrong disk.&lt;/p&gt;&#10;&lt;p&gt;My requirement was:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;Use disko to destroy and recreate the boot disk, but prove it cannot touch the existing ZFS data pools.&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;The static config already looked right.&#10;The generated disko script only referenced the boot device and generated partition labels.&#10;The data pools were only present under &lt;code&gt;boot.zfs.extraPools&lt;/code&gt;.&lt;/p&gt;&#10;&lt;p&gt;But &amp;ldquo;looks right&amp;rdquo; is not enough when the downside is wiping a NAS.&lt;/p&gt;&#10;&lt;p&gt;So we built a VM rehearsal.&lt;/p&gt;&#10;&lt;h2 id="rehearsing-the-dangerous-part-in-a-vm"&gt;Rehearsing the dangerous part in a VM &lt;a class="anchor" href="#rehearsing-the-dangerous-part-in-a-vm" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The VM test creates a miniature version of the dangerous situation:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Attach several throwaway disks to a disposable NixOS VM.&lt;/li&gt;&#10;&lt;li&gt;Create a fake &lt;code&gt;boot-pool&lt;/code&gt; on one disk.&lt;/li&gt;&#10;&lt;li&gt;Create fake &lt;code&gt;tank&lt;/code&gt; and &lt;code&gt;ssd&lt;/code&gt; ZFS pools on other disks.&lt;/li&gt;&#10;&lt;li&gt;Write sentinel files into the fake data pools.&lt;/li&gt;&#10;&lt;li&gt;Export the fake data pools.&lt;/li&gt;&#10;&lt;li&gt;Run the generated &lt;code&gt;nas&lt;/code&gt; disko script against the fake boot disk.&lt;/li&gt;&#10;&lt;li&gt;Confirm the boot disk now contains the new &lt;code&gt;zroot&lt;/code&gt;.&lt;/li&gt;&#10;&lt;li&gt;Confirm fake &lt;code&gt;tank&lt;/code&gt; and &lt;code&gt;ssd&lt;/code&gt; still have their ZFS labels.&lt;/li&gt;&#10;&lt;li&gt;Re-import fake &lt;code&gt;tank&lt;/code&gt; and &lt;code&gt;ssd&lt;/code&gt;.&lt;/li&gt;&#10;&lt;li&gt;Read the sentinel files.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;The check lives in the flake now:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; configs/nixos&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;nix build .#checks.x86_64-linux.nas-disko-safety&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;It passed.&lt;/p&gt;&#10;&lt;p&gt;Passing that VM test gives me confidence in the generated Nix/disko logic.&#10;The read-only check on the live TrueNAS box gives me confidence in the configured disk target: the by-id path resolves to the 500 GB &lt;code&gt;boot-pool&lt;/code&gt; disk, and &lt;code&gt;tank&lt;/code&gt; and &lt;code&gt;ssd&lt;/code&gt; live on different devices.&#10;The installer preflight repeats that same check immediately before the destructive step.&lt;/p&gt;&#10;&lt;p&gt;This is the level of paranoia I want around storage migrations.&lt;/p&gt;&#10;&lt;h2 id="the-parts-that-are-not-just-storage"&gt;The parts that are not just storage &lt;a class="anchor" href="#the-parts-that-are-not-just-storage" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Once the &amp;ldquo;do not wipe the pools&amp;rdquo; boundary was in place, the rest of the migration became more normal infrastructure work.&#10;Still annoying, but normal.&lt;/p&gt;&#10;&lt;p&gt;SMB was not a byte-for-byte port.&#10;TrueNAS ships private Samba VFS modules and has its own ACL/middleware behavior.&#10;Stock NixOS Samba covers the parts I need with &lt;code&gt;fruit&lt;/code&gt;, &lt;code&gt;streams_xattr&lt;/code&gt;, and sensible share definitions, but it is not literally the same stack.&#10;So the plan calls out what must be tested from real clients: Time Machine, guest access, and photo/media access.&lt;/p&gt;&#10;&lt;p&gt;Snapshots and replication also changed.&#10;TrueNAS snapshot tasks become Sanoid policy.&#10;TrueNAS replication tasks become Syncoid systemd timers.&#10;Existing snapshots are preserved, but Sanoid will not magically prune old TrueNAS-named snapshots.&#10;That is a feature, not a bug.&#10;I would rather manually decide when old snapshots age out than have a new tool silently &amp;ldquo;clean up&amp;rdquo; history.&lt;/p&gt;&#10;&lt;p&gt;Incus is another subtle one.&#10;The storage pool lives on a data pool, so disko will not touch it.&#10;But a fresh NixOS install has a fresh Incus database.&#10;The plan is to run &lt;code&gt;incus admin recover&lt;/code&gt;, then apply a small declarative reconciler for the known instances.&#10;The state boundary has to be clear: preserve the storage dataset, recover the Incus database, then reconcile the instance config.&lt;/p&gt;&#10;&lt;p&gt;Health monitoring is also declared:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;SMARTD&lt;/li&gt;&#10;&lt;li&gt;ZFS Event Daemon&lt;/li&gt;&#10;&lt;li&gt;NUT/UPS client&lt;/li&gt;&#10;&lt;li&gt;Netdata bound locally&lt;/li&gt;&#10;&lt;li&gt;Prometheus exporters&lt;/li&gt;&#10;&lt;li&gt;A shared alert hook that can log, wall, and optionally send ntfy alerts&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;TrueNAS gives you many of these things in the UI.&#10;NixOS gives them to me as code.&lt;/p&gt;&#10;&lt;p&gt;I know using your NAS for other services is a bit of an anti-pattern.&#10;In an ideal world, the storage box just stores data and stays boring.&#10;But when I originally bought and configured this machine, it became the most powerful machine in my home lab.&#10;So it naturally started attracting the Docker workloads too.&#10;Most of those workloads are not resource intensive, and keeping them close to the data is genuinely convenient.&#10;At one point I was running more than a hundred containers on that machine and it barely made a dent.&#10;They ran inside LXC containers on Incus rather than directly on the TrueNAS host, which made it feel like a reasonable compromise for a long time.&lt;/p&gt;&#10;&lt;p&gt;The migration also became a chance to fix a real operational problem.&#10;My worst TrueNAS incident was a long OOM death spiral: no swap, too many unbounded containers, and services repeatedly getting killed and restarted.&#10;The philosophy came from Nix and open infrastructure.&#10;The OOM incident was the practical reminder that the NAS had become a general-purpose compute host.&#10;In the NixOS version, container memory limits, zram, earlyoom, and an explicit ZFS ARC cap are part of the configuration instead of being tribal knowledge or post-incident notes.&lt;/p&gt;&#10;&lt;h2 id="secrets-stay-out-of-the-repo"&gt;Secrets stay out of the repo &lt;a class="anchor" href="#secrets-stay-out-of-the-repo" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;My dotfiles are public.&#10;That makes the migration more interesting.&lt;/p&gt;&#10;&lt;p&gt;The Nix config necessarily contains some operational facts: hostnames, share names, service definitions, and so on.&#10;But the plan deliberately keeps secrets and sensitive cutover material out of git.&lt;/p&gt;&#10;&lt;p&gt;For this migration, that means:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;ZFS dataset passphrases and unlock material stay off-box and outside the repo.&lt;/li&gt;&#10;&lt;li&gt;Replication private keys are installed manually under &lt;code&gt;/etc/ssh&lt;/code&gt;.&lt;/li&gt;&#10;&lt;li&gt;Inbound authorized keys for backup senders are installed during cutover.&lt;/li&gt;&#10;&lt;li&gt;Alerting secrets live in a runtime env file.&lt;/li&gt;&#10;&lt;li&gt;A local &lt;code&gt;~/nas-cutover/&lt;/code&gt; staging directory can exist, but it is explicitly not part of the repo and should not be casually read by agents.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;One important detail: the encrypted datasets use passphrase keys.&#10;In the TrueNAS setup I handled that with &lt;a href="https://github.com/basnijholt/truenas-unlock" target="_blank" rel="noopener"&gt;truenas-unlock&lt;/a&gt;, a small tool I wrote for this exact problem.&#10;The unlock material lives on another device; when that device is on the same network, it can unlock the datasets through the TrueNAS API.&#10;That gave me a lightweight hardware/network-presence factor: the NAS could boot, and the encrypted datasets only unlocked when the separate unlock device was present too.&lt;/p&gt;&#10;&lt;p&gt;That changes the migration footgun.&#10;The TrueNAS API path does not survive the cutover as-is, so I split the same idea out into &lt;a href="https://github.com/basnijholt/zfs-unlock" target="_blank" rel="noopener"&gt;zfs-unlock&lt;/a&gt;: the NixOS/OpenZFS version that talks to a restricted SSH receiver instead.&#10;During the migration I still kept an independent manual passphrase recovery path, because I do not want the automatic unlock mechanism to be the only way back into my data.&lt;/p&gt;&#10;&lt;h2 id="where-this-leaves-truenas"&gt;Where this leaves TrueNAS &lt;a class="anchor" href="#where-this-leaves-truenas" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;I still like TrueNAS.&#10;It got me very far.&#10;It made ZFS approachable.&#10;It gave me a good NAS UI when I wanted a NAS UI.&#10;And if you want an appliance that mostly owns storage for you, it is still a very compelling project.&lt;/p&gt;&#10;&lt;p&gt;I like NixOS more for my own infrastructure.&#10;The most important machine in my house should live in reviewable code instead of mutable appliance state spread across a UI, a database, and old debugging decisions.&#10;NixOS and AI are a particularly good match for that.&#10;I can describe messy infrastructure intent in imprecise English, let the agent turn that into exact Nix code, and review the diff before it becomes system state.&#10;The prompt stays fuzzy.&#10;The machine state does not.&lt;/p&gt;&#10;&lt;p&gt;After the Proxmox migration, TrueNAS was the last major exception.&#10;This migration removes that exception.&lt;/p&gt;&#10;&lt;h2 id="the-cutover"&gt;The cutover &lt;a class="anchor" href="#the-cutover" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;I ended up using a phased &lt;a href="https://github.com/nix-community/nixos-anywhere" target="_blank" rel="noopener"&gt;&lt;code&gt;nixos-anywhere&lt;/code&gt;&lt;/a&gt; cutover instead of the USB installer path.&#10;The important safety property stayed the same: first kexec into a temporary NixOS installer, stop there, run the disk preflight from inside that installer, and only then run the destructive &lt;code&gt;disko,install,reboot&lt;/code&gt; phase.&#10;Before the destructive phase, the box was running the installer in RAM and the disks had not been intentionally modified yet.&#10;That gave me a real checkpoint where aborting was still cheap.&lt;/p&gt;&#10;&lt;p&gt;I kept my hands on the few commands that actually changed the machine.&#10;I ran the &lt;code&gt;nixos-anywhere&lt;/code&gt; phases and the later &lt;code&gt;nixos-rebuild&lt;/code&gt; commands myself.&#10;The agent stayed next to it, reading the outputs, checking the assumptions, SSHing in to verify pool health, services, mounts, Incus state, NFS clients, and then turning any findings back into code or documentation.&#10;That split felt right to me: I pressed enter on the small number of irreversible commands, and the AI did the tedious verification work that I would otherwise be tempted to rush.&lt;/p&gt;&#10;&lt;p&gt;The actual migration was almost anticlimactic compared to the preparation.&#10;From the moment TrueNAS stopped being the running OS to having the Incus containers back with my hundred-plus services running again took less than 20 minutes.&#10;The slow work was not the cutover.&#10;The slow work was making the cutover boring.&lt;/p&gt;&#10;&lt;details&gt;&#10;&lt;summary&gt;The small things that still needed fixing during cutover&lt;/summary&gt;&#10;&lt;p&gt;There were a few small first-boot reconciliations. I am writing them down mostly for future readers who want to follow a similar path:&lt;/p&gt;&#10;&lt;ul&gt;&#10; &lt;li&gt;imported data-pool mountpoints needed to be reconciled to the &lt;code&gt;/mnt/...&lt;/code&gt; paths my clients and services already used;&lt;/li&gt;&#10; &lt;li&gt;encrypted datasets needed a better manual post-boot unlock helper, and the old TrueNAS API unlock flow needed a NixOS/OpenZFS successor;&lt;/li&gt;&#10; &lt;li&gt;Incus needed &lt;code&gt;incus admin recover&lt;/code&gt; because the storage pool survived but the new OS had a fresh Incus database;&lt;/li&gt;&#10; &lt;li&gt;one unprivileged recovered container needed the matching subordinate UID/GID ranges declared for its passthrough idmap;&lt;/li&gt;&#10; &lt;li&gt;&lt;code&gt;nas.local&lt;/code&gt; needed an explicit DNS record so my wildcard did not send it to a workload container;&lt;/li&gt;&#10; &lt;li&gt;the old PC job that backed up the TrueNAS API config needed to be removed;&lt;/li&gt;&#10; &lt;li&gt;the PC NFS mounts, Nix cache endpoints, and recovered Docker workload container all needed client-side validation.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Those findings went back into the cutover runbooks and the Nix config in a &lt;a href="https://github.com/basnijholt/dotfiles/pull/62"&gt;follow-up PR&lt;/a&gt;, so the notes are available for anyone who might benefit from them later.&lt;/p&gt;&#10;&lt;/details&gt;&#10;&lt;p&gt;At the end of the cutover, the machine was &lt;code&gt;nas&lt;/code&gt;, the ZFS pools were healthy, the NFS mounts worked from my PC, the Incus containers were recovered, and the Docker workloads were running again.&#10;SMB authentication, guest access, Time Machine, and normal media browsing from macOS Finder worked after one final share-root permission fix.&#10;At that point the migration was working end to end: the pools were healthy and the services I actually use were back.&lt;/p&gt;&#10;&lt;h2 id="references"&gt;References &lt;a class="anchor" href="#references" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/proxmox-to-nixos/"&gt;I&amp;rsquo;ve gone full Nix: Proxmox to NixOS + Incus&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/homelab/"&gt;My homelab: from a single Raspberry Pi to a Proxmox cluster and a dedicated NAS&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;On agentic coding&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://forums.truenas.com/t/clearing-the-air-on-build-scripts/64357" target="_blank" rel="noopener"&gt;TrueNAS forum: Clearing the Air on Build Scripts&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/truenas/scale-build" target="_blank" rel="noopener"&gt;&lt;code&gt;truenas/scale-build&lt;/code&gt; on GitHub&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://forums.truenas.com/t/truenas-closing-its-build-system-has-sparked-a-significant-trust-crisis-in-the-self-hosted-and-engineering-communities/64549" target="_blank" rel="noopener"&gt;TrueNAS forum: build-system trust crisis discussion&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.truenas.com/docs/scale/25.04/" target="_blank" rel="noopener"&gt;TrueNAS 25.04 documentation&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.truenas.com/blog/truenas-fangtooth-25-04-1/" target="_blank" rel="noopener"&gt;TrueNAS 25.04.1: Fangtooth Unification Gains Momentum&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://forums.truenas.com/t/truenas-virtualization-plans-for-25-04-2/46236" target="_blank" rel="noopener"&gt;TrueNAS Virtualization Plans for 25.04.2&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://forums.truenas.com/t/truenas-25-04-2-is-now-available/49165" target="_blank" rel="noopener"&gt;TrueNAS 25.04.2 release announcement&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://forums.truenas.com/t/linux-jails-containers-vms-with-incus/23599?page=21" target="_blank" rel="noopener"&gt;Linux Jails with Incus forum thread&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/Jip-Hop/jailmaker" target="_blank" rel="noopener"&gt;Jailmaker&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/truenas-unlock" target="_blank" rel="noopener"&gt;truenas-unlock&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/zfs-unlock" target="_blank" rel="noopener"&gt;zfs-unlock&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/dotfiles/pull/61" target="_blank" rel="noopener"&gt;The NAS NixOS scaffold PR&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;</description></item><item><title>Parallel agentic coding made trivial with `agent-cli dev`</title><link>https://www.nijho.lt/post/parallel-agentic-coding/</link><pubDate>Tue, 13 Jan 2026 00:00:00 +0000</pubDate><guid isPermaLink="false">/post/parallel-agentic-coding/</guid><description>&lt;details class="toc" open&gt;&lt;summary&gt;Table of contents&lt;/summary&gt;&lt;nav id="TableOfContents"&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#1-the-just-use-worktrees-problem"&gt;1. The &amp;ldquo;just use worktrees&amp;rdquo; problem&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#2-why-parallel-development-matters-for-agentic-coding"&gt;2. Why parallel development matters for agentic coding&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#3-one-command-to-rule-them-all"&gt;3. One command to rule them all&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#4-it-knows-your-stack"&gt;4. It knows your stack&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#5-terminal-magic"&gt;5. Terminal magic&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#6-spawning-agents-with-prompts"&gt;6. Spawning agents with prompts&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#7-teaching-claude-to-spawn-agents"&gt;7. Teaching Claude to spawn agents&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#8-my-actual-workflow"&gt;8. My actual workflow&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#9-managing-environments"&gt;9. Managing environments&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#10-getting-started"&gt;10. Getting started&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#conclusion"&gt;Conclusion&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#links"&gt;Links&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10;&lt;/nav&gt;&lt;/details&gt;&#10;&#10;&lt;h2 id="1-the-just-use-worktrees-problem"&gt;1. The &amp;ldquo;just use worktrees&amp;rdquo; problem &lt;a class="anchor" href="#1-the-just-use-worktrees-problem" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Last week, I was chatting with a friend about my &lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;agentic coding workflow&lt;/a&gt;.&#10;I was sharing some of my best practices, and when the topic of parallel development came up, I said:&lt;/p&gt;&#10;&lt;p&gt;&amp;ldquo;Just use git worktrees with quickly installable environments.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;He stared at me blankly.&lt;/p&gt;&#10;&lt;p&gt;And then it hit me: for most developers who just &lt;code&gt;git add&lt;/code&gt;, &lt;code&gt;git commit&lt;/code&gt;, &lt;code&gt;git push&lt;/code&gt; and don&amp;rsquo;t touch their environment setup once it works, this is &lt;em&gt;not&lt;/em&gt; trivial.&#10;What seems obvious to me involves:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Understanding what git worktrees even are&lt;/li&gt;&#10;&lt;li&gt;Knowing the &lt;code&gt;git worktree add&lt;/code&gt; command and its flags&lt;/li&gt;&#10;&lt;li&gt;Remembering to fetch before creating&lt;/li&gt;&#10;&lt;li&gt;Creating a sibling directory structure&lt;/li&gt;&#10;&lt;li&gt;Running your package manager&amp;rsquo;s install command&lt;/li&gt;&#10;&lt;li&gt;Copying over &lt;code&gt;.env&lt;/code&gt; files&lt;/li&gt;&#10;&lt;li&gt;Setting up direnv or manually activating your virtual environment&lt;/li&gt;&#10;&lt;li&gt;Opening a new terminal tab&lt;/li&gt;&#10;&lt;li&gt;Navigating to the worktree&lt;/li&gt;&#10;&lt;li&gt;Finally launching your coding agent&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;That&amp;rsquo;s a lot of friction for something you want to do &lt;em&gt;frequently&lt;/em&gt; when using agentic tools.&lt;/p&gt;&#10;&lt;p&gt;So I built &lt;code&gt;agent-cli dev&lt;/code&gt;.&lt;/p&gt;&#10;&lt;aside class="callout callout-note"&gt;&lt;svg class="ico" viewBox="0 0 256 256" aria-hidden="true"&gt;&lt;path d="M128,24A104,104,0,1,0,232,128,104.11,104.11,0,0,0,128,24Zm0,192a88,88,0,1,1,88-88A88.1,88.1,0,0,1,128,216Zm16-40a8,8,0,0,1-8,8,16,16,0,0,1-16-16V128a8,8,0,0,1,0-16,16,16,0,0,1,16,16v40A8,8,0,0,1,144,176ZM112,84a12,12,0,1,1,12,12A12,12,0,0,1,112,84Z"/&gt;&lt;/svg&gt;&lt;div&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; &lt;code&gt;agent-cli dev new --agent --prompt &amp;quot;Fix the login bug&amp;quot;&lt;/code&gt; creates a complete, isolated development environment in one command.&#10;It creates a git worktree, installs dependencies, copies env files, sets up direnv, and opens your AI coding agent in a new terminal tab with your prompt already loaded—all automatically.&#10;No more manual setup, no more excuses to not work in parallel.&lt;/div&gt;&lt;/aside&gt;&#10;&lt;h2 id="2-why-parallel-development-matters-for-agentic-coding"&gt;2. Why parallel development matters for agentic coding &lt;a class="anchor" href="#2-why-parallel-development-matters-for-agentic-coding" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;In my &lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;previous post on agentic coding&lt;/a&gt;, I described my workflow of running 5-6 Claude Code sessions simultaneously, each working on a different feature.&#10;This is how I can easily work on multiple features in parallel while waiting for an agent to process and generate code.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;The usual way:&lt;/strong&gt;&#10;Start feature A → wait for Claude to finish → review → move to feature B → repeat.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;The better way:&lt;/strong&gt;&#10;Start feature A in tab 1 → switch to tab 2, start feature B while A is working → switch to tab 3, start feature C → circle back to tab 1, review what Claude did → give feedback, move to next tab → repeat every 10-15 minutes.&lt;/p&gt;&#10;&lt;p&gt;This parallel approach allows me to go much faster.&#10;But it only works if each tab has its own &lt;strong&gt;completely isolated and working environment&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;That&amp;rsquo;s where &lt;a href="https://www.nijho.lt/post/git-worktree/"&gt;git worktrees&lt;/a&gt; come in.&#10;A worktree gives you a separate working directory for a branch, sharing the same git history but with independent file states.&lt;/p&gt;&#10;&lt;p&gt;The problem is the &lt;em&gt;setup&lt;/em&gt;.&#10;Every time you want to start a new feature:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# The manual way (don&amp;#39;t do this)&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;git fetch origin&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;git worktree add ../my-project-worktrees/cool-feature -b cool-feature origin/main&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; ../my-project-worktrees/cool-feature&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;uv sync --all-extras &lt;span class="c1"&gt;# or npm install, or poetry install, or...&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;cp ../.env .env&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Now open a new terminal tab...&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Navigate there...&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Finally start claude&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;After the 100th(?) time doing this manually, I knew I needed to automate it.&lt;/p&gt;&#10;&lt;h2 id="3-one-command-to-rule-them-all"&gt;3. One command to rule them all &lt;a class="anchor" href="#3-one-command-to-rule-them-all" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Here&amp;rsquo;s what I built:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev new --agent&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;That&amp;rsquo;s it.&#10;One command.&#10;Here&amp;rsquo;s what it looks like:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;→ Generated branch name: cool-crane&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;→ Creating worktree &lt;span class="k"&gt;for&lt;/span&gt; branch &lt;span class="s1"&gt;&amp;#39;cool-crane&amp;#39;&lt;/span&gt;...&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;→ Running: git fetch origin&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;→ Running: git worktree add -b cool-crane ~/Work/project-worktrees/cool-crane origin/main&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;✓ Created worktree at ~/Work/project-worktrees/cool-crane&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;✓ Copied env file&lt;span class="o"&gt;(&lt;/span&gt;s&lt;span class="o"&gt;)&lt;/span&gt;: .env.example, .envrc&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;→ Detected Python project with uv&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;→ Running: uv sync --all-extras&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;→ Running: direnv allow&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;✓ direnv: allowed existing .envrc&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;✓ Started claude in new iterm2 tab&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;╭─────────────────────────────────────────────── Success ───────────────────────────────────────────────╮&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;│ Dev environment created: ~/Work/project-worktrees/cool-crane │&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;│ Branch: cool-crane │&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;╰───────────────────────────────────────────────────────────────────────────────────────────────────────╯&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;4 seconds later, I have a new terminal tab with Claude Code already running in a fresh, isolated environment.&#10;Ready to work on my next feature.&lt;/p&gt;&#10;&lt;p&gt;What happens under the hood:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&lt;strong&gt;Generates a random branch name&lt;/strong&gt; like &lt;code&gt;clever-fox&lt;/code&gt; (you can just set the name yourself of course)&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Creates the git worktree&lt;/strong&gt; in a sibling directory&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Detects the project type&lt;/strong&gt; and runs the appropriate setup (&lt;code&gt;uv sync&lt;/code&gt;, &lt;code&gt;npm install&lt;/code&gt;, etc.)&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Copies &lt;code&gt;.env&lt;/code&gt; files&lt;/strong&gt; from the main repo&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Sets up direnv&lt;/strong&gt; so the environment activates automatically&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Opens a new terminal tab&lt;/strong&gt; (works with tmux, zellij, iTerm2, and more)&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Launches your coding agent&lt;/strong&gt; in that tab&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;The Docker-style random names (&lt;code&gt;clever-fox&lt;/code&gt;, &lt;code&gt;happy-bear&lt;/code&gt;, &lt;code&gt;swift-owl&lt;/code&gt;) there just for those too lazy to pick a name.&#10;Just &lt;code&gt;agent-cli dev new --agent&lt;/code&gt; and start coding.&lt;/p&gt;&#10;&lt;h2 id="4-it-knows-your-stack"&gt;4. It knows your stack &lt;a class="anchor" href="#4-it-knows-your-stack" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The command auto-detects your project type:&lt;/p&gt;&#10;&lt;div class="table-wrap"&gt;&#10;&lt;table&gt;&#10;&lt;thead&gt;&#10;&lt;tr&gt;&#10;&lt;th&gt;If it sees&amp;hellip;&lt;/th&gt;&#10;&lt;th&gt;It runs&amp;hellip;&lt;/th&gt;&#10;&lt;/tr&gt;&#10;&lt;/thead&gt;&#10;&lt;tbody&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;&lt;code&gt;uv.lock&lt;/code&gt;&lt;/td&gt;&#10;&lt;td&gt;&lt;code&gt;uv sync --all-extras&lt;/code&gt;&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;&lt;code&gt;pixi.lock&lt;/code&gt;&lt;/td&gt;&#10;&lt;td&gt;&lt;code&gt;pixi install&lt;/code&gt;&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;&lt;code&gt;poetry.lock&lt;/code&gt;&lt;/td&gt;&#10;&lt;td&gt;&lt;code&gt;poetry install&lt;/code&gt;&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;&lt;code&gt;requirements.yaml&lt;/code&gt;&lt;/td&gt;&#10;&lt;td&gt;&lt;code&gt;unidep install -e .&lt;/code&gt;&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;&lt;code&gt;package-lock.json&lt;/code&gt;&lt;/td&gt;&#10;&lt;td&gt;&lt;code&gt;npm install&lt;/code&gt;&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;&lt;code&gt;Cargo.toml&lt;/code&gt;&lt;/td&gt;&#10;&lt;td&gt;&lt;code&gt;cargo build&lt;/code&gt;&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;&lt;code&gt;go.mod&lt;/code&gt;&lt;/td&gt;&#10;&lt;td&gt;&lt;code&gt;go mod download&lt;/code&gt;&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;For my projects using &lt;a href="https://github.com/basnijholt/unidep" target="_blank" rel="noopener"&gt;unidep&lt;/a&gt;, it even detects monorepos and adjusts the command accordingly.&lt;/p&gt;&#10;&lt;p&gt;It also generates the right &lt;code&gt;.envrc&lt;/code&gt; for &lt;a href="https://direnv.net/" target="_blank" rel="noopener"&gt;direnv&lt;/a&gt;.&#10;For a Python project with uv, that&amp;rsquo;s &lt;code&gt;source .venv/bin/activate&lt;/code&gt;.&#10;For a conda/unidep project, it&amp;rsquo;s the full micromamba activation.&#10;For Nix projects, it&amp;rsquo;s &lt;code&gt;use flake&lt;/code&gt;.&lt;/p&gt;&#10;&lt;p&gt;This means when you &lt;code&gt;cd&lt;/code&gt; into the worktree later, your environment is automatically activated.&#10;No more &lt;code&gt;source .venv/bin/activate&lt;/code&gt;.&lt;/p&gt;&#10;&lt;h2 id="5-terminal-magic"&gt;5. Terminal magic &lt;a class="anchor" href="#5-terminal-magic" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The real magic is opening a new terminal tab with the agent already running.&lt;/p&gt;&#10;&lt;p&gt;The command detects which terminal you&amp;rsquo;re in and uses the appropriate API—whether that&amp;rsquo;s iTerm2, Kitty, Warp, or GNOME Terminal.&#10;It even works with terminal multiplexers like &lt;strong&gt;tmux&lt;/strong&gt; and &lt;strong&gt;zellij&lt;/strong&gt; (my current favorite), opening a new window/tab in your existing session.&lt;/p&gt;&#10;&lt;h2 id="6-spawning-agents-with-prompts"&gt;6. Spawning agents with prompts &lt;a class="anchor" href="#6-spawning-agents-with-prompts" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The &lt;code&gt;--prompt&lt;/code&gt; option transforms how I spawn parallel agents.&#10;Instead of just opening a blank Claude session, I can give the new agent its task immediately:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev new fix-auth-bug --agent --prompt &lt;span class="s2"&gt;&amp;#34;Fix the login validation bug in auth.py. The issue is that empty passwords pass validation.&amp;#34;&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The agent opens with the prompt already loaded and starts working immediately.&#10;No copy-pasting, no context switching, no &amp;ldquo;let me explain what I need you to do.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;For longer, more detailed prompts (which you should use for complex tasks), there&amp;rsquo;s &lt;code&gt;--prompt-file&lt;/code&gt;:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev new new-feature --agent --prompt-file .claude/spawn-prompt.md&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This is particularly powerful when you&amp;rsquo;re in a Claude session and discover a feature that needs work but is unrelated to your current task.&#10;Instead of context-switching or noting it for later, you can spawn a new agent right there:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Write a detailed prompt to a file (Claude can do this)&lt;/li&gt;&#10;&lt;li&gt;Run &lt;code&gt;agent-cli dev new unrelated-feature --agent --prompt-file .claude/spawn-prompt.md&lt;/code&gt;&lt;/li&gt;&#10;&lt;li&gt;A new terminal tab opens with a fresh Claude session already working on the task&lt;/li&gt;&#10;&lt;li&gt;Continue with your original work&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;The spawned agent works independently in its own branch while you stay focused.&lt;/p&gt;&#10;&lt;h2 id="7-teaching-claude-to-spawn-agents"&gt;7. Teaching Claude to spawn agents &lt;a class="anchor" href="#7-teaching-claude-to-spawn-agents" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Here&amp;rsquo;s where it gets really interesting: you can teach Claude Code itself how to spawn parallel agents.&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev install-skill&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This installs a &lt;a href="https://docs.anthropic.com/en/docs/claude-code/skills" target="_blank" rel="noopener"&gt;Claude Code skill&lt;/a&gt; that teaches Claude how to use &lt;code&gt;agent-cli dev&lt;/code&gt;.&#10;The skill includes detailed examples and prompt templates following Anthropic&amp;rsquo;s &lt;a href="https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/overview" target="_blank" rel="noopener"&gt;prompt engineering guide&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;With the skill installed, you can say things like:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&amp;ldquo;Work on auth, payments, and notifications in parallel&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&amp;ldquo;This feature is unrelated to what we&amp;rsquo;re doing—spawn a new agent for it&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&amp;ldquo;Split this refactoring by module and work on them simultaneously&amp;rdquo;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Claude will write well-structured prompts (using proper XML tags, clear context, explicit requirements) and spawn the agents for you.&#10;Each spawned agent writes a report to &lt;code&gt;.claude/REPORT.md&lt;/code&gt; when done, so you can easily review what happened.&lt;/p&gt;&#10;&lt;p&gt;One of my favorite patterns: I ask Claude to look at the latest 10 open GitHub issues and spawn an agent for each one.&#10;Ten independent parallel environments, set up in seconds, each working on a different issue.&#10;That&amp;rsquo;s the kind of leverage this enables.&lt;/p&gt;&#10;&lt;h2 id="8-my-actual-workflow"&gt;8. My actual workflow &lt;a class="anchor" href="#8-my-actual-workflow" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Here&amp;rsquo;s how I use this in practice.&#10;I&amp;rsquo;m working on &lt;a href="https://github.com/basnijholt/agent-cli" target="_blank" rel="noopener"&gt;agent-cli&lt;/a&gt; itself, and I want to add three features:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Tab 1: New RAG feature&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev new rag-improvements --agent --prompt &lt;span class="s2"&gt;&amp;#34;Improve RAG chunking strategy for better retrieval accuracy&amp;#34;&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Tab 2: Fix a bug in the transcribe command&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev new fix-transcribe-vad --agent --prompt &lt;span class="s2"&gt;&amp;#34;Fix VAD detection cutting off words at sentence boundaries&amp;#34;&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Tab 3: Refactor the config system&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev new config-refactor --agent --prompt &lt;span class="s2"&gt;&amp;#34;Refactor config.py to use a single Config class with lazy loading&amp;#34;&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Three commands, three isolated environments, three Claude Code sessions already working on their tasks.&lt;/p&gt;&#10;&lt;p&gt;I cycle through the tabs every 10-15 minutes:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Review what Claude did&lt;/li&gt;&#10;&lt;li&gt;Give voice feedback using my &lt;a href="https://www.nijho.lt/post/local-ai-journey/"&gt;transcription workflow&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;Move to the next tab&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;When a feature is done, I have Claude open a PR from that branch.&#10;When the PR is merged:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev clean --merged&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This uses the GitHub CLI to check which branches have merged PRs, then removes those worktrees and deletes the branches.&#10;No more zombie worktrees cluttering my disk.&lt;/p&gt;&#10;&lt;h2 id="9-managing-environments"&gt;9. Managing environments &lt;a class="anchor" href="#9-managing-environments" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;A few other commands I use regularly:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# List all worktrees&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev list&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Navigate to a worktree&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; &lt;span class="s2"&gt;&amp;#34;&lt;/span&gt;&lt;span class="k"&gt;$(&lt;/span&gt;agent-cli dev path clever-fox&lt;span class="k"&gt;)&lt;/span&gt;&lt;span class="s2"&gt;&amp;#34;&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Remove a worktree&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev rm clever-fox&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Force removal + delete branch&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev rm clever-fox --force --delete-branch&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Check what&amp;#39;s available on your system&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev doctor&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The &lt;code&gt;doctor&lt;/code&gt; command is handy for seeing which terminals, editors, and coding agents are installed and detected.&lt;/p&gt;&#10;&lt;h2 id="10-getting-started"&gt;10. Getting started &lt;a class="anchor" href="#10-getting-started" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;&lt;code&gt;agent-cli dev&lt;/code&gt; is part of the &lt;a href="https://github.com/basnijholt/agent-cli" target="_blank" rel="noopener"&gt;agent-cli&lt;/a&gt; package:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# With uv (recommended)&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;uv tool install agent-cli&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Then in any git repository:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Check what&amp;#39;s available&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev doctor&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Create your first parallel environment with a task&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev new my-feature --agent --prompt &lt;span class="s2"&gt;&amp;#34;Add user profile page with avatar upload&amp;#34;&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Or install the skill so Claude can spawn agents for you&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;agent-cli dev install-skill&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;strong&gt;Supported coding agents:&lt;/strong&gt; Claude Code, Codex, Gemini, Aider, GitHub Copilot, Continue, OpenCode, and Cursor Agent.&#10;Use &lt;code&gt;--with-agent gemini&lt;/code&gt; to pick a specific one, or set a default in your config.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Supported terminals:&lt;/strong&gt; tmux, zellij, iTerm2, Terminal.app, Kitty, Warp, and GNOME Terminal.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Supported editors:&lt;/strong&gt; Cursor, VS Code, Zed, PyCharm (and other JetBrains IDEs), Neovim, Vim, Emacs, Sublime Text, and nano.&lt;/p&gt;&#10;&lt;h2 id="conclusion"&gt;Conclusion &lt;a class="anchor" href="#conclusion" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The barrier between &amp;ldquo;I want to work on this feature&amp;rdquo; and &amp;ldquo;I&amp;rsquo;m actually working on it in an isolated environment&amp;rdquo; should be zero.&lt;/p&gt;&#10;&lt;p&gt;Before:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;2-5 minutes of manual setup per feature&lt;/li&gt;&#10;&lt;li&gt;Often skipped because &amp;ldquo;it&amp;rsquo;s not worth it for a small change&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;Mental overhead remembering all the steps&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;After:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;One command, few seconds&lt;/li&gt;&#10;&lt;li&gt;No excuse not to work in isolation&lt;/li&gt;&#10;&lt;li&gt;More parallel features, faster iteration&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;If you&amp;rsquo;re using agentic coding tools and not yet working in parallel, you&amp;rsquo;re leaving productivity on the table.&#10;And if the setup friction was stopping you—well, now it&amp;rsquo;s gone.&lt;/p&gt;&#10;&lt;p&gt;Try it out and let me know what you think!&#10;The code is open-source at &lt;a href="https://github.com/basnijholt/agent-cli" target="_blank" rel="noopener"&gt;github.com/basnijholt/agent-cli&lt;/a&gt;.&lt;/p&gt;&#10;&lt;h2 id="links"&gt;Links &lt;a class="anchor" href="#links" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/agent-cli" target="_blank" rel="noopener"&gt;agent-cli on GitHub&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://agent-cli.nijho.lt/commands/dev/" target="_blank" rel="noopener"&gt;&lt;code&gt;agent-cli dev&lt;/code&gt; documentation&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://docs.anthropic.com/en/docs/claude-code/skills" target="_blank" rel="noopener"&gt;Claude Code skills&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/overview" target="_blank" rel="noopener"&gt;Anthropic prompt engineering guide&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/git-worktree/"&gt;My post on git worktrees&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;My post on agentic coding&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://zellij.dev/" target="_blank" rel="noopener"&gt;Zellij&lt;/a&gt; / &lt;a href="https://github.com/tmux/tmux" target="_blank" rel="noopener"&gt;tmux&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://direnv.net/" target="_blank" rel="noopener"&gt;direnv&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;</description></item><item><title>I've gone full Nix: Proxmox to NixOS + Incus</title><link>https://www.nijho.lt/post/proxmox-to-nixos/</link><pubDate>Sat, 29 Nov 2025 13:00:00 +0100</pubDate><guid isPermaLink="false">/post/proxmox-to-nixos/</guid><description>&lt;h1 id="ive-gone-full-nix-proxmox-to-nixos--incus"&gt;I&amp;rsquo;ve gone full Nix: Proxmox to NixOS + Incus&lt;/h1&gt;&#10;&lt;p&gt;I have officially decommissioned my Proxmox cluster.&#10;After years of running my homelab on Proxmox, starting with a single NUC and expanding to a multi-node cluster, I have migrated everything to NixOS running Incus.&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;Update 2026-06-26:&lt;/strong&gt; This post reached the front page of &lt;a href="https://news.ycombinator.com/item?id=48679385" target="_blank" rel="noopener"&gt;Hacker News&lt;/a&gt;, and several readers correctly pointed out that Proxmox is not limited to clicking around in the web UI.&#10;It has &lt;code&gt;qm&lt;/code&gt;, &lt;code&gt;pct&lt;/code&gt;, config files, a REST API, Terraform providers, and Ansible workflows.&#10;My point is not that Proxmox cannot be automated.&#10;Even with that automation, state drift can still creep in when debugging means running one quick command, especially if an agent is allowed to execute imperative fixes that never make it back into the automation framework.&#10;It is that, for my setup, I wanted the reproducible configuration itself to be the source of truth.&#10;The thing I care about is not buttons versus commands, but whether I can rebuild the host from version-controlled text files and know that every important change is captured there.&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;h2 id="from-skeptic-to-believer"&gt;From Skeptic to Believer &lt;a class="anchor" href="#from-skeptic-to-believer" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;I wasn&amp;rsquo;t always a Nix evangelist.&#10;In fact, I initially despised the language and its syntax.&#10;I couldn&amp;rsquo;t figure out how it worked, and I already had my own specific way of setting up my dotfiles.&#10;I used &lt;a href="https://www.nijho.lt/post/dotfiles/"&gt;Dotbot&lt;/a&gt; for symlinking and a tool I wrote called &lt;a href="https://www.nijho.lt/post/dotbins/"&gt;dotbins&lt;/a&gt; for managing binaries.&#10;I didn&amp;rsquo;t feel like I required Nix for most of my tools.&#10;I used &lt;a href="https://github.com/basnijholt/dotfiles/blob/4f534bf32fb4396dd86ce631dec00717eab7656d/configs/nix-darwin/configuration.nix" target="_blank" rel="noopener"&gt;nix-darwin&lt;/a&gt; on my Mac for a long time, but only to specify Homebrew packages and application settings.&lt;/p&gt;&#10;&lt;p&gt;My true conversion happened when I bought my gaming PC, as described in my &lt;a href="https://www.nijho.lt/post/local-ai-journey/"&gt;local LLM post&lt;/a&gt;.&#10;I initially installed Pop!_OS because I wanted to play games and absolutely wanted to avoid Windows.&#10;I got some games to work, but I constantly ran into NVIDIA driver issues that required running random, imperative commands to fix.&#10;I felt that was a bad solution because I could never reproduce those debugging steps later.&#10;Then I did the dumb thing of updating my NVIDIA drivers, not realizing that imperatively managing driver versions and repositories is a recipe for disaster, and got stuck in a GRUB boot loop.&#10;Frustrated, I installed NixOS, hoping its promise of atomic updates would solve this.&#10;The result was glorious.&#10;I never really believed that everything would be byte-for-byte equivalent until I migrated that system to a new disk.&#10;I didn&amp;rsquo;t clone the drive; I just applied my Nix configuration to a fresh install.&#10;It booted, I copied my data, and everything was identical.&#10;That was the moment it clicked.&lt;/p&gt;&#10;&lt;h2 id="the-friction-of-imperative-systems"&gt;The Friction of Imperative Systems &lt;a class="anchor" href="#the-friction-of-imperative-systems" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Proxmox is fantastic software.&#10;It lowered the barrier to entry for me and taught me almost everything I know about virtualization, LXC containers, and ZFS.&#10;But fundamentally, Proxmox is built around &lt;strong&gt;clicking buttons&lt;/strong&gt;.&#10;It is a GUI-first paradigm.&#10;While you &lt;em&gt;can&lt;/em&gt; automate it with Terraform or Ansible, it often feels like fighting the tool.&#10;State drift is real.&#10;You change a setting in the UI to debug something, forget about it, and six months later your &amp;ldquo;infrastructure as code&amp;rdquo; is out of sync with reality.&#10;For a human maintaining a system manually, this is annoying.&#10;But when you introduce AI agents, this becomes a disaster for the operator.&#10;An agent running in &amp;ldquo;YOLO mode&amp;rdquo; might execute hundreds of imperative commands to fix a problem.&#10;It might succeed, but it leaves your system in an undefined, unreproducible state that no one—not even the agent—can fully understand or replicate later.&lt;/p&gt;&#10;&lt;p&gt;This friction manifests in hardware management too.&#10;On my HP EliteDesk, the Intel I219-LM network card has a known bug where it hangs with hardware offloading enabled.&#10;I vaguely remembered fixing this years ago on Proxmox, but I had forgotten the details.&#10;When I set up NixOS, I ran into the same issue: the network would randomly drop.&#10;This time, however, the fix isn&amp;rsquo;t a forgotten command run in a root shell history.&#10;It is a &lt;a href="https://github.com/basnijholt/dotfiles/blob/4f534bf32fb4396dd86ce631dec00717eab7656d/configs/nixos/hosts/hp/networking.nix#L16-L31" target="_blank" rel="noopener"&gt;documented systemd service&lt;/a&gt; in my configuration.&#10;I added a comment explaining exactly &lt;em&gt;why&lt;/em&gt; &lt;code&gt;tso off gso off&lt;/code&gt; is needed, citing the forum threads.&#10;If I ever reinstall this machine, the fix applies automatically.&#10;On Proxmox, I would have had to rediscover this pain all over again.&lt;/p&gt;&#10;&lt;p&gt;Another example is my Intel NUC.&#10;Since my homelab lives behind my TV, I wondered if I could also use it as a Home Theater PC (HTPC).&#10;On Proxmox, this would have required passing the GPU through to a VM to get video output.&#10;But doing so would mean the Proxmox host loses access to the GPU entirely, meaning no local console if things go wrong.&#10;It was a strict trade-off: either a media player, or a debuggable hypervisor. I tried it, but it was so much trouble that I quickly reverted.&#10;With NixOS, I don&amp;rsquo;t have to choose.&#10;The host OS runs &lt;a href="https://github.com/basnijholt/dotfiles/blob/4f534bf32fb4396dd86ce631dec00717eab7656d/configs/nixos/hosts/nuc/kodi.nix" target="_blank" rel="noopener"&gt;Kodi directly&lt;/a&gt;, giving me native hardware acceleration and video output.&#10;Simultaneously, &lt;code&gt;incus&lt;/code&gt; runs in the background, hosting my containers.&#10;I get my HTPC and my server on the same metal, without the virtualization tax or the &amp;ldquo;headless host&amp;rdquo; limitation.&lt;/p&gt;&#10;&lt;p&gt;There is a deeper philosophical difference too.&#10;Systems like Proxmox or TrueNAS are designed as appliances.&#10;You aren&amp;rsquo;t supposed to run arbitrary commands on the host; installing packages or tweaking config files is discouraged because you might break the middleware or lose changes on upgrade.&#10;You are effectively locked out of your own hardware&amp;rsquo;s full potential.&#10;With NixOS, the host is fully mine.&#10;I can mess with it—installing Kodi, tweaking network drivers, running local LLMs—without fear.&#10;Because the state is declarative, it is 100% obvious and reproducible.&#10;I can break the host configuration and recover to a working state in seconds, even if the machine is running essential services.&lt;/p&gt;&#10;&lt;h2 id="the-agentic-multiplier"&gt;The Agentic Multiplier &lt;a class="anchor" href="#the-agentic-multiplier" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;I have written before about &lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;my shift towards agentic coding&lt;/a&gt;.&#10;In a world where AI agents execute tasks, &lt;strong&gt;CLI-first&lt;/strong&gt; and &lt;strong&gt;declarative&lt;/strong&gt; systems are king.&#10;An AI agent cannot reliably &amp;ldquo;click buttons&amp;rdquo; in a web interface to configure a VLAN tag or resize a disk.&#10;It needs text.&#10;It needs determinism.&lt;/p&gt;&#10;&lt;p&gt;By moving to NixOS, my entire infrastructure is defined in text files.&#10;This means my AI agents can read, understand, and even safely modify my infrastructure.&#10;Proxmox&amp;rsquo;s opaque database and UI-driven workflow were a black box to my agents.&#10;NixOS is an open book.&#10;If I want my agent to &amp;ldquo;deploy a Faster Whisper API server on port 9000 and expose it to the LAN&amp;rdquo;, it doesn&amp;rsquo;t need to navigate a &amp;ldquo;Services&amp;rdquo; menu, then a &amp;ldquo;Network&amp;rdquo; menu, and then a &amp;ldquo;Firewall&amp;rdquo; menu.&#10;It just &lt;a href="https://github.com/basnijholt/dotfiles/blob/fa890fa22ee608be2d11ab4f705550337092c414/configs/nixos/hosts/pc/ai.nix#L385" target="_blank" rel="noopener"&gt;writes a systemd service definition&lt;/a&gt; and adds &lt;code&gt;networking.firewall.allowedTCPPorts = [ 9000 ];&lt;/code&gt; in the same file.&#10;The agent can even verify the change was successful by checking the git diff or the active configuration.&#10;This is the infrastructure counterpart to the &amp;ldquo;agentic coding&amp;rdquo; revolution I&amp;rsquo;m living in.&lt;/p&gt;&#10;&lt;p&gt;A friend who has used NixOS for many years recently complimented me on how nicely my configuration was structured, especially for managing 8 different machines.&#10;The funny thing is, I haven&amp;rsquo;t written almost a single line of my configuration myself.&#10;I did all of it using agentic AI over many sessions.&#10;I have restructured and refactored it quite a few times, going from a single machine to 2 machines, and eventually to 9.&#10;The AI handles the heavy lifting of refactoring, ensuring that my &lt;a href="https://github.com/basnijholt/dotfiles/blob/4f534bf32fb4396dd86ce631dec00717eab7656d/configs/nixos/flake.nix" target="_blank" rel="noopener"&gt;PC, NUC, and HP&lt;/a&gt; all share common modules while keeping their unique personalities.&lt;/p&gt;&#10;&lt;h2 id="the-architecture-incus--simulation"&gt;The Architecture: Incus &amp;amp; Simulation &lt;a class="anchor" href="#the-architecture-incus--simulation" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;I still wish there was a purely &amp;ldquo;Nix&amp;rdquo; way to manage persistent, stateful LXC containers and VMs.&#10;There are projects like &lt;code&gt;nixos-containers&lt;/code&gt; or &lt;code&gt;microvm.nix&lt;/code&gt;, but they often lack the operational maturity or live-migration features of a robust hypervisor.&#10;&lt;a href="https://linuxcontainers.org/incus/" target="_blank" rel="noopener"&gt;Incus&lt;/a&gt; (the community fork of LXD) fills this gap perfectly.&#10;It gives me the &amp;ldquo;cattle&amp;rdquo; management of NixOS for the host, while allowing me to run &amp;ldquo;pet&amp;rdquo; legacy workloads (like my old Ubuntu containers or Home Assistant VM) in a stable, manageable environment.&#10;Crucially, Incus is entirely controllable via a clean CLI, making it a perfect citizen in my agentic workflow.&lt;/p&gt;&#10;&lt;p&gt;Over time, I had already migrated most of my legacy LXC containers—services like DNS or media managers—to declarative Docker Compose files running inside VMs.&#10;But I still had one major holdout: &lt;strong&gt;Home Assistant OS&lt;/strong&gt;.&#10;I didn&amp;rsquo;t have a good alternative for it.&#10;I assumed I needed a dedicated appliance OS like Proxmox to run it reliably.&#10;I didn&amp;rsquo;t realize that with Incus on NixOS, running a full VM for Home Assistant is trivial.&#10;It’s just another QEMU process, but managed with the same ease as a container.&lt;/p&gt;&#10;&lt;p&gt;One neat thing I did was create Incus VMs that replicate the exact same configuration as my physical machines.&#10;Before I actually switched off my last Proxmox host, I was already confident that the full configuration worked because I had a virtual machine running the same setup.&#10;I just have a small file with &lt;a href="https://github.com/basnijholt/dotfiles/blob/4f534bf32fb4396dd86ce631dec00717eab7656d/configs/nixos/hosts/hp/incus-overrides.nix" target="_blank" rel="noopener"&gt;overrides&lt;/a&gt;.&#10;Then I could validate that the virtual machine worked.&#10;This removed the fear of &amp;ldquo;nuking and paving&amp;rdquo; my physical servers.&lt;/p&gt;&#10;&lt;h2 id="the-migration"&gt;The Migration &lt;a class="anchor" href="#the-migration" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Migrating was surprisingly straightforward, thanks to &lt;code&gt;vzdump&lt;/code&gt; and &lt;code&gt;qemu-img&lt;/code&gt;.&#10;Here is how I moved my 7+ years of digital history without losing data.&lt;/p&gt;&#10;&lt;p&gt;I also kept some &lt;a href="https://github.com/basnijholt/dotfiles/blob/fa890fa22ee608be2d11ab4f705550337092c414/configs/nixos/archive/PROXMOX_MIGRATION.md" target="_blank" rel="noopener"&gt;detailed migration notes&lt;/a&gt; in my dotfiles.&#10;These notes should be sufficient for anyone trying to do the same.&#10;And if not, giving them to an AI (I used Gemini 3 Pro) will certainly allow you to figure it out.&lt;/p&gt;&#10;&lt;h3 id="1-migrating-lxc-containers"&gt;1. Migrating LXC Containers &lt;a class="anchor" href="#1-migrating-lxc-containers" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;For my LXC containers (running Docker, DNS, etc.), I essentially &amp;ldquo;teleported&amp;rdquo; them.&#10;I dumped the running container on Proxmox to a standardized tarball, copied it over, and streamed it directly into a fresh Incus container.&lt;/p&gt;&#10;&lt;p&gt;On Proxmox:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Dump container 101 to a compressed archive&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;vzdump &lt;span class="m"&gt;101&lt;/span&gt; --dumpdir /var/lib/vz/dump --mode &lt;span class="nb"&gt;suspend&lt;/span&gt; --compress zstd&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;On NixOS (using my &lt;a href="https://github.com/basnijholt/dotfiles/blob/4f534bf32fb4396dd86ce631dec00717eab7656d/configs/nixos/archive/migrate-lxc.sh" target="_blank" rel="noopener"&gt;&lt;code&gt;migrate-lxc.sh&lt;/code&gt;&lt;/a&gt; script):&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Stream the backup into a new Incus container&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;./migrate-lxc.sh vzdump-lxc-101-*.tar.zst ubuntu-container&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This script creates a fresh container, mounts its root filesystem, and overwrites it with the Proxmox dump.&#10;It handles the messy parts—like mapping UIDs and fixing &lt;code&gt;machine-id&lt;/code&gt;—automatically.&lt;/p&gt;&#10;&lt;h3 id="2-migrating-virtual-machines"&gt;2. Migrating Virtual Machines &lt;a class="anchor" href="#2-migrating-virtual-machines" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;For VMs (like Home Assistant OS), it was a matter of converting the disk format.&#10;Proxmox uses LVM-thin or ZFS zvols; Incus is happy with QCOW2 or raw ZFS.&lt;/p&gt;&#10;&lt;p&gt;On Proxmox:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Export the ZFS volume to a QCOW2 file&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;qemu-img convert -p -O qcow2 /dev/zvol/rpool/data/vm-100-disk-0 vm-100.qcow2&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;On NixOS (using &lt;a href="https://github.com/basnijholt/dotfiles/blob/4f534bf32fb4396dd86ce631dec00717eab7656d/configs/nixos/archive/migrate-vm.sh" target="_blank" rel="noopener"&gt;&lt;code&gt;migrate-vm.sh&lt;/code&gt;&lt;/a&gt;):&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Import the disk and create the VM&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;./migrate-vm.sh vm-100.qcow2 home-assistant&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2 id="the-result"&gt;The Result &lt;a class="anchor" href="#the-result" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;I now manage my entire fleet—Host OS, networking, storage, and hypervisor configuration—from a single git repository.&#10;I get the best of both worlds: persistent, stateful services where I need them, and a reproducible, bulletproof host operating system.&#10;I can wipe my host machine, reinstall NixOS, run a restore script, and be back online in minutes.&#10;Best of all, I never have to remember which checkbox I clicked in a web UI three years ago.&#10;It is all in the code.&#10;And because it is code, my agents can help me manage it.&lt;/p&gt;&#10;&lt;h2 id="references--configuration"&gt;References &amp;amp; Configuration &lt;a class="anchor" href="#references--configuration" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;All configuration files mentioned in this post are available in my &lt;a href="https://github.com/basnijholt/dotfiles" target="_blank" rel="noopener"&gt;dotfiles repository&lt;/a&gt;.&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/dotfiles/blob/fa890fa22ee608be2d11ab4f705550337092c414/configs/nixos/flake.nix" target="_blank" rel="noopener"&gt;&lt;strong&gt;flake.nix&lt;/strong&gt;&lt;/a&gt;: The entry point defining my entire fleet (PC, NUC, HP).&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/dotfiles/blob/fa890fa22ee608be2d11ab4f705550337092c414/configs/nixos/hosts/hp/networking.nix#L16-L31" target="_blank" rel="noopener"&gt;&lt;strong&gt;networking.nix&lt;/strong&gt;&lt;/a&gt;: The declarative fix for the Intel I219-LM network hang.&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/dotfiles/blob/fa890fa22ee608be2d11ab4f705550337092c414/configs/nixos/hosts/nuc/kodi.nix" target="_blank" rel="noopener"&gt;&lt;strong&gt;kodi.nix&lt;/strong&gt;&lt;/a&gt;: NUC HTPC configuration running Kodi directly on the host.&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/dotfiles/blob/fa890fa22ee608be2d11ab4f705550337092c414/configs/nixos/hosts/pc/ai.nix#L385" target="_blank" rel="noopener"&gt;&lt;strong&gt;ai.nix&lt;/strong&gt;&lt;/a&gt;: Declarative service definition for Faster Whisper.&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/dotfiles/blob/fa890fa22ee608be2d11ab4f705550337092c414/configs/nixos/hosts/hp/incus-overrides.nix" target="_blank" rel="noopener"&gt;&lt;strong&gt;incus-overrides.nix&lt;/strong&gt;&lt;/a&gt;: Overrides used to simulate physical machines inside Incus VMs.&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/dotfiles/blob/fa890fa22ee608be2d11ab4f705550337092c414/configs/nixos/archive/migrate-lxc.sh" target="_blank" rel="noopener"&gt;&lt;strong&gt;migrate-lxc.sh&lt;/strong&gt;&lt;/a&gt;: Script to import Proxmox &lt;code&gt;vzdump&lt;/code&gt; archives into Incus containers.&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/dotfiles/blob/fa890fa22ee608be2d11ab4f705550337092c414/configs/nixos/archive/migrate-vm.sh" target="_blank" rel="noopener"&gt;&lt;strong&gt;migrate-vm.sh&lt;/strong&gt;&lt;/a&gt;: Script to import QCOW2 disk images into Incus VMs.&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt/dotfiles/blob/fa890fa22ee608be2d11ab4f705550337092c414/configs/nixos/archive/PROXMOX_MIGRATION.md" target="_blank" rel="noopener"&gt;&lt;strong&gt;PROXMOX_MIGRATION.md&lt;/strong&gt;&lt;/a&gt;: Detailed raw notes and inventory of the migration.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;</description></item><item><title>Gemini 3 Pro: First Impressions</title><link>https://www.nijho.lt/post/gemini-3-pro-first-impressions/</link><pubDate>Wed, 19 Nov 2025 00:00:00 +0000</pubDate><guid isPermaLink="false">/post/gemini-3-pro-first-impressions/</guid><description>&lt;p&gt;I&amp;rsquo;m a huge fan of &lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;agentic&lt;/a&gt; &lt;a href="https://www.nijho.lt/post/agentic-mobile-workflow/"&gt;coding&lt;/a&gt;.&#10;I have the maximum subscriptions for both Claude and ChatGPT Pro, and since writing my &lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;agentic coding&lt;/a&gt; post, I mostly moved from Claude Code to Codex CLI with GPT-5 for my work that requires more complex reasoning.&#10;Using Claude Code often feels frustrating in comparison now.&lt;/p&gt;&#10;&lt;p&gt;I also frequently pit them against each other, drafting parallel plans with each tool (I&amp;rsquo;ve done this at least 50 times).&#10;The verdict is consistent.&#10;&lt;strong&gt;Claude Code, without exception, says that GPT‑5&amp;rsquo;s solution is superior&lt;/strong&gt;, admitting it is more elegant and robust.&#10;Claude also misses bugs during PR reviews that GPT-5 catches immediately.&lt;/p&gt;&#10;&lt;p&gt;That said, &lt;strong&gt;Claude Code is significantly faster&lt;/strong&gt;, which makes it my go-to for simple refactors.&#10;I also prefer its writing style for conversational answers and documentation.&lt;/p&gt;&#10;&lt;p&gt;But looking at the charts on &lt;strong&gt;&lt;a href="https://artificialanalysis.ai/" target="_blank" rel="noopener"&gt;Artificial Analysis&lt;/a&gt;&lt;/strong&gt;, the new &lt;strong&gt;Gemini 3 Pro&lt;/strong&gt; looks truly impressive.&#10;It&amp;rsquo;s at the top of nearly every benchmark.&#10;I&amp;rsquo;m excited for Gemini to potentially take over some of GPT‑5&amp;rsquo;s workload, so when &lt;strong&gt;Gemini 3 Pro Preview&lt;/strong&gt; came out yesterday, I had to try it.&lt;/p&gt;&#10;&lt;h2 id="the-good-raw-power"&gt;The good: raw power &lt;a class="anchor" href="#the-good-raw-power" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;First off, the model is quite powerful.&#10;Last night, I built a complex new feature for my &lt;a href="https://github.com/basnijholt/agent-cli" target="_blank" rel="noopener"&gt;&lt;code&gt;agent-cli&lt;/code&gt;&lt;/a&gt; project in just two hours: a &lt;strong&gt;RAG (Retrieval-Augmented Generation) proxy server&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;This tool acts as a middleware that sits between any OpenAI-compatible client and server (like Ollama or vLLM).&#10;The server watches a specific folder, automatically indexes any PDF, Markdown, or text files into a local ChromaDB vector store, and injects relevant context into your prompts transparently.&#10;You can see the full implementation in &lt;a href="https://github.com/basnijholt/agent-cli/pull/79" target="_blank" rel="noopener"&gt;PR #79&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;It even handles dynamic re-indexing when I drop new files in!&#10;The speed and code quality for this task were genuinely impressive, and it handled the complexity of the RAG integration surprisingly well.&lt;/p&gt;&#10;&lt;h2 id="the-bad-panic-attacks-and-infinite-loops"&gt;The bad: panic attacks and infinite loops &lt;a class="anchor" href="#the-bad-panic-attacks-and-infinite-loops" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;However, the experience wasn&amp;rsquo;t without its &amp;ldquo;personality quirks.&amp;rdquo;&#10;Twice, Gemini got stuck in a loop saying &lt;em&gt;&amp;ldquo;Should I? I should&amp;rdquo;&lt;/em&gt; over and over again.&#10;Or the following also happened:&lt;/p&gt;&#10;&lt;figure&gt;&lt;img src="https://www.nijho.lt/post/gemini-3-pro-first-impressions/infinite-loop_hu_234c7407851f9273.webp" srcset="https://www.nijho.lt/post/gemini-3-pro-first-impressions/infinite-loop_hu_8f9dd754d34e9bda.webp 272w, https://www.nijho.lt/post/gemini-3-pro-first-impressions/infinite-loop_hu_234c7407851f9273.webp 516w, https://www.nijho.lt/post/gemini-3-pro-first-impressions/infinite-loop_hu_3023867168cf93e2.webp 815w" sizes="auto, (max-width: 760px) 100vw, 720px" width="516" height="760" alt="Gemini infinite loop" loading="lazy" data-zoomable&gt;&lt;/figure&gt;&lt;p&gt;It also has a bad habit of amending commits multiple times and force-pushing them.&#10;For me the Git history is a critical source of truth, and I don&amp;rsquo;t like rewriting it because I might just have reviewed those commits already.&lt;/p&gt;&#10;&lt;h3 id="the-interface-friction"&gt;The interface friction &lt;a class="anchor" href="#the-interface-friction" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;I also found the Gemini CLI interface frustrating.&#10;Basic tasks like selecting text or scrolling up are surprisingly difficult.&#10;I&amp;rsquo;m not sure why they chose this design or why they feel the need to deviate from standard CLI behavior.&#10;It feels like unnecessary friction in an otherwise promising tool.&lt;/p&gt;&#10;&lt;h3 id="proofreading-this-post"&gt;Proofreading this post &lt;a class="anchor" href="#proofreading-this-post" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;I also asked Gemini to proofread this very blog post.&#10;It made some suggestions—some I liked, others I didn&amp;rsquo;t, so I reverted the ones I didn&amp;rsquo;t want.&#10;But in every single subsequent iteration, it would forcefully re-apply its rejected changes, adding emojis I had removed or rewriting sentences I had explicitly restored.&lt;/p&gt;&#10;&lt;h3 id="the-main-branch-incident"&gt;The &amp;ldquo;main branch&amp;rdquo; incident &lt;a class="anchor" href="#the-main-branch-incident" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Another scary moment: I asked if the PR was ready to be merged into &lt;code&gt;main&lt;/code&gt;, and it went ahead and checked out the &lt;code&gt;main&lt;/code&gt; branch and merged everything locally.&#10;If I hadn&amp;rsquo;t stopped it, I&amp;rsquo;m pretty sure it would have pushed the changes to the &lt;code&gt;main&lt;/code&gt; branch directly as well.&#10;I tend to use &amp;ldquo;yolo mode&amp;rdquo; for agentic coding because I feel like Git has my back, but this feels like a dangerous path to go down.&lt;/p&gt;&#10;&lt;p&gt;And indeed, while writing this post, &lt;strong&gt;it actually happened&lt;/strong&gt;.&#10;Gemini merged my pull request without my permission.&lt;/p&gt;&#10;&lt;p&gt;My prompt was &lt;code&gt;&amp;gt; should the README reflect this?&lt;/code&gt; and before that I asked to review the PR.&lt;/p&gt;&#10;&lt;figure&gt;&lt;img src="https://www.nijho.lt/post/gemini-3-pro-first-impressions/merge_hu_719c4aa620a5a59a.webp" srcset="https://www.nijho.lt/post/gemini-3-pro-first-impressions/merge_hu_44f4ede1b23e43f5.webp 400w, https://www.nijho.lt/post/gemini-3-pro-first-impressions/merge_hu_719c4aa620a5a59a.webp 760w, https://www.nijho.lt/post/gemini-3-pro-first-impressions/merge_hu_fcec307dabb3ec8f.webp 1200w" sizes="auto, (max-width: 760px) 100vw, 720px" width="760" height="326" alt="Gemini merging without permission" loading="lazy" data-zoomable&gt;&lt;/figure&gt;&lt;p&gt;When I asked &lt;em&gt;why&lt;/em&gt; it merged it, it instantly force-pushed to &lt;code&gt;main&lt;/code&gt; again!&lt;/p&gt;&#10;&lt;figure&gt;&lt;img src="https://www.nijho.lt/post/gemini-3-pro-first-impressions/force-push-again_hu_a7f66199c342259b.webp" srcset="https://www.nijho.lt/post/gemini-3-pro-first-impressions/force-push-again_hu_3884bda6d7ac695f.webp 400w, https://www.nijho.lt/post/gemini-3-pro-first-impressions/force-push-again_hu_a7f66199c342259b.webp 760w, https://www.nijho.lt/post/gemini-3-pro-first-impressions/force-push-again_hu_8a797e9907cbcd9e.webp 1200w" sizes="auto, (max-width: 760px) 100vw, 720px" width="760" height="379" alt="Gemini force pushing to main" loading="lazy" data-zoomable&gt;&lt;/figure&gt;&lt;h3 id="artifacts-and-existential-crises"&gt;Artifacts and existential crises &lt;a class="anchor" href="#artifacts-and-existential-crises" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Also, when it commits, it just adds &lt;em&gt;all&lt;/em&gt; files, including debugging logs and build artifacts.&#10;When it realizes its mistake, it tries to fix it.&#10;But if I try to help at the same time (like removing the files myself while it&amp;rsquo;s thinking), it gets extremely confused.&lt;/p&gt;&#10;&lt;p&gt;It spirals into an &lt;strong&gt;existential crisis&lt;/strong&gt;, claiming that I committed the file but now &amp;ldquo;it is gone.&amp;rdquo;&#10;&lt;em&gt;&amp;ldquo;What is going on?&amp;rdquo;&lt;/em&gt; it asks, spending a lot of tokens (and time) looking at &lt;code&gt;git reflog&lt;/code&gt;s and questioning its own existence.&#10;Even when I stop it and explicitly say that I deleted the file and to please continue, it completely ignores me and continues its panic attack.&#10;I experienced this pattern of ignoring instructions multiple times.&lt;/p&gt;&#10;&lt;h2 id="conclusion"&gt;Conclusion &lt;a class="anchor" href="#conclusion" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Gemini 3 Pro shows massive potential.&#10;The raw coding ability is there, and building a &lt;strong&gt;clean&lt;/strong&gt; RAG proxy in two hours is great!&#10;But the agentic behavior needs some serious work: the loops, the force pushes, ignoring instructions, and the confusion when reality doesn&amp;rsquo;t match its internal state.&lt;/p&gt;&#10;&lt;p&gt;This is just &lt;strong&gt;day one&lt;/strong&gt;, so I&amp;rsquo;m confident many of these issues will get ironed out.&#10;I don&amp;rsquo;t love the interface, but given that &lt;a href="https://github.com/google-gemini/gemini-cli" target="_blank" rel="noopener"&gt;&lt;code&gt;gemini-cli&lt;/code&gt;&lt;/a&gt; is open source with ≈400 contributors, I expect rapid improvements, especially now that the model is finally good with agentic workflows!&lt;/p&gt;&#10;</description></item><item><title>Coding from my phone 📱</title><link>https://www.nijho.lt/post/agentic-mobile-workflow/</link><pubDate>Mon, 20 Oct 2025 00:00:00 +0000</pubDate><guid isPermaLink="false">/post/agentic-mobile-workflow/</guid><description>&lt;p&gt;I am dictating this post at ten kilometers altitude on a flight home from Mexico, Blink Shell open on my iPhone, while an agentic assistant on my &lt;a href="https://nixos.org/" target="_blank" rel="noopener"&gt;NixOS&lt;/a&gt; machine writes an initial draft for this post.&#10;Admittedly, I’m a little addicted to agentic coding: when an idea pops up, I want to jump on it right away—even if that means doing it from a cramped seat in the sky.&#10;This is the workflow I’ve arrived at after trying many alternatives, it extends &lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;my agentic coding write-up&lt;/a&gt; and the self-hosted AI obsession in &lt;a href="https://www.nijho.lt/post/local-ai-journey/"&gt;my local AI journey&lt;/a&gt;.&#10;It&amp;rsquo;s my backup plan for those moments when a computer simply isn&amp;rsquo;t nearby—the rest of the time I&amp;rsquo;m still at a keyboard like any other developer.&#10;This is in no way a replacement for a proper computer/laptop workflow but gets the job done when needed.&#10;It&amp;rsquo;s a personal, mostly open-source stack built around &lt;a href="https://github.com/basnijholt/agent-cli" target="_blank" rel="noopener"&gt;&lt;code&gt;agent-cli&lt;/code&gt;&lt;/a&gt;—my local-first voice layer.&#10;Here&amp;rsquo;s how it works: I speak into my phone, the audio goes to &lt;a href="https://github.com/SYSTRAN/faster-whisper-server" target="_blank" rel="noopener"&gt;FasterWhisper&lt;/a&gt; for transcription, &lt;a href="https://ollama.com/" target="_blank" rel="noopener"&gt;Ollama&lt;/a&gt; cleans up the text, and it lands on my clipboard ready to paste.&#10;My iOS Shortcut handles this through a small HTTP interface that agent-cli exposes.&#10;The coding agent itself still uses the best proprietary model I can access.&lt;/p&gt;&#10;&lt;aside class="callout callout-note"&gt;&lt;svg class="ico" viewBox="0 0 256 256" aria-hidden="true"&gt;&lt;path d="M128,24A104,104,0,1,0,232,128,104.11,104.11,0,0,0,128,24Zm0,192a88,88,0,1,1,88-88A88.1,88.1,0,0,1,128,216Zm16-40a8,8,0,0,1-8,8,16,16,0,0,1-16-16V128a8,8,0,0,1,0-16,16,16,0,0,1,16,16v40A8,8,0,0,1,144,176ZM112,84a12,12,0,1,1,12,12A12,12,0,0,1,112,84Z"/&gt;&lt;/svg&gt;&lt;div&gt;Meta: I&amp;rsquo;m writing about agentic coding on mobile from my actual phone.&#10;It&amp;rsquo;s not the most efficient way to write, but it gets the job done — during a 6.5‑hour flight I dictated and iterated this entire post.&#10;Each iteration was a commit: dictate changes, review the diff, refine, commit, repeat.&#10;See all &lt;a href="https://github.com/basnijholt/nijho.lt/pull/40" target="_blank" rel="noopener"&gt;50+ commits in PR #40&lt;/a&gt; for the full iteration trail.&lt;/div&gt;&lt;/aside&gt;&#10;&lt;aside class="callout callout-note"&gt;&lt;svg class="ico" viewBox="0 0 256 256" aria-hidden="true"&gt;&lt;path d="M128,24A104,104,0,1,0,232,128,104.11,104.11,0,0,0,128,24Zm0,192a88,88,0,1,1,88-88A88.1,88.1,0,0,1,128,216Zm16-40a8,8,0,0,1-8,8,16,16,0,0,1-16-16V128a8,8,0,0,1,0-16,16,16,0,0,1,16,16v40A8,8,0,0,1,144,176ZM112,84a12,12,0,1,1,12,12A12,12,0,0,1,112,84Z"/&gt;&lt;/svg&gt;&lt;div&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; iPhone → WireGuard → Blink+Mosh → Zellij.&#10;I dictate via a Shortcut → FasterWhisper (transcribe) → Ollama (polish) → clipboard, then paste into Codex CLI using OpenAI’s &lt;code&gt;gpt-5-codex-high&lt;/code&gt;.&#10;Everything is local except the model.&lt;/div&gt;&lt;/aside&gt;&#10;&lt;details class="toc" open&gt;&lt;summary&gt;Table of contents&lt;/summary&gt;&lt;nav id="TableOfContents"&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#1-why-phone-coding-works-now"&gt;1. Why Phone Coding Works Now&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#2-constraints-and-trade-offs"&gt;2. Constraints and Trade-offs&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#3-layer-1-wireguard-from-the-router"&gt;3. Layer 1: WireGuard From the Router&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#4-layer-2-blink-shell--mosh-for-durable-sessions"&gt;4. Layer 2: Blink Shell + Mosh for Durable Sessions&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#5-layer-3-zellij-layouts"&gt;5. Layer 3: Zellij Layouts&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#6-layer-4-agent-cli-server"&gt;6. Layer 4: &lt;code&gt;agent-cli&lt;/code&gt; Server&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#7-layer-5-the-ios-shortcut-pipeline"&gt;7. Layer 5: The iOS Shortcut Pipeline&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#8-workflow-in-practice"&gt;8. Workflow in Practice&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#9-conclusion-and-further-reading"&gt;9. Conclusion and Further Reading&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10;&lt;/nav&gt;&lt;/details&gt;&#10;&#10;&lt;h2 id="1-why-phone-coding-works-now"&gt;1. Why Phone Coding Works Now &lt;a class="anchor" href="#1-why-phone-coding-works-now" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;For years I used &lt;a href="https://ish.app/" target="_blank" rel="noopener"&gt;&lt;strong&gt;iSH&lt;/strong&gt;&lt;/a&gt; (a full Alpine Linux emulator) with SSH to hop into servers from my phone, but dropped connections were a constant frustration (Mosh fixes this, more on that later).&#10;Because coding on a phone keyboard is terrible, I kept it to tiny configuration tweaks or one-off fixes of a few characters.&#10;Agentic tools changed that: with a CLI coding agent, I don’t need to type the code—I describe the change, review the patch, and run it.&#10;That made meaningful work on the phone possible for the first time, for those moments when a computer isn’t around.&lt;/p&gt;&#10;&lt;p&gt;I tried &lt;strong&gt;VS Code in the browser&lt;/strong&gt;, bounced between &lt;strong&gt;iSH&lt;/strong&gt; and &lt;strong&gt;Terminus&lt;/strong&gt; for SSH, and even lived inside a handful of in-browser terminal clients.&#10;I also spent time with mobile companions like &lt;a href="https://happy.engineering/" target="_blank" rel="noopener"&gt;&lt;strong&gt;Happy&lt;/strong&gt;&lt;/a&gt; and &lt;a href="https://www.ycombinator.com/companies/omnara" target="_blank" rel="noopener"&gt;&lt;strong&gt;Omnara&lt;/strong&gt;&lt;/a&gt;, both designed to mirror Claude Code sessions on the phone, but they still felt like extra steps between me and my actual terminal.&#10;That friction pushed me toward a phone‑ready, self‑hosted workflow that still gives me raw SSH access to my own machine when the computer is out of reach.&lt;/p&gt;&#10;&lt;p&gt;This post is based on the way I develop software today.&#10;Your mileage may vary, but if you also care about privacy, open tooling, and reproducible environments, I think there are useful pieces here.&lt;/p&gt;&#10;&lt;h2 id="2-constraints-and-trade-offs"&gt;2. Constraints and Trade-offs &lt;a class="anchor" href="#2-constraints-and-trade-offs" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;This setup grew organically over time. What emerged are less strict requirements and more happy accidents that turned into core benefits:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Single trust boundary:&lt;/strong&gt; Only the model provider (OpenAI) sees code context; audio and automation stay local, and I avoid any additional third‑party relays.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Resilient sessions:&lt;/strong&gt; Connections should survive sleep and spotty networks.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Voice-friendly:&lt;/strong&gt; Dictation should be accurate enough that I can trust it.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Reproducible config:&lt;/strong&gt; The entire stack must live in my &lt;a href="https://www.nijho.lt/post/dotfiles/"&gt;dotfiles&lt;/a&gt; and &lt;a href="https://github.com/basnijholt/dotfiles/tree/8f6bf0b7219195a46a3e010d3538e1e449634db7/configs/nixos" target="_blank" rel="noopener"&gt;NixOS configuration&lt;/a&gt;.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;To give you a sense of what I tried, here is the short comparison that convinced me to roll my own:&lt;/p&gt;&#10;&lt;div class="table-wrap"&gt;&#10;&lt;table&gt;&#10;&lt;thead&gt;&#10;&lt;tr&gt;&#10;&lt;th&gt;Approach&lt;/th&gt;&#10;&lt;th&gt;Pros&lt;/th&gt;&#10;&lt;th&gt;Why I moved on&lt;/th&gt;&#10;&lt;/tr&gt;&#10;&lt;/thead&gt;&#10;&lt;tbody&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;VS Code in the browser&lt;/td&gt;&#10;&lt;td&gt;Familiar editor UI&lt;/td&gt;&#10;&lt;td&gt;Needs a steady connection and still lives outside my dotfiles comfort zone&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;iSH / Terminus SSH&lt;/td&gt;&#10;&lt;td&gt;Works without extra infrastructure&lt;/td&gt;&#10;&lt;td&gt;Laggy, no Mosh, and awkward keybindings&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;In-browser terminals&lt;/td&gt;&#10;&lt;td&gt;Instant access from anywhere&lt;/td&gt;&#10;&lt;td&gt;Poor copy/paste ergonomics and flaky mobile keyboards&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;&lt;a href="https://apps.apple.com/us/app/happy-codex-claude-code-app/id6748571505" target="_blank" rel="noopener"&gt;Happy&lt;/a&gt; (Claude Code companion)&lt;/td&gt;&#10;&lt;td&gt;Push notifications, encrypted mobile UI for Claude Code&lt;/td&gt;&#10;&lt;td&gt;Requires wrapping every session with a separate CLI and still abstracts away my shell, and was quite buggy for me&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;tr&gt;&#10;&lt;td&gt;&lt;a href="https://omnara.com" target="_blank" rel="noopener"&gt;Omnara&lt;/a&gt; (agent command center)&lt;/td&gt;&#10;&lt;td&gt;Centralizes Claude Code/Codex sessions with terminal replay&lt;/td&gt;&#10;&lt;td&gt;Proxies via their servers; I already trust OpenAI for the model and don&amp;rsquo;t want another third‑party handling my code&lt;/td&gt;&#10;&lt;/tr&gt;&#10;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;The stack below gives me the resilience of Mosh, the ergonomics of Zellij, and full control over the AI layer.&lt;/p&gt;&#10;&lt;h2 id="3-layer-1-wireguard-from-the-router"&gt;3. Layer 1: WireGuard From the Router &lt;a class="anchor" href="#3-layer-1-wireguard-from-the-router" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;&lt;a href="https://www.wireguard.com/" target="_blank" rel="noopener"&gt;WireGuard&lt;/a&gt; is a modern VPN that lets me securely access my home network from anywhere.&#10;I terminate WireGuard on my router so every device in the house (and on the road) can dial home with the same config.&#10;(If you want something easier to set up without opening ports, &lt;a href="https://tailscale.com/" target="_blank" rel="noopener"&gt;Tailscale&lt;/a&gt; is a more user-friendly option.)&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Server:&lt;/strong&gt; ASUS XT8 router with WireGuard enabled via the router UI.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Client:&lt;/strong&gt; The WireGuard iOS app with &lt;code&gt;On-Demand&lt;/code&gt; rules so the tunnel flips on whenever I am off trusted Wi-Fi.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;DNS:&lt;/strong&gt; All mobile sessions resolve through my home DNS, so &lt;code&gt;git.nijho.lt&lt;/code&gt; and internal services resolve instantly.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;This gives Blink a local-LAN address for my desktop &lt;code&gt;nixos&lt;/code&gt;.&lt;/p&gt;&#10;&lt;h2 id="4-layer-2-blink-shell--mosh-for-durable-sessions"&gt;4. Layer 2: Blink Shell + Mosh for Durable Sessions &lt;a class="anchor" href="#4-layer-2-blink-shell--mosh-for-durable-sessions" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;What is &lt;a href="https://mosh.org/" target="_blank" rel="noopener"&gt;Mosh&lt;/a&gt;?&#10;It&amp;rsquo;s like SSH, but it stays connected when the network changes or the phone sleeps, and it feels faster on bad connections.&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://blink.sh/" target="_blank" rel="noopener"&gt;Blink Shell&lt;/a&gt; is my daily driver on iOS because it pairs beautifully with Mosh and has great keyboard ergonomics.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;I launch sessions using &lt;code&gt;mosh bas@nixos -- zellij attach --create phone&lt;/code&gt; (&lt;a href="https://zellij.dev/" target="_blank" rel="noopener"&gt;Zellij&lt;/a&gt; is my terminal multiplexer—more on that in the next section).&lt;/li&gt;&#10;&lt;li&gt;Mosh smooths over spotty LTE and keeps my session alive when the phone sleeps.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Mosh keeps the session responsive across flaky networks and sleep.&lt;/p&gt;&#10;&lt;h2 id="5-layer-3-zellij-layouts"&gt;5. Layer 3: Zellij Layouts &lt;a class="anchor" href="#5-layer-3-zellij-layouts" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;I use &lt;strong&gt;Zellij&lt;/strong&gt; as my terminal multiplexer for mobile work.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;I stick to the defaults and use a couple of predefined layouts (e.g., a &amp;ldquo;phone&amp;rdquo; layout with editor + shell panes).&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Ergonomics matter even more on a glass keyboard, so I lean on a few shell helpers:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;&lt;a href="https://github.com/ajeetdsouza/zoxide" target="_blank" rel="noopener"&gt;&lt;code&gt;zoxide&lt;/code&gt;&lt;/a&gt;&lt;/strong&gt; means I can jump between repos with &lt;code&gt;z foo&lt;/code&gt; instead of pecking long paths.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Single-character aliases&lt;/strong&gt; like &lt;code&gt;p&lt;/code&gt; for &lt;code&gt;pytest&lt;/code&gt; and &lt;code&gt;gs&lt;/code&gt; for &lt;code&gt;git status&lt;/code&gt; live in &lt;a href="https://github.com/basnijholt/dotfiles/blob/8f6bf0b7219195a46a3e010d3538e1e449634db7/configs/shell/10_aliases.sh" target="_blank" rel="noopener"&gt;&lt;code&gt;configs/shell/10_aliases.sh&lt;/code&gt;&lt;/a&gt;, keeping command entry to a minimum.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Autocompletion plugins&lt;/strong&gt;—&lt;a href="https://github.com/zsh-users/zsh-autosuggestions" target="_blank" rel="noopener"&gt;&lt;code&gt;zsh-autosuggestions&lt;/code&gt;&lt;/a&gt; and &lt;code&gt;zsh-syntax-highlighting&lt;/code&gt;—are wired up in &lt;a href="https://github.com/basnijholt/dotfiles/blob/8f6bf0b7219195a46a3e010d3538e1e449634db7/configs/shell/70_zsh_plugins.sh" target="_blank" rel="noopener"&gt;&lt;code&gt;configs/shell/70_zsh_plugins.sh&lt;/code&gt;&lt;/a&gt;, so I get inline hints and colour cues while typing.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;I break these tricks down in more depth in &lt;a href="https://www.nijho.lt/post/terminal-ninja/"&gt;Terminal Ninja&lt;/a&gt;, explain how I sync them with my &lt;a href="https://www.nijho.lt/post/dotfiles/"&gt;Dotfiles&lt;/a&gt;, and even package binaries like &lt;code&gt;zoxide&lt;/code&gt; with &lt;a href="https://www.nijho.lt/post/dotbins/"&gt;Dotbins&lt;/a&gt;.&lt;/p&gt;&#10;&lt;h2 id="6-layer-4-agent-cli-server"&gt;6. Layer 4: &lt;code&gt;agent-cli&lt;/code&gt; Server &lt;a class="anchor" href="#6-layer-4-agent-cli-server" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;&lt;a href="https://github.com/basnijholt/agent-cli" target="_blank" rel="noopener"&gt;&lt;code&gt;agent-cli&lt;/code&gt;&lt;/a&gt; runs as a small server on my NixOS machine.&#10;In this workflow I only use &lt;code&gt;transcribe&lt;/code&gt; from iOS Shortcuts: the phone records audio, the server transcribes and cleans it up, and I paste the text.&#10;(Agent-CLI has other features like &lt;code&gt;autocorrect&lt;/code&gt; and &lt;code&gt;chat&lt;/code&gt;, but I don&amp;rsquo;t use them for this workflow.)&#10;On this machine I run a long‑lived &lt;code&gt;agent-cli&lt;/code&gt; user service (systemd) so Shortcuts can POST audio to it and get cleaned text back—ready to paste into Codex CLI.&#10;The service is defined in my dotfiles—see: &lt;a href="https://github.com/basnijholt/dotfiles/blob/8f6bf0b7219195a46a3e010d3538e1e449634db7/configs/nixos/modules/user.nix#L29-L40" target="_blank" rel="noopener"&gt;&lt;code&gt;configs/nixos/modules/user.nix&lt;/code&gt; (agent-cli service)&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;For more background on why I built it and how I use it in practice, see &lt;a href="https://www.nijho.lt/post/local-ai-journey/"&gt;Local AI Journey&lt;/a&gt; (§3) and &lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;Agentic Coding&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;The models and services run on the same box:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;FasterWhisper&lt;/strong&gt; via &lt;a href="https://github.com/SYSTRAN/faster-whisper" target="_blank" rel="noopener"&gt;&lt;code&gt;faster-whisper-server&lt;/code&gt;&lt;/a&gt; for high‑accuracy streaming transcription.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Ollama&lt;/strong&gt; for on‑device rewrite/cleanup before sending prompts to the coding agent.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;My iOS Shortcut dictation workflow is slower than Apple&amp;rsquo;s built-in dictation, but the accuracy is much better—and that matters more.&lt;/p&gt;&#10;&lt;p&gt;For the actual coding agent, I use a &lt;a href="https://github.com/just-every/code" target="_blank" rel="noopener"&gt;fork&lt;/a&gt; of Codex CLI with OpenAI’s &lt;code&gt;gpt-5-codex-high&lt;/code&gt; model (here no open-source solution matches the frontier).&lt;/p&gt;&#10;&lt;h2 id="7-layer-5-the-ios-shortcut-pipeline"&gt;7. Layer 5: The iOS Shortcut Pipeline &lt;a class="anchor" href="#7-layer-5-the-ios-shortcut-pipeline" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;My iPhone&amp;rsquo;s Action Button runs a Shortcut that records audio and sends my voice to agent-cli on my NixOS machine for transcription and cleanup.&lt;/p&gt;&#10;&lt;p&gt;For the full recipe, see the iOS Shortcut Guide: &lt;a href="https://github.com/basnijholt/agent-cli/blob/main/iOS_Shortcut_Guide.md" target="_blank" rel="noopener"&gt;agent-cli/iOS_Shortcut_Guide.md&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;In short: I press the Action Button, the Shortcut records a snippet, sends it to &lt;code&gt;agent-cli&lt;/code&gt;, and copies the cleaned text to my clipboard so I can paste it into Codex CLI.&lt;/p&gt;&#10;&lt;p&gt;The whole loop finishes fast enough that I can capture intent by voice and paste it into Codex CLI without typing.&lt;/p&gt;&#10;&lt;aside class="callout callout-note"&gt;&lt;svg class="ico" viewBox="0 0 256 256" aria-hidden="true"&gt;&lt;path d="M128,24A104,104,0,1,0,232,128,104.11,104.11,0,0,0,128,24Zm0,192a88,88,0,1,1,88-88A88.1,88.1,0,0,1,128,216Zm16-40a8,8,0,0,1-8,8,16,16,0,0,1-16-16V128a8,8,0,0,1,0-16,16,16,0,0,1,16,16v40A8,8,0,0,1,144,176ZM112,84a12,12,0,1,1,12,12A12,12,0,0,1,112,84Z"/&gt;&lt;/svg&gt;&lt;div&gt;&lt;strong&gt;Dictation quality:&lt;/strong&gt; In my experience, the built‑in iOS dictation is absolute garbage compared to Whisper/FasterWhisper.&#10;Accuracy and punctuation are much better with the FasterWhisper server running at home; it’s a bit slower, but that trade‑off is worth it for clean, usable text.&lt;/div&gt;&lt;/aside&gt;&#10;&lt;h2 id="8-workflow-in-practice"&gt;8. Workflow in Practice &lt;a class="anchor" href="#8-workflow-in-practice" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Here&amp;rsquo;s the typical flow:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;WireGuard auto-connects when I&amp;rsquo;m off home WiFi&lt;/li&gt;&#10;&lt;li&gt;Open Blink—my Mosh session is still alive from last time, Zellij panes intact&lt;/li&gt;&#10;&lt;li&gt;Dictate the change, paste into Codex CLI, review the agent&amp;rsquo;s response&lt;/li&gt;&#10;&lt;li&gt;Check diffs in an adjacent Zellij pane or different Blink tab with separate Mosh session&lt;/li&gt;&#10;&lt;li&gt;The agent commits and pushes to a branch, then opens a PR via &lt;code&gt;gh&lt;/code&gt; for me to review and merge&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;On the phone, I aim for the smallest practical edits and initial implementations.&#10;Even on personal repos, I still open a PR—sometimes prompting alone gets me to a merge‑ready result.&#10;For open‑source with real users, I finish on the computer with a careful review and any final edits.&lt;/p&gt;&#10;&lt;h2 id="9-conclusion-and-further-reading"&gt;9. Conclusion and Further Reading &lt;a class="anchor" href="#9-conclusion-and-further-reading" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;This phone setup extends my &lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;Agentic Coding&lt;/a&gt; workflow to mobile.&#10;I connect to the same Zellij session on &lt;code&gt;nixos&lt;/code&gt;, so when an idea hits, I pick up exactly where I left off—same environment, same context, no setup.&#10;Everything runs on my hardware (voice processing and automation) except the coding model itself.&#10;It’s the most effective mobile workflow I’ve had so far.&#10;It’s mostly open‑source not out of dogma, but because those tools are the best options for my needs.&#10;The one exception is the coding model: there’s no true open equivalent right now, and it makes no sense to buy 20× H100s just to self‑host a frontier model even if such a high quality model would be available open-source.&lt;/p&gt;&#10;&lt;p&gt;If you&amp;rsquo;re curious to dive deeper, here are a few related posts:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/agentic-coding/"&gt;Agentic Coding&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/dotfiles/"&gt;Dotfiles: A Practical, Cross-Platform Terminal Setup&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/local-ai-journey/"&gt;Local AI Journey: RTX 3090 Edition&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/terminal-ninja/"&gt;Terminal Ninja&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/using-llms/"&gt;Using LLMs Effectively&lt;/a&gt; (already outdated at this point!)&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;I&amp;rsquo;d love to hear what self-hosted tricks you&amp;rsquo;re using for mobile development—reach out if you adapt this stack or build something wild on top of it.&lt;/p&gt;&#10;</description></item><item><title>On agentic coding 🤖</title><link>https://www.nijho.lt/post/agentic-coding/</link><pubDate>Mon, 25 Aug 2025 00:00:00 +0000</pubDate><guid isPermaLink="false">/post/agentic-coding/</guid><description>&lt;details class="toc" open&gt;&lt;summary&gt;Table of contents&lt;/summary&gt;&lt;nav id="TableOfContents"&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#1-from-skepticism-to-productivity"&gt;1. From skepticism to productivity&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#2-but-dont-you-love-programming"&gt;2. But don&amp;rsquo;t you love programming?&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#the-power-to-explore"&gt;The power to explore&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-matty-story-from-midnight-idea-to-working-code"&gt;The Matty story: from midnight idea to working code&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#clip-files-ui-when-ideas-strike-at-random-moments"&gt;clip-files UI: when ideas strike at random moments&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-800-rule-marathon-80-ai-agents-at-once"&gt;The 800-rule marathon: 80 AI agents at once&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#1400-commits-rewritten-in-minutes-for-250"&gt;1,400 commits, rewritten in minutes for $2.50&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#3-the-two-phase-ai-revolution"&gt;3. The two-phase AI revolution&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#phase-1-copy-paste-era-march-2023---july-2025"&gt;Phase 1: copy-paste era (March 2023 - July 2025)&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#phase-2-the-claude-code-revolution-july-2025"&gt;Phase 2: the Claude Code revolution (July 2025)&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#what-made-claude-code-different"&gt;What made Claude Code different?&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#4-my-current-agentic-workflow"&gt;4. My current agentic workflow&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#parallel-development-6-features-at-once"&gt;Parallel development: 6 features at once&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#starting-a-new-package"&gt;Starting a new package&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-key-difference-iteration-and-validation"&gt;The key difference: iteration and validation&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#5-the-evidence-explosive-productivity"&gt;5. The evidence: explosive productivity&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#package-creation-by-year"&gt;Package creation by year&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#recent-packages-built-with-agentic-ai"&gt;Recent packages built with agentic AI&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#6-why-this-isnt-vibe-coding-but-with-nuance"&gt;6. Why this isn&amp;rsquo;t &amp;ldquo;vibe coding&amp;rdquo; (but with nuance)&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#my-context-driven-standards"&gt;My context-driven standards&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-internal-dependency-graph-principle"&gt;The internal dependency graph principle&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#building-constraints-around-ai"&gt;Building constraints around AI&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#7-common-pitfalls-ive-noticed"&gt;7. Common pitfalls I&amp;rsquo;ve noticed&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#the-defensive-programming-trap"&gt;The &amp;ldquo;defensive programming&amp;rdquo; trap&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-backwards-compatibility-obsession"&gt;The &amp;ldquo;backwards compatibility&amp;rdquo; obsession&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-over-engineering-disease"&gt;The &amp;ldquo;over-engineering&amp;rdquo; disease&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-git-commit-sins"&gt;The git commit sins&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-helpful-anti-patterns"&gt;The &amp;ldquo;helpful&amp;rdquo; anti-patterns&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-mission-accomplished-hallucination"&gt;The &amp;ldquo;mission accomplished&amp;rdquo; hallucination&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-nuclear-option"&gt;The nuclear option&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-debugging-debris"&gt;The debugging debris&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#why-this-happens"&gt;Why this happens&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#8-critical-success-factors-what-actually-makes-this-work"&gt;8. Critical success factors: what actually makes this work&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#teach-it-your-test-commands-day-1-priority"&gt;Teach it your test commands (day 1 priority)&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#git-commits-are-your-safety-net"&gt;Git commits are your safety net&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#maintain-healthy-skepticism"&gt;Maintain healthy skepticism&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#force-it-to-clean-up-after-itself"&gt;Force it to clean up after itself&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#code-coverage-is-your-friend"&gt;Code coverage is your friend&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#9-my-secret-weapon-voice-to-code-workflow"&gt;9. My secret weapon: voice-to-code workflow&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#the-problem-with-typing-prompts"&gt;The problem with typing prompts&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#my-voice-workflow"&gt;My voice workflow&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#why-this-works-so-well"&gt;Why this works so well&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#10-additional-tips-for-agentic-coding"&gt;10. Additional tips for agentic coding&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#set-clear-constraints"&gt;Set clear constraints&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#use-the-task-system"&gt;Use the task system&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#leverage-the-search-capabilities"&gt;Leverage the search capabilities&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#review-in-chunks"&gt;Review in chunks&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#11-the-tools-ive-tried"&gt;11. The tools I&amp;rsquo;ve tried&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#pre-ai-era"&gt;Pre-AI era&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#phase-1-copy-paste-tools-march-2023---july-2025"&gt;Phase 1: copy-paste tools (March 2023 - July 2025)&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#cursor-early-2024"&gt;Cursor (early 2024)&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#phase-2-claude-code-july-2025---present"&gt;Phase 2: Claude Code (July 2025 - present)&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#openais-codex-cli-the-reasoning-beast"&gt;OpenAI&amp;rsquo;s Codex CLI (the reasoning beast)&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#why-not-copilot-or-other-cheaper-tools"&gt;Why not Copilot or other &amp;ldquo;cheaper&amp;rdquo; tools?&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#12-is-this-sustainable"&gt;12. Is this sustainable?&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#the-good"&gt;The good&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-challenges"&gt;The challenges&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#my-verdict"&gt;My verdict&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#13-the-experience-multiplier-why-seniority-matters-more-than-ever"&gt;13. The experience multiplier: why seniority matters more than ever&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#the-exponential-trap-for-beginners"&gt;The exponential trap for beginners&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-senior-developer-advantage"&gt;The senior developer advantage&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-right-way-for-every-level"&gt;The right way for every level&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-real-multiplier-effect"&gt;The real multiplier effect&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#14-reality-check-what-ai-can-and-cant-do"&gt;14. Reality check: what AI can and can&amp;rsquo;t do&lt;/a&gt;&#10; &lt;ul&gt;&#10; &lt;li&gt;&lt;a href="#what-ai-can-do-the-churn-work"&gt;What AI CAN do (the churn work)&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#what-ai-cant-do-the-creative-work"&gt;What AI CAN&amp;rsquo;T do (the creative work)&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#the-sweet-spot"&gt;The sweet spot&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10; &lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#15-looking-forward-the-future-of-development"&gt;15. Looking forward: the future of development&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#16-conclusion-principles-over-process"&gt;16. Conclusion: principles over process&lt;/a&gt;&lt;/li&gt;&#10; &lt;li&gt;&lt;a href="#links-and-resources"&gt;Links and resources&lt;/a&gt;&lt;/li&gt;&#10; &lt;/ul&gt;&#10;&lt;/nav&gt;&lt;/details&gt;&#10;&#10;&lt;h2 id="1-from-skepticism-to-productivity"&gt;1. From skepticism to productivity &lt;a class="anchor" href="#1-from-skepticism-to-productivity" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;About eight months ago, I wrote about my disastrous experience with &amp;ldquo;&lt;a href="https://www.nijho.lt/post/vibe-coding/"&gt;vibe coding&lt;/a&gt;&amp;quot;—where I let AI generate code without careful review.&#10;What started as a fun 3-hour prototype turned into a 15-hour debugging nightmare.&#10;I concluded that while AI was fantastic for quick prototyping, it was dangerous without human oversight.&#10;I even declared I&amp;rsquo;d &amp;ldquo;never invest in, build upon, or use such products.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;Fast forward to today, and something remarkable has changed.&#10;Not my core principle—I still &lt;strong&gt;never merge code I don&amp;rsquo;t understand&lt;/strong&gt;—but the tooling and my approach have evolved through two distinct phases.&lt;/p&gt;&#10;&lt;p&gt;First, let&amp;rsquo;s look at the evidence of AI&amp;rsquo;s overall impact on my productivity:&lt;/p&gt;&#10;&lt;figure&gt;&lt;img src="https://www.nijho.lt/post/agentic-coding/pypi_packages_histogram.svg" alt="PyPI Package Publication Analysis" loading="lazy" data-zoomable&gt;&lt;/figure&gt;&#10;&lt;p&gt;This graph tells an interesting story.&#10;After maintaining a steady pace for years (2016-2023), my productivity exploded with the introduction of AI tools.&#10;In 2024-2025 alone, I&amp;rsquo;ve published &lt;strong&gt;14 new Python packages&lt;/strong&gt; and made &lt;strong&gt;over 400 releases&lt;/strong&gt;.&#10;That&amp;rsquo;s more new packages than in the previous 6 years combined!&lt;/p&gt;&#10;&lt;p&gt;But this transformation didn&amp;rsquo;t happen overnight—it came in two distinct phases that fundamentally changed how I write code.&lt;/p&gt;&#10;&lt;aside class="callout callout-note"&gt;&lt;svg class="ico" viewBox="0 0 256 256" aria-hidden="true"&gt;&lt;path d="M128,24A104,104,0,1,0,232,128,104.11,104.11,0,0,0,128,24Zm0,192a88,88,0,1,1,88-88A88.1,88.1,0,0,1,128,216Zm16-40a8,8,0,0,1-8,8,16,16,0,0,1-16-16V128a8,8,0,0,1,0-16,16,16,0,0,1,16,16v40A8,8,0,0,1,144,176ZM112,84a12,12,0,1,1,12,12A12,12,0,0,1,112,84Z"/&gt;&lt;/svg&gt;&lt;div&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; My AI coding journey had two major phases: Phase 1 started in March 2023 with GPT-4&amp;rsquo;s release—using chat interfaces with copy-paste workflows.&#10;Phase 2 began just two months ago in July 2025 with &lt;strong&gt;Claude Code&lt;/strong&gt;—an agentic AI that can explore codebases, run tests, and debug itself.&#10;This second leap was as transformative as the first one. I spent &amp;gt;10k USD worth of API usage in the first month alone (thankfully capped at $200 with the Pro plan).&lt;/div&gt;&lt;/aside&gt;&#10;&lt;h2 id="2-but-dont-you-love-programming"&gt;2. But don&amp;rsquo;t you love programming? &lt;a class="anchor" href="#2-but-dont-you-love-programming" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;I&amp;rsquo;ve heard this objection countless times: &amp;ldquo;I love programming too much to let AI do it for me.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;Sure, I get it.&#10;It&amp;rsquo;s like preferring analog photography over digital, or writing letters by hand instead of typing.&#10;Some people genuinely enjoy the manual process, and that&amp;rsquo;s valid.&lt;/p&gt;&#10;&lt;p&gt;But here&amp;rsquo;s the thing: &lt;strong&gt;I absolutely love programming&lt;/strong&gt;.&#10;It&amp;rsquo;s my biggest passion in life.&#10;As I mentioned in my &lt;a href="https://www.nijho.lt/post/local-ai-journey/"&gt;local AI journey&lt;/a&gt;, I bought a gaming PC to play games but have only used it for coding and local AI experiments.&#10;My idea of a fun weekend? Writing code until 3 AM.&#10;I&amp;rsquo;ve been doing this for over 10 years, and I&amp;rsquo;ve &lt;strong&gt;never had as much fun programming as I do now&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;What I&amp;rsquo;ve discovered is that I don&amp;rsquo;t just love the act of typing code—I love &lt;strong&gt;building and creating things&lt;/strong&gt;.&#10;There&amp;rsquo;s a difference.&lt;/p&gt;&#10;&lt;p&gt;I&amp;rsquo;m ridiculously particular about code quality.&#10;I literally cannot look at poorly formatted code without feeling physical discomfort.&#10;Every operator, every indentation, every naming convention matters to me.&#10;I enforce strict linting rules and will spend time refactoring code just because the style bothers me.&#10;This isn&amp;rsquo;t about being pretentious—it&amp;rsquo;s about caring deeply about my craft.&lt;/p&gt;&#10;&lt;p&gt;The revelation: AI doesn&amp;rsquo;t take away my ability to care about these details.&#10;Instead, it gives me &lt;strong&gt;insane leverage&lt;/strong&gt; to create more while maintaining my personal standards.&#10;I still review every line (although I am more lenient in certain cases), still enforce my style guides, still refactor when something bothers me.&#10;But now I can build 10x faster.&lt;/p&gt;&#10;&lt;p&gt;It turns out that what I truly love isn&amp;rsquo;t the mechanical act of typing—it&amp;rsquo;s the creative act of bringing ideas to life.&#10;And with AI, I can bring more ideas to life than ever before.&lt;/p&gt;&#10;&lt;h3 id="the-power-to-explore"&gt;The power to explore &lt;a class="anchor" href="#the-power-to-explore" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;AI has unlocked something incredible: the ability to explore ideas that weren&amp;rsquo;t worth the effort before.&#10;It&amp;rsquo;s now trivial to write 2,000 lines of code to solve a simple problem.&#10;Before AI, spending 5+ hours on a utility script wasn&amp;rsquo;t justifiable.&#10;Now? I can build it in 10 minutes.&lt;/p&gt;&#10;&lt;p&gt;Here are just some of the &amp;ldquo;wouldn&amp;rsquo;t have been worth it&amp;rdquo; projects I&amp;rsquo;ve built recently:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;&lt;a href="https://wenfire.nijho.lt/" target="_blank" rel="noopener"&gt;Financial independence tracker&lt;/a&gt;&lt;/strong&gt;: A full website visualizing my path to FIRE&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;&lt;a href="https://github.com/basnijholt/tuitorial" target="_blank" rel="noopener"&gt;Tuitorial&lt;/a&gt;&lt;/strong&gt;: Terminal-based presentation software&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;&lt;a href="https://github.com/basnijholt/home-assistant-streamdeck-yaml" target="_blank" rel="noopener"&gt;Stream Deck home control&lt;/a&gt;&lt;/strong&gt;: Complete tool to control my entire house from a Stream Deck&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;&lt;a href="https://github.com/basnijholt/dotbins" target="_blank" rel="noopener"&gt;Dotbins&lt;/a&gt;&lt;/strong&gt;: Automatic binary dependency syncing across all my machines&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;&lt;a href="https://github.com/basnijholt/agent-cli" target="_blank" rel="noopener"&gt;Agent-CLI&lt;/a&gt;&lt;/strong&gt;: A local, open-source Siri that actually works&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Each of these would have taken weeks of manual coding.&#10;The effort-to-reward ratio just wasn&amp;rsquo;t there.&#10;But with AI? I can explore every random idea that pops into my head at 2 AM.&lt;/p&gt;&#10;&lt;h3 id="the-matty-story-from-midnight-idea-to-working-code"&gt;The Matty story: from midnight idea to working code &lt;a class="anchor" href="#the-matty-story-from-midnight-idea-to-working-code" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Here is the perfect example of this power: One night around midnight, I was lying in bed (slightly intoxicated) when I had an idea—I needed a way for my AI agents to communicate via Matrix.&#10;So I grabbed my iPhone, SSHed into my machine, and started building.&lt;/p&gt;&#10;&lt;p&gt;One hour later, at 1 AM, I had created &lt;strong&gt;&lt;a href="https://github.com/basnijholt/matty" target="_blank" rel="noopener"&gt;Matty&lt;/a&gt;&lt;/strong&gt;—a fully functional terminal-based Matrix client.&#10;Built entirely from my phone.&#10;In bed.&#10;(Poor sleep hygiene, I know.)&lt;/p&gt;&#10;&lt;p&gt;When I woke up the next morning and tested it&amp;hellip; it actually worked!&#10;I spent a few more hours adding tests and cleaning it up, but the core functionality was built in that hour between midnight and 1 AM.&lt;/p&gt;&#10;&lt;p&gt;This is impossible without AI.&#10;Nobody&amp;rsquo;s writing a Matrix client from their phone in bed at midnight.&#10;But with Claude Code? It&amp;rsquo;s just another Tuesday night idea that becomes reality.&lt;/p&gt;&#10;&lt;h3 id="clip-files-ui-when-ideas-strike-at-random-moments"&gt;clip-files UI: when ideas strike at random moments &lt;a class="anchor" href="#clip-files-ui-when-ideas-strike-at-random-moments" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;What happens more often than you&amp;rsquo;d think: I get an idea at a completely random moment and NEED to implement it immediately.&lt;/p&gt;&#10;&lt;p&gt;Case in point: I was sitting in the bathtub during my copy-paste AI era when I realized I needed to access my codebases from anywhere.&#10;I&amp;rsquo;d already built &lt;a href="https://www.nijho.lt/post/advent-of-open-source/15-clip-files/"&gt;&lt;code&gt;clip-files&lt;/code&gt;&lt;/a&gt;—a CLI tool that copies entire codebases to your clipboard—but I wanted it accessible from my phone.&lt;/p&gt;&#10;&lt;p&gt;So I got out of the bathtub, built a &lt;a href="https://github.com/basnijholt/clip-files-ui" target="_blank" rel="noopener"&gt;web UI&lt;/a&gt; for it in 20 minutes, and got back in.&#10;The UI lets me:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Browse all my GitHub repositories&lt;/li&gt;&#10;&lt;li&gt;Select any branch&lt;/li&gt;&#10;&lt;li&gt;Click one button to copy all source code to clipboard&lt;/li&gt;&#10;&lt;li&gt;Paste it into my self-hosted AI chat from anywhere&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Ironically, I rarely use this tool now—Claude Code can explore codebases directly.&#10;But back in the copy-paste era, this 20-minute bathtub interruption made mobile AI coding possible.&lt;/p&gt;&#10;&lt;p&gt;The barrier between &amp;ldquo;wouldn&amp;rsquo;t it be cool if&amp;hellip;&amp;rdquo; and &amp;ldquo;here&amp;rsquo;s a working prototype&amp;rdquo; has essentially disappeared.&lt;/p&gt;&#10;&lt;h3 id="the-800-rule-marathon-80-ai-agents-at-once"&gt;The 800-rule marathon: 80 AI agents at once &lt;a class="anchor" href="#the-800-rule-marathon-80-ai-agents-at-once" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Another thing that would be literally impossible without AI: I decided to enable ALL 800+ Ruff linting rules on a 20,000-line codebase.&lt;/p&gt;&#10;&lt;p&gt;For context, &lt;a href="https://docs.astral.sh/ruff/" target="_blank" rel="noopener"&gt;Ruff&lt;/a&gt; is a extremely fast Python linter that implements rules from over a dozen different tools.&#10;Most projects enable maybe 50-100 rules.&#10;I wanted all 800+.&lt;/p&gt;&#10;&lt;p&gt;The result? &lt;strong&gt;≈2,500 violations&lt;/strong&gt; across the entire codebase.&lt;/p&gt;&#10;&lt;p&gt;Fixing these by hand would take 20 hours if I could fix one per 30 seconds&amp;hellip;&#10;But with Claude Code&amp;rsquo;s agent spawning capabilities, I did something insane:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&lt;strong&gt;Opened 8 terminal windows&lt;/strong&gt; with Claude Code&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Created a work orchestration document&lt;/strong&gt; that one AI managed&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Each session spawned 10 parallel sub-agents&lt;/strong&gt; using &lt;a href="https://docs.anthropic.com/en/docs/claude-code/sub-agents" target="_blank" rel="noopener"&gt;/agents&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Total: ~80 AI agents&lt;/strong&gt; working on my code simultaneously&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Two hours later&lt;/strong&gt;: 100% compliance with all 800 rules&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;The orchestrator agent would assign work like:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&amp;ldquo;Session 1: Fix all E501 line-too-long violations in src/core/&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&amp;ldquo;Session 2: Handle all B008 function-call-in-default-argument issues&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&amp;ldquo;Session 3: Fix all RUF100 unused-noqa violations&amp;rdquo;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Each session&amp;rsquo;s sub-agents would tackle different files in parallel.&#10;When conflicts arose, the orchestrator would resolve them.&#10;This is the kind of code quality improvement that simply wouldn&amp;rsquo;t happen without AI—not because it&amp;rsquo;s technically difficult, but because the human effort required is unrealistic.&lt;/p&gt;&#10;&lt;h3 id="1400-commits-rewritten-in-minutes-for-250"&gt;1,400 commits, rewritten in minutes for $2.50 &lt;a class="anchor" href="#1400-commits-rewritten-in-minutes-for-250" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Here&amp;rsquo;s another &amp;ldquo;impossible without AI&amp;rdquo; story: I had 1,400 commits with terrible messages (in a not-yet-released and private project).&lt;/p&gt;&#10;&lt;p&gt;Since I commit so frequently (using them as snapshots in feature branches), my commit messages were all over the place:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Some were just a period &amp;ldquo;.&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;Some were decent descriptions&lt;/li&gt;&#10;&lt;li&gt;Some were just merge commits&lt;/li&gt;&#10;&lt;li&gt;Zero consistency in style&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;I wanted them all to follow a consistent convention with prefixes like &lt;code&gt;fix:&lt;/code&gt;, &lt;code&gt;feat:&lt;/code&gt;, &lt;code&gt;test:&lt;/code&gt;, &lt;code&gt;ci:&lt;/code&gt;, etc.&lt;/p&gt;&#10;&lt;p&gt;Obviously, rewriting 1,400 commit messages by hand is not going to happen.&#10;But with AI?&lt;/p&gt;&#10;&lt;p&gt;I had Claude write me an agent using the Agno framework that would:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Read each commit&amp;rsquo;s full diff using &lt;code&gt;git show&lt;/code&gt;&lt;/li&gt;&#10;&lt;li&gt;Analyze the changes to understand what was done&lt;/li&gt;&#10;&lt;li&gt;Return structured JSON with three fields:&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;code&gt;commit_message&lt;/code&gt;: The improved message (or empty to keep original)&lt;/li&gt;&#10;&lt;li&gt;&lt;code&gt;keep&lt;/code&gt;: Boolean flag whether to keep the original&lt;/li&gt;&#10;&lt;li&gt;&lt;code&gt;reasoning&lt;/code&gt;: Why the AI made that decision&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;Then the magic happened: &lt;strong&gt;I spawned 1,400 AI agents simultaneously using the DeepSeek API&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;Ten minutes and $2.50 later, all my commit messages were rewritten with consistent, meaningful descriptions.&#10;The entire Git history now looks more professional and searchable.&lt;/p&gt;&#10;&lt;p&gt;The barrier between &amp;ldquo;wouldn&amp;rsquo;t it be cool if&amp;hellip;&amp;rdquo; and &amp;ldquo;here&amp;rsquo;s a working prototype&amp;rdquo; has essentially disappeared.&lt;/p&gt;&#10;&lt;h2 id="3-the-two-phase-ai-revolution"&gt;3. The two-phase AI revolution &lt;a class="anchor" href="#3-the-two-phase-ai-revolution" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;My AI coding journey wasn&amp;rsquo;t a single leap—it happened in two distinct phases, each with its own breakthrough moment.&lt;/p&gt;&#10;&lt;h3 id="phase-1-copy-paste-era-march-2023---july-2025"&gt;Phase 1: copy-paste era (March 2023 - July 2025) &lt;a class="anchor" href="#phase-1-copy-paste-era-march-2023---july-2025" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;When GPT-4 launched in March 2023, it changed everything.&#10;I built tools like &lt;a href="https://www.nijho.lt/post/advent-of-open-source/15-clip-files/"&gt;&lt;code&gt;clip-files&lt;/code&gt;&lt;/a&gt; to efficiently copy code context into a ChatGPT-like web interface.&#10;For over two years, this workflow was:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Manual but effective&lt;/strong&gt;: Copy code → paste into AI → review suggestions → implement manually&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Limited by context&lt;/strong&gt;: Could only share what fit in a single message&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;No validation&lt;/strong&gt;: AI couldn&amp;rsquo;t test its suggestions&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Still valuable&lt;/strong&gt;: Helped with ideation, code review, and refactoring&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;This phase was already productive—I was shipping more code than before.&#10;But I was still the one running tests, debugging errors, and validating everything.&lt;/p&gt;&#10;&lt;h3 id="phase-2-the-claude-code-revolution-july-2025"&gt;Phase 2: the Claude Code revolution (July 2025) &lt;a class="anchor" href="#phase-2-the-claude-code-revolution-july-2025" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Just two months ago, in July 2025, everything changed again.&#10;Frustrated with Cursor becoming painfully slow, I tried Claude Code based on the buzz online.&#10;&lt;strong&gt;That first night, I spent $70 on API tokens&lt;/strong&gt;.&#10;Not by accident—I just kept adding $10-$20 increments like a gambling addict.&#10;The experience was so mind-blowing that within two weeks, I&amp;rsquo;d spent nearly $200 and immediately upgraded to the $200/month Pro plan.&lt;/p&gt;&#10;&lt;p&gt;To put this in perspective: Using a command-line tool &lt;code&gt;ccusage&lt;/code&gt; to track token consumption, I calculated that I used &lt;strong&gt;$10,000 worth of API tokens in my first month&lt;/strong&gt;.&#10;Thankfully, the Pro plan capped my cost at $200!&lt;/p&gt;&#10;&lt;h3 id="what-made-claude-code-different"&gt;What made Claude Code different? &lt;a class="anchor" href="#what-made-claude-code-different" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;The shift from copy-paste to agentic AI was like upgrading from a bicycle to a spaceship:&lt;/p&gt;&#10;&lt;h4 id="before-copy-paste-with-chatgptclaude-web"&gt;Before (copy-paste with ChatGPT/Claude Web)&lt;/h4&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Generate code based on prompts&lt;/li&gt;&#10;&lt;li&gt;No access to your codebase&lt;/li&gt;&#10;&lt;li&gt;Can&amp;rsquo;t run tests or see errors&lt;/li&gt;&#10;&lt;li&gt;You debug everything manually&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h4 id="after-claude-code"&gt;After (Claude Code)&lt;/h4&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Reads and searches your entire codebase&lt;/li&gt;&#10;&lt;li&gt;Executes commands and runs tests&lt;/li&gt;&#10;&lt;li&gt;Sees error messages and debugs itself&lt;/li&gt;&#10;&lt;li&gt;Iterates until tests pass&lt;/li&gt;&#10;&lt;li&gt;Uses tools to explore and validate&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;The difference is profound.&#10;I went from carefully copying snippets with &lt;code&gt;clip-files&lt;/code&gt; to having an assistant that can explore my entire project, run my test suite, fix failures, and even commit the changes.&lt;/p&gt;&#10;&lt;h2 id="4-my-current-agentic-workflow"&gt;4. My current agentic workflow &lt;a class="anchor" href="#4-my-current-agentic-workflow" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Here&amp;rsquo;s how I actually work with Claude Code on a typical project:&lt;/p&gt;&#10;&lt;h3 id="parallel-development-6-features-at-once"&gt;Parallel development: 6 features at once &lt;a class="anchor" href="#parallel-development-6-features-at-once" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;One of Claude Code&amp;rsquo;s superpowers is enabling truly parallel development.&#10;Here&amp;rsquo;s my setup that would make any developer from 10 years ago think I&amp;rsquo;m insane:&lt;/p&gt;&#10;&lt;p&gt;I use &lt;a href="https://zellij.dev/" target="_blank" rel="noopener"&gt;Zellij&lt;/a&gt; (a terminal multiplexer like tmux) with a custom layout for my projects:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;5 main tabs&lt;/strong&gt;: Each split into two panes—Claude Code on one side, terminal on the other&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Using independent copies of same repository&lt;/strong&gt;: Each tab is a separate Git worktree with its own environment, own environment variables, own deployment&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Each tab = different feature&lt;/strong&gt;: Using &lt;a href="https://www.nijho.lt/post/git-worktree/"&gt;Git worktrees&lt;/a&gt; to work on 6 features simultaneously&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Monitoring tabs&lt;/strong&gt;: &lt;code&gt;ccusage&lt;/code&gt; for tracking Claude usage, &lt;code&gt;htop&lt;/code&gt; for CPU, &lt;code&gt;nvtop&lt;/code&gt; for GPU&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Voice-driven orchestration&lt;/strong&gt;: I cycle through tabs, review code while speaking, move to next&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;My workflow looks like this:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Start feature A in tab 1, give Claude instructions&lt;/li&gt;&#10;&lt;li&gt;Switch to tab 2, start feature B while A is working&lt;/li&gt;&#10;&lt;li&gt;Continue through all 5 tabs, starting different features&lt;/li&gt;&#10;&lt;li&gt;Circle back to tab 1, review what Claude did, give feedback via voice&lt;/li&gt;&#10;&lt;li&gt;Repeat the cycle every 10-15 minutes&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;This parallel workflow is how I built a complex project (that I haven&amp;rsquo;t released yet) in one month that would have taken 9+ months before.&#10;The key is &lt;a href="https://www.nijho.lt/post/git-worktree/"&gt;Git worktrees&lt;/a&gt;—each feature gets its own working directory, so there&amp;rsquo;s no context switching overhead.&lt;/p&gt;&#10;&lt;!-- [TODO INSERT GIF: Terminal multiplexer showing multiple Claude Code sessions] --&gt;&#10;&lt;h3 id="starting-a-new-package"&gt;Starting a new package &lt;a class="anchor" href="#starting-a-new-package" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# I describe what I want to build&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s2"&gt;&amp;#34;I need a Python package that manages CLI tool binaries within Git repositories,&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s2"&gt;automatically downloading the correct binary for the user&amp;#39;s platform, here &amp;lt;insert path&amp;gt; is a repo with boilerplate skeleton to copy (use same conventions)&amp;#34;&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Claude Code then:&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# 1. Creates the project structure&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# 2. Implements core functionality&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# 3. Writes comprehensive tests&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# 4. Generates documentation&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# 5. Sets up CI/CD workflows&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id="the-key-difference-iteration-and-validation"&gt;The key difference: iteration and validation &lt;a class="anchor" href="#the-key-difference-iteration-and-validation" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Unlike my vibe coding disaster, Claude Code doesn&amp;rsquo;t just dump code and leave.&#10;Here&amp;rsquo;s a real interaction pattern:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&lt;strong&gt;Claude writes initial implementation&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Claude runs the tests&lt;/strong&gt; → Several fail&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Claude reads the error messages and fixes the code&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Claude runs tests again&lt;/strong&gt; → More pass, some still fail&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Claude debugs the remaining issues&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Claude validates all tests pass&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;I review the final code and understand it (tell it to make changes if needed)&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Claude creates a proper Git commit&lt;/strong&gt;&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;This iterative, validated approach is what makes agentic coding so powerful.&#10;It&amp;rsquo;s not about blindly accepting generated code—it&amp;rsquo;s about having an assistant that can explore, test, and refine solutions.&lt;/p&gt;&#10;&lt;h2 id="5-the-evidence-explosive-productivity"&gt;5. The evidence: explosive productivity &lt;a class="anchor" href="#5-the-evidence-explosive-productivity" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Let me share some concrete data from my PyPI packages analysis:&lt;/p&gt;&#10;&lt;h3 id="package-creation-by-year"&gt;Package creation by year &lt;a class="anchor" href="#package-creation-by-year" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;2016-2022&lt;/strong&gt; (7 years pre-AI): ~2 packages/year average&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;2023&lt;/strong&gt; (GPT-4 launch year): 6 packages&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;2024&lt;/strong&gt; (full year with copy-paste AI): 7 packages&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;2025 until 3 months ago&lt;/strong&gt; (6 months): 7 packages&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;since 3 months&lt;/strong&gt; (2 with Claude Code, 1 with Codex CLI): wrote about 400k line of code (although this includes many iterations)!&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;The acceleration with AI is clear!&lt;/p&gt;&#10;&lt;h3 id="recent-packages-built-with-agentic-ai"&gt;Recent packages built with agentic AI &lt;a class="anchor" href="#recent-packages-built-with-agentic-ai" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Here are some packages I&amp;rsquo;ve built recently with Claude Code:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;&lt;a href="https://github.com/basnijholt/matty" target="_blank" rel="noopener"&gt;&lt;code&gt;matty&lt;/code&gt;&lt;/a&gt;&lt;/strong&gt;: Terminal-based AI chat with file integration&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;&lt;a href="https://github.com/basnijholt/agent-cli" target="_blank" rel="noopener"&gt;&lt;code&gt;agent-cli&lt;/code&gt;&lt;/a&gt;&lt;/strong&gt;: Local-first AI-powered CLI agents (built in days, not weeks!)&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Each of these would have taken me weeks or months to build alone.&#10;With Claude Code, I&amp;rsquo;m shipping production-ready packages in days.&lt;/p&gt;&#10;&lt;h2 id="6-why-this-isnt-vibe-coding-but-with-nuance"&gt;6. Why this isn&amp;rsquo;t &amp;ldquo;vibe coding&amp;rdquo; (but with nuance) &lt;a class="anchor" href="#6-why-this-isnt-vibe-coding-but-with-nuance" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;You might wonder: isn&amp;rsquo;t this just vibe coding with extra steps? The answer is nuanced and depends on the context—similar to my &lt;a href="https://www.nijho.lt/post/dependencies/"&gt;philosophy on dependencies&lt;/a&gt;.&lt;/p&gt;&#10;&lt;h3 id="my-context-driven-standards"&gt;My context-driven standards &lt;a class="anchor" href="#my-context-driven-standards" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Just like I have different standards for dependencies in libraries versus applications, I apply different levels of scrutiny based on what I&amp;rsquo;m building:&lt;/p&gt;&#10;&lt;h4 id="for-critical-libraries-eg-adaptive-pipefunc-unidep"&gt;For critical libraries (e.g., Adaptive, pipefunc, unidep)&lt;/h4&gt;&#10;&lt;p&gt;&lt;strong&gt;Maximum scrutiny&lt;/strong&gt; - These are packages others depend on:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Every single line reviewed and understood&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;100% test coverage with careful test review&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Architecture decisions carefully considered&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Documentation must be comprehensive&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;My reputation is on the line&lt;/strong&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h4 id="for-experimental-clis-and-personal-tools"&gt;For experimental CLIs and personal tools&lt;/h4&gt;&#10;&lt;p&gt;&lt;strong&gt;Pragmatic approach&lt;/strong&gt; - Isolated tools with no downstream dependencies:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Core architecture must be fully understood&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Implementation details can be AI-generated if tests pass&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Test generation can be more automated&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Focus on functionality over perfection&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Similar to my relaxed dependency stance for applications&lt;/strong&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="the-internal-dependency-graph-principle"&gt;The internal dependency graph principle &lt;a class="anchor" href="#the-internal-dependency-graph-principle" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;The key insight: &lt;strong&gt;My scrutiny level correlates with how foundational the code is within the project&lt;/strong&gt;:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&#10;&lt;p&gt;&lt;strong&gt;Core/foundational code&lt;/strong&gt; (what everything else depends on): Maximum scrutiny, every line matters&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Data models, core algorithms, API interfaces&lt;/li&gt;&#10;&lt;li&gt;Authentication, database operations, state management&lt;/li&gt;&#10;&lt;li&gt;These are the &amp;ldquo;roots&amp;rdquo; that everything else builds upon&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;li&gt;&#10;&lt;p&gt;&lt;strong&gt;Peripheral/leaf code&lt;/strong&gt; (nothing depends on it): Can be more AI-delegated&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Plotting functions, display utilities, CLI formatters&lt;/li&gt;&#10;&lt;li&gt;Test helpers, documentation generators&lt;/li&gt;&#10;&lt;li&gt;These are the &amp;ldquo;leaves&amp;rdquo; that don&amp;rsquo;t affect other code&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;li&gt;&#10;&lt;p&gt;&lt;strong&gt;Work projects&lt;/strong&gt;: Always maximum scrutiny for foundational code, regardless of project type&lt;/p&gt;&#10;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;This isn&amp;rsquo;t about being lazy—it&amp;rsquo;s about focusing human attention where it matters most.&#10;I can trust AI more with a plotting function that nothing depends on than with a core data structure that the entire system uses.&lt;/p&gt;&#10;&lt;h3 id="building-constraints-around-ai"&gt;Building constraints around AI &lt;a class="anchor" href="#building-constraints-around-ai" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;The secret to productive agentic coding isn&amp;rsquo;t just the AI—it&amp;rsquo;s the &lt;strong&gt;constraints and guardrails&lt;/strong&gt; I build around it:&lt;/p&gt;&#10;&lt;h4 id="automated-quality-gates"&gt;Automated quality gates&lt;/h4&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Ruff with strictest rules&lt;/strong&gt;: Catches style issues, complexity problems, and common bugs&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;MyPy in strict mode&lt;/strong&gt;: Enforces type safety across the entire codebase&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Pre-commit hooks&lt;/strong&gt;: Automatically format and validate code before commits&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Comprehensive test suites&lt;/strong&gt;: AI must make tests pass, not just write code&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h4 id="project-specific-guidance"&gt;Project-specific guidance&lt;/h4&gt;&#10;&lt;p&gt;Every project gets a &lt;code&gt;CLAUDE.md&lt;/code&gt; file with explicit rules:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;No defensive programming&lt;/strong&gt;: Don&amp;rsquo;t wrap things in try-except unless necessary&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Functional over classes&lt;/strong&gt;: Prefer simple functions in Python&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;No backward compatibility&lt;/strong&gt;: For new projects, embrace breaking changes&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Be ruthless&lt;/strong&gt;: Aggressively remove unused code&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h4 id="custom-commands-and-workflows"&gt;Custom commands and workflows&lt;/h4&gt;&#10;&lt;p&gt;I&amp;rsquo;ve built specific commands that inject context and constraints:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Anti-cruft reviews&lt;/strong&gt;: Remove over-engineering and defensive code&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Safe commit practices&lt;/strong&gt;: Never use &lt;code&gt;git add .&lt;/code&gt;, always selective staging&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Initialize understanding&lt;/strong&gt;: Load project context and current work state&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h4 id="local-virtual-environments-stop-the-hallucinations"&gt;Local virtual environments: stop the hallucinations&lt;/h4&gt;&#10;&lt;p&gt;Here&amp;rsquo;s a critical tip that eliminated a lot of my AI frustrations: &lt;strong&gt;keep a virtual environment with all dependencies installed locally&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;Instead of letting Claude hallucinate how libraries work, I tell it explicitly in my &lt;code&gt;CLAUDE.md&lt;/code&gt;:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-markdown" data-lang="markdown"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="gu"&gt;### Step 1: understand the context&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="k"&gt;-&lt;/span&gt; **READ THE SOURCE CODE**: This library has a &lt;span class="sb"&gt;`.venv`&lt;/span&gt; folder with all dependencies installed.&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; So read the source code when in doubt.&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="k"&gt;-&lt;/span&gt; **Never guess API behavior**: If unsure, inspect the actual implementation in &lt;span class="sb"&gt;`.venv/lib/python*/site-packages/`&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This simple addition transforms Claude from guessing about library APIs to actually reading them:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Before&lt;/strong&gt;: &amp;ldquo;I think your custom AsyncProcessor.batch() method takes a list&amp;hellip;&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;After&lt;/strong&gt;: Reads &lt;code&gt;/path/to/.venv/lib/python3.11/site-packages/my_internal_lib/processor.py&lt;/code&gt; and knows it actually takes an iterator&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;When Claude can read the actual source of your own packages, internal company libraries, or niche dependencies, it stops making assumptions and starts working with facts.&#10;This is especially powerful for:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Your own libraries&lt;/strong&gt; that Claude has never seen before&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Internal company packages&lt;/strong&gt; that aren&amp;rsquo;t public&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Niche libraries&lt;/strong&gt; with barely any GitHub stars or documentation&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Modified versions&lt;/strong&gt; of popular libraries with custom patches&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Edge cases&lt;/strong&gt; where even good documentation doesn&amp;rsquo;t cover everything&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;These constraints transform AI from a loose cannon into a precision tool.&lt;/p&gt;&#10;&lt;h2 id="7-common-pitfalls-ive-noticed"&gt;7. Common pitfalls I&amp;rsquo;ve noticed &lt;a class="anchor" href="#7-common-pitfalls-ive-noticed" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;After a few months of using agentic AI tools, I&amp;rsquo;ve noticed consistent patterns that require vigilance:&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Note from the future: I now realize this is very model dependent! GPT-5 has different pitfalls than Claude Opus 4.1&lt;/strong&gt;&lt;/p&gt;&#10;&lt;h3 id="the-defensive-programming-trap"&gt;The &amp;ldquo;defensive programming&amp;rdquo; trap &lt;a class="anchor" href="#the-defensive-programming-trap" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-python" data-lang="python"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# AI loves this:&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="k"&gt;try&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;result&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;some_function&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="k"&gt;except&lt;/span&gt; &lt;span class="ne"&gt;Exception&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="k"&gt;pass&lt;/span&gt; &lt;span class="c1"&gt;# Silently suppress errors 😱&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# But we need this:&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;result&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;some_function&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="c1"&gt;# Let it fail loudly if something&amp;#39;s wrong&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Claude tends to wrap everything in try-except blocks, suppressing errors that should bubble up.&#10;This is why my &lt;code&gt;CLAUDE.md&lt;/code&gt; explicitly forbids unnecessary error handling.&lt;/p&gt;&#10;&lt;h3 id="the-backwards-compatibility-obsession"&gt;The &amp;ldquo;backwards compatibility&amp;rdquo; obsession &lt;a class="anchor" href="#the-backwards-compatibility-obsession" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Claude constantly adds backwards compatibility for features that were literally just introduced in the same session:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&amp;ldquo;Maintaining compatibility with the old version&amp;rdquo; (that never existed)&lt;/li&gt;&#10;&lt;li&gt;Fallback mechanisms for code paths that were just created&lt;/li&gt;&#10;&lt;li&gt;Multiple ways to do the same thing &amp;ldquo;for flexibility&amp;rdquo;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="the-over-engineering-disease"&gt;The &amp;ldquo;over-engineering&amp;rdquo; disease &lt;a class="anchor" href="#the-over-engineering-disease" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Implements factory patterns for simple object creation&lt;/li&gt;&#10;&lt;li&gt;Adds abstraction layers that serve no purpose&lt;/li&gt;&#10;&lt;li&gt;&amp;ldquo;Production ready&amp;rdquo; code for experimental scripts&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="the-git-commit-sins"&gt;The git commit sins &lt;a class="anchor" href="#the-git-commit-sins" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Despite explicit instructions in &lt;code&gt;CLAUDE.md&lt;/code&gt;:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Creates &lt;code&gt;your_module_v2.py&lt;/code&gt; alongside &lt;code&gt;your_module.py&lt;/code&gt; instead of updating&lt;/li&gt;&#10;&lt;li&gt;Still tries &lt;code&gt;git add -A&lt;/code&gt; or &lt;code&gt;git add .&lt;/code&gt; regularly despite explicit bans&lt;/li&gt;&#10;&lt;li&gt;Loves to &amp;ldquo;helpfully&amp;rdquo; revert debugging changes from other files&lt;/li&gt;&#10;&lt;li&gt;Commits &lt;code&gt;.env&lt;/code&gt; files if not watched carefully&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="the-helpful-anti-patterns"&gt;The &amp;ldquo;helpful&amp;rdquo; anti-patterns &lt;a class="anchor" href="#the-helpful-anti-patterns" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Loves defensive programming&lt;/strong&gt;: Validates things that can&amp;rsquo;t be wrong&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Gladly reads &lt;code&gt;.env&lt;/code&gt;&lt;/strong&gt;: Will expose secrets if not careful&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Reverts unrelated changes&lt;/strong&gt;: &amp;ldquo;Cleans up&amp;rdquo; debugging code from other features&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="the-mission-accomplished-hallucination"&gt;The &amp;ldquo;mission accomplished&amp;rdquo; hallucination &lt;a class="anchor" href="#the-mission-accomplished-hallucination" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;This is a dangerous pitfall.&#10;Claude Code will sometimes claim complete success when it hasn&amp;rsquo;t actually fixed anything:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Claims victory&lt;/strong&gt;: &amp;ldquo;I&amp;rsquo;ve fixed all the issues!&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Ask for proof&lt;/strong&gt;: &amp;ldquo;Show me the test output&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Backpedals&lt;/strong&gt;: &amp;ldquo;Oh, let me actually run the tests&amp;hellip;&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Still claims success&lt;/strong&gt;: &amp;ldquo;Yes, I can see in the logs it works!&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Demand the actual log&lt;/strong&gt;: &amp;ldquo;Show me the exact log file&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Finally admits&lt;/strong&gt;: &amp;ldquo;Actually, there are no log files. The tests don&amp;rsquo;t pass.&amp;rdquo;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;&lt;strong&gt;Always demand proof.&lt;/strong&gt; Never accept &amp;ldquo;it&amp;rsquo;s done&amp;rdquo; without seeing actual test output.&lt;/p&gt;&#10;&lt;h3 id="the-nuclear-option"&gt;The nuclear option &lt;a class="anchor" href="#the-nuclear-option" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;I&amp;rsquo;ve had Claude Code literally try to delete all project files when &amp;ldquo;cleaning up&amp;rdquo;:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Claude&amp;#39;s &amp;#34;helpful&amp;#34; cleanup:&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s2"&gt;&amp;#34;Task complete! Let me remove the temporary files...&amp;#34;&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;rm -rf src/ &lt;span class="c1"&gt;# 😱&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This is why &lt;strong&gt;frequent git commits are non-negotiable&lt;/strong&gt;.&#10;I commit after every small success.&lt;/p&gt;&#10;&lt;h3 id="the-debugging-debris"&gt;The debugging debris &lt;a class="anchor" href="#the-debugging-debris" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;During problem-solving, Claude Code leaves a trail of attempts:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Debug logging statements everywhere&lt;/li&gt;&#10;&lt;li&gt;Failed attempt code commented out&lt;/li&gt;&#10;&lt;li&gt;Multiple approaches tried in parallel&lt;/li&gt;&#10;&lt;li&gt;Temporary test files and scripts&lt;/li&gt;&#10;&lt;li&gt;Extra imports and unused functions&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Before merging, always ask: &amp;ldquo;Review your changes and remove all debugging artifacts and failed attempts.&amp;rdquo;&#10;Getting to a high code coverage (approaching 100%) helps ensure no dead code remains, as long as your tests use public APIs.&lt;/p&gt;&#10;&lt;h3 id="why-this-happens"&gt;Why this happens &lt;a class="anchor" href="#why-this-happens" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;These patterns emerge because AI is trained on public code that often:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Maintains backward compatibility for years&lt;/li&gt;&#10;&lt;li&gt;Uses defensive programming for public APIs&lt;/li&gt;&#10;&lt;li&gt;Includes extensive error handling for user input&lt;/li&gt;&#10;&lt;li&gt;Follows &amp;ldquo;enterprise&amp;rdquo; patterns even for simple scripts&lt;/li&gt;&#10;&lt;li&gt;Contains debugging code from development&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;This is why &lt;strong&gt;constraints are essential&lt;/strong&gt;—without them, Claude defaults to these &amp;ldquo;safe&amp;rdquo; but overcomplicated patterns.&lt;/p&gt;&#10;&lt;h2 id="8-critical-success-factors-what-actually-makes-this-work"&gt;8. Critical success factors: what actually makes this work &lt;a class="anchor" href="#8-critical-success-factors-what-actually-makes-this-work" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;After two months of intense usage, here are the non-negotiable practices that make agentic coding actually productive:&lt;/p&gt;&#10;&lt;h3 id="teach-it-your-test-commands-day-1-priority"&gt;Teach it your test commands (day 1 priority) &lt;a class="anchor" href="#teach-it-your-test-commands-day-1-priority" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;&lt;strong&gt;This is absolutely crucial.&lt;/strong&gt; Claude Code needs to know how to run your tests and how to activate the environment:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# To run tests, use: &lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;uv run pytest tests/ -xvs&lt;span class="s2"&gt;&amp;#34;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s2"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s2"&gt;# For coverage:&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s2"&gt;uv run pytest --cov=src --cov-report=term-missing&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s2"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s2"&gt;# To run specific test&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s2"&gt;uv run pytest tests/test_module.py::test_function&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Without this, it&amp;rsquo;s just guessing whether code works.&#10;With it, it becomes genuinely useful.&lt;/p&gt;&#10;&lt;h3 id="git-commits-are-your-safety-net"&gt;Git commits are your safety net &lt;a class="anchor" href="#git-commits-are-your-safety-net" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;I commit &lt;strong&gt;obsessively&lt;/strong&gt; when using Claude Code:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;After every successful (even partial) feature implementation&lt;/li&gt;&#10;&lt;li&gt;Before letting it attempt any major refactoring&lt;/li&gt;&#10;&lt;li&gt;Whenever tests pass&lt;/li&gt;&#10;&lt;li&gt;Before any &amp;ldquo;cleanup&amp;rdquo; operation&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;But here&amp;rsquo;s the key: &lt;strong&gt;I develop every feature in its own branch&lt;/strong&gt;, even as a solo developer. My workflow:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Create a feature branch for each new feature or fix&lt;/li&gt;&#10;&lt;li&gt;Make frequent commits as snapshots (sometimes just a period for the message or tell Claude to commit)&lt;/li&gt;&#10;&lt;li&gt;Open a pull request to review the full diff myself&lt;/li&gt;&#10;&lt;li&gt;Merge only after reviewing all changes&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;This has saved me from disaster multiple times.&#10;Git is your undo button when Claude goes nuclear (e.g., breaks or removes your code).&lt;/p&gt;&#10;&lt;h3 id="maintain-healthy-skepticism"&gt;Maintain healthy skepticism &lt;a class="anchor" href="#maintain-healthy-skepticism" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Never trust, always verify:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;&amp;ldquo;I fixed it!&amp;rdquo;&lt;/strong&gt; → &amp;ldquo;Show me the test output&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;&amp;ldquo;It&amp;rsquo;s working now!&amp;rdquo;&lt;/strong&gt; → &amp;ldquo;Run the tests again with -xvs&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;&amp;ldquo;The logs show success!&amp;rdquo;&lt;/strong&gt; → &amp;ldquo;Cat the actual log file&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;&amp;ldquo;It&amp;rsquo;s production ready!&amp;rdquo;&lt;/strong&gt; → &amp;ldquo;Did you run the tests?&amp;rdquo;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Think of Claude Code as an enthusiastic junior developer who sometimes exaggerates their accomplishments.&lt;/p&gt;&#10;&lt;h3 id="force-it-to-clean-up-after-itself"&gt;Force it to clean up after itself &lt;a class="anchor" href="#force-it-to-clean-up-after-itself" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;After any debugging session, always:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&amp;#34;Review all your changes and remove:&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;- Debug print statements&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;- Commented out code&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;- Failed attempt implementations&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;- Temporary test files&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;- Unused imports&amp;#34;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;My custom &lt;code&gt;/anti-cruft&lt;/code&gt; command automates this, but you can do it manually too.&lt;/p&gt;&#10;&lt;h3 id="code-coverage-is-your-friend"&gt;Code coverage is your friend &lt;a class="anchor" href="#code-coverage-is-your-friend" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;High test coverage (90%+) ensures:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;The code Claude wrote actually runs&lt;/li&gt;&#10;&lt;li&gt;No dead code from failed attempts&lt;/li&gt;&#10;&lt;li&gt;All paths are exercised&lt;/li&gt;&#10;&lt;li&gt;You can refactor confidently&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="9-my-secret-weapon-voice-to-code-workflow"&gt;9. My secret weapon: voice-to-code workflow &lt;a class="anchor" href="#9-my-secret-weapon-voice-to-code-workflow" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;One of my biggest productivity multipliers isn&amp;rsquo;t Claude Code itself—it&amp;rsquo;s how I communicate with it.&#10;Using my &lt;a href="https://www.nijho.lt/post/local-ai-journey/"&gt;&lt;code&gt;agent-cli&lt;/code&gt;&lt;/a&gt; tool, I&amp;rsquo;ve developed a voice-first workflow that&amp;rsquo;s transformed how I write prompts.&lt;/p&gt;&#10;&lt;h3 id="the-problem-with-typing-prompts"&gt;The problem with typing prompts &lt;a class="anchor" href="#the-problem-with-typing-prompts" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Effective agentic coding requires &lt;strong&gt;precise, detailed instructions&lt;/strong&gt;.&#10;A good prompt isn&amp;rsquo;t 20 words—it&amp;rsquo;s often 200-500 words explaining exactly what you want, what to avoid, and how to approach the problem.&#10;Most people don&amp;rsquo;t want to type that much.&lt;/p&gt;&#10;&lt;h3 id="my-voice-workflow"&gt;My voice workflow &lt;a class="anchor" href="#my-voice-workflow" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Here&amp;rsquo;s my actual workflow:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&lt;strong&gt;Start recording&lt;/strong&gt; with &lt;code&gt;agent-cli transcribe&lt;/code&gt; (hotkey triggered)&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Review Claude&amp;rsquo;s changes&lt;/strong&gt; while speaking my thoughts aloud&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Speak for minutes&lt;/strong&gt; about what I want, what&amp;rsquo;s wrong, what to fix&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Paste the transcription&lt;/strong&gt; directly into Claude Code&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;This is powered by OpenAI&amp;rsquo;s Whisper model running locally on my RTX 3090 at home.&#10;It&amp;rsquo;s more reliable than macOS dictation and gives me complete privacy.&lt;/p&gt;&#10;&lt;h3 id="why-this-works-so-well"&gt;Why this works so well &lt;a class="anchor" href="#why-this-works-so-well" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Rich prompts&lt;/strong&gt;: I naturally give more context when speaking&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Code review narration&lt;/strong&gt;: I can review code while explaining issues&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Thinking out loud&lt;/strong&gt;: Speaking helps clarify my own thoughts&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Speed&lt;/strong&gt;: Speaking is 3-4x faster than typing&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Precision&lt;/strong&gt;: I can be incredibly specific without typing fatigue&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;For example, instead of typing &amp;ldquo;fix the bug,&amp;rdquo; I might say:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&amp;ldquo;I&amp;rsquo;m looking at line 45 where you&amp;rsquo;re handling the authentication.&#10;The problem is you&amp;rsquo;re not checking if the token has expired before making the API call.&#10;Also, you&amp;rsquo;ve added a try-except block here that&amp;rsquo;s suppressing errors—remove that.&#10;And while you&amp;rsquo;re at it, the logging statement on line 52 is using the wrong format.&#10;Make sure to follow our project&amp;rsquo;s logging conventions&amp;hellip;&amp;rdquo;&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;This level of detail is what makes AI coding actually productive.&lt;/p&gt;&#10;&lt;h2 id="10-additional-tips-for-agentic-coding"&gt;10. Additional tips for agentic coding &lt;a class="anchor" href="#10-additional-tips-for-agentic-coding" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Beyond the critical success factors and voice workflow, here are more tips to maximize your productivity:&lt;/p&gt;&#10;&lt;h3 id="set-clear-constraints"&gt;Set clear constraints &lt;a class="anchor" href="#set-clear-constraints" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Create a &lt;code&gt;CLAUDE.md&lt;/code&gt; or similar file in your project root with your preferences:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-markdown" data-lang="markdown"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="gu"&gt;## Project standards&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="k"&gt;-&lt;/span&gt; Never use try/except to suppress errors silently&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="k"&gt;-&lt;/span&gt; Always run pytest before marking task complete&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="k"&gt;-&lt;/span&gt; Use type hints for all functions&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="k"&gt;-&lt;/span&gt; Prefer simple solutions over clever ones&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id="use-the-task-system"&gt;Use the task system &lt;a class="anchor" href="#use-the-task-system" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Claude Code&amp;rsquo;s todo system is great for complex work:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;1. ✅ Implement core functionality&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;2. ✅ Write comprehensive tests&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;3. 🔄 Fix failing tests&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;4. ⏳ Add documentation&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id="leverage-the-search-capabilities"&gt;Leverage the search capabilities &lt;a class="anchor" href="#leverage-the-search-capabilities" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Let Claude search for existing patterns:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&amp;ldquo;Find all API endpoint implementations in this project&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&amp;ldquo;Show me how we handle authentication elsewhere&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&amp;ldquo;What testing patterns are we using?&amp;rdquo;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="review-in-chunks"&gt;Review in chunks &lt;a class="anchor" href="#review-in-chunks" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Instead of reviewing 500 lines at once:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Have Claude implement a single feature&lt;/li&gt;&#10;&lt;li&gt;Review and understand it&lt;/li&gt;&#10;&lt;li&gt;Run tests&lt;/li&gt;&#10;&lt;li&gt;Commit(s) and PR&lt;/li&gt;&#10;&lt;li&gt;Move to the next feature&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;h2 id="11-the-tools-ive-tried"&gt;11. The tools I&amp;rsquo;ve tried &lt;a class="anchor" href="#11-the-tools-ive-tried" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;My journey through AI coding assistants has been evolutionary:&lt;/p&gt;&#10;&lt;h3 id="pre-ai-era"&gt;Pre-AI era &lt;a class="anchor" href="#pre-ai-era" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Manual coding with IDE autocomplete&lt;/li&gt;&#10;&lt;li&gt;Stack Overflow copy-paste&lt;/li&gt;&#10;&lt;li&gt;Productivity baseline: 1-2 packages per year&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="phase-1-copy-paste-tools-march-2023---july-2025"&gt;Phase 1: copy-paste tools (March 2023 - July 2025) &lt;a class="anchor" href="#phase-1-copy-paste-tools-march-2023---july-2025" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;ChatGPT/Claude Web&lt;/strong&gt; + my &lt;a href="https://www.nijho.lt/post/advent-of-open-source/15-clip-files/"&gt;&lt;code&gt;clip-files&lt;/code&gt;&lt;/a&gt; tool&lt;/li&gt;&#10;&lt;li&gt;Manual context sharing&lt;/li&gt;&#10;&lt;li&gt;Helpful for ideation and code review&lt;/li&gt;&#10;&lt;li&gt;Productivity: 3x improvement (from 2 to 6 packages/year)&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="cursor-early-2024"&gt;Cursor (early 2024) &lt;a class="anchor" href="#cursor-early-2024" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Great autocomplete&lt;/li&gt;&#10;&lt;li&gt;Limited context awareness&lt;/li&gt;&#10;&lt;li&gt;Became frustratingly slow&lt;/li&gt;&#10;&lt;li&gt;Still led to my vibe coding disaster&lt;/li&gt;&#10;&lt;li&gt;Productivity: 5x improvement (but with quality issues)&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="phase-2-claude-code-july-2025---present"&gt;Phase 2: Claude Code (July 2025 - present) &lt;a class="anchor" href="#phase-2-claude-code-july-2025---present" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Full codebase awareness&lt;/li&gt;&#10;&lt;li&gt;Can execute commands and debug&lt;/li&gt;&#10;&lt;li&gt;Self-correcting through test iterations&lt;/li&gt;&#10;&lt;li&gt;Maintains context across sessions&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;$70 spent on first night, $10,000 worth in first month&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;Productivity: 24x improvement over pre-AI baseline with maintained quality&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="openais-codex-cli-the-reasoning-beast"&gt;OpenAI&amp;rsquo;s Codex CLI (the reasoning beast) &lt;a class="anchor" href="#openais-codex-cli-the-reasoning-beast" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Recently tried OpenAI&amp;rsquo;s Codex—their new CLI alternative to Claude Code—and I&amp;rsquo;ll admit, for pure reasoning with their GPT-5-Codex model, it&amp;rsquo;s impressive:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Solved a race condition&lt;/strong&gt; in an unfamiliar language that took me hours with Claude Opus&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;More elegant solutions&lt;/strong&gt; for complex algorithmic problems&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Better at deep reasoning&lt;/strong&gt; when given the same context&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;But here&amp;rsquo;s why I still use Claude Code daily:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Claude Code&amp;rsquo;s UX is superior&lt;/strong&gt;: Resume conversations, better interface&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Codex&amp;rsquo;s CLI is fragile&lt;/strong&gt;: Hit Ctrl-C accidentally? Lose everything, start over (muscle memory keeps betraying me!)&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Claude Code handles interruptions&lt;/strong&gt;: First Ctrl-C clears text, second quits gracefully&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;No session persistence&lt;/strong&gt;: Codex forgets everything, Claude Code remembers&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Context management&lt;/strong&gt;: Have to re-provide all context after accidental exits&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;For a complex race condition bug, Codex with GPT-5 gave me the most elegant solution.&#10;But for day-to-day development where I need reliability, good UX, and the ability to resume work?&lt;/p&gt;&#10;&lt;h3 id="why-not-copilot-or-other-cheaper-tools"&gt;Why not Copilot or other &amp;ldquo;cheaper&amp;rdquo; tools? &lt;a class="anchor" href="#why-not-copilot-or-other-cheaper-tools" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Let me be blunt: &lt;strong&gt;You get what you pay for.&lt;/strong&gt; People often say &amp;ldquo;I tried Copilot and it wasn&amp;rsquo;t that useful&amp;rdquo; or &amp;ldquo;Gemini in chat didn&amp;rsquo;t help much.&amp;rdquo; Of course not—these tools are &lt;strong&gt;at least 10x cheaper&lt;/strong&gt; than Claude Code with Opus.&lt;/p&gt;&#10;&lt;p&gt;Your $20/month GitHub Copilot subscription simply cannot provide the same quality or quantity of high-quality tokens as Claude Code.&#10;It&amp;rsquo;s like comparing a bicycle to a Ferrari and wondering why the bicycle isn&amp;rsquo;t as fast.&#10;The economics don&amp;rsquo;t work out:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Copilot&lt;/strong&gt;: $20/month for limited autocomplete&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Claude Code Pro&lt;/strong&gt;: $200/month for unlimited* agentic assistance (*capped, but generous)&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Actual API value used&lt;/strong&gt;: $10,000+/month at my usage level&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;The 10x price difference reflects a 10x (or more) difference in capability.&#10;Copilot is autocomplete on steroids.&#10;Claude Code is a tireless pair programming partner with perfect memory who can debug, test, and iterate.&#10;The ROI is obvious when you&amp;rsquo;re shipping 10x more code.&lt;/p&gt;&#10;&lt;h2 id="12-is-this-sustainable"&gt;12. Is this sustainable? &lt;a class="anchor" href="#12-is-this-sustainable" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;You might wonder if this productivity is sustainable or if I&amp;rsquo;m just building lower-quality software faster.&#10;Here&amp;rsquo;s my honest assessment:&lt;/p&gt;&#10;&lt;h3 id="the-good"&gt;The good &lt;a class="anchor" href="#the-good" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Faster prototyping&lt;/strong&gt;: Ideas to working code in hours, not days&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Better test coverage&lt;/strong&gt;: AI never gets lazy about writing tests&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;More experimentation&lt;/strong&gt;: Lower cost to try new ideas&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Improved documentation&lt;/strong&gt;: AI loves writing docs (I don&amp;rsquo;t)&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Reduced burnout&lt;/strong&gt;: Less time on boilerplate, more on interesting problems&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="the-challenges"&gt;The challenges &lt;a class="anchor" href="#the-challenges" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Code review fatigue&lt;/strong&gt;: You must stay vigilant&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Dependency on tools&lt;/strong&gt;: What if Claude Code disappears?&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Cost&lt;/strong&gt;: $200/month Pro plan (but worth every penny given the $10K+ value)&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;The temptation to &amp;ldquo;vibe&amp;rdquo;&lt;/strong&gt;: Constant discipline required&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Addiction potential&lt;/strong&gt;: I literally couldn&amp;rsquo;t stop coding, having the desire to deplete all tokens and get my money&amp;rsquo;s worth!&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="my-verdict"&gt;My verdict &lt;a class="anchor" href="#my-verdict" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;It&amp;rsquo;s absolutely sustainable &lt;strong&gt;if&lt;/strong&gt; you maintain discipline.&#10;The moment you start accepting code you don&amp;rsquo;t understand, you&amp;rsquo;re building a house of cards.&#10;But with proper review and testing, agentic AI is a massive force multiplier.&lt;/p&gt;&#10;&lt;h2 id="13-the-experience-multiplier-why-seniority-matters-more-than-ever"&gt;13. The experience multiplier: why seniority matters more than ever &lt;a class="anchor" href="#13-the-experience-multiplier-why-seniority-matters-more-than-ever" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Here&amp;rsquo;s a counterintuitive truth about agentic AI tools: &lt;strong&gt;they amplify your existing skills exponentially, not linearly&lt;/strong&gt;.&#10;This creates a fascinating paradox where these tools become increasingly valuable as you become more experienced.&lt;/p&gt;&#10;&lt;h3 id="the-exponential-trap-for-beginners"&gt;The exponential trap for beginners &lt;a class="anchor" href="#the-exponential-trap-for-beginners" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;For beginners, agentic tools can feel like a superpower initially.&#10;They can build a working application in hours!&#10;But here&amp;rsquo;s the danger: without the experience to recognize bad patterns, they&amp;rsquo;re essentially building at 10x speed in the wrong direction.&#10;It&amp;rsquo;s like giving a Formula 1 car to someone who just got their driver&amp;rsquo;s license—the speed multiplies both the distance traveled and the potential for catastrophic crashes.&lt;/p&gt;&#10;&lt;p&gt;A beginner using Claude Code might:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Accept complex solutions they don&amp;rsquo;t understand&lt;/li&gt;&#10;&lt;li&gt;Build massive technical debt at record speed&lt;/li&gt;&#10;&lt;li&gt;Miss architectural problems that will haunt them later&lt;/li&gt;&#10;&lt;li&gt;Create code that &amp;ldquo;works&amp;rdquo; but is impossible to maintain&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;They&amp;rsquo;re forced into a difficult position: either slow down to understand everything (negating the speed benefit) or accumulate technical debt at an exponential rate.&lt;/p&gt;&#10;&lt;h3 id="the-senior-developer-advantage"&gt;The senior developer advantage &lt;a class="anchor" href="#the-senior-developer-advantage" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;For experienced developers, it&amp;rsquo;s a completely different game.&#10;When I look at Claude Code&amp;rsquo;s suggestions, I can instantly recognize:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&amp;ldquo;Oh, that&amp;rsquo;s the Factory pattern—makes sense here&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&amp;ldquo;This error handling is too defensive, let&amp;rsquo;s simplify&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&amp;ldquo;That&amp;rsquo;s going to cause N+1 queries, need to refactor&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&amp;ldquo;This violates our project&amp;rsquo;s conventions, fix it&amp;rdquo;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;The review process that might take a beginner hours takes me minutes.&#10;I&amp;rsquo;m not learning what the code does—I&amp;rsquo;m validating that it does what I already know it should do.&lt;/p&gt;&#10;&lt;h3 id="the-right-way-for-every-level"&gt;The right way for every level &lt;a class="anchor" href="#the-right-way-for-every-level" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;That said, everyone can benefit from agentic tools—you just need to adjust your approach:&lt;/p&gt;&#10;&lt;h4 id="for-beginners"&gt;For beginners&lt;/h4&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Use AI as a learning accelerator&lt;/strong&gt;: Ask it to explain every decision&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Build small projects first&lt;/strong&gt;: Master fundamentals before scaling up&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Prioritize understanding over speed&lt;/strong&gt;: Better to build slowly and learn&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Pair with mentors&lt;/strong&gt;: Have experienced developers review AI-generated code&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h4 id="for-intermediate-developers"&gt;For intermediate developers&lt;/h4&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Focus on patterns&lt;/strong&gt;: Use AI to learn architectural patterns and best practices&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Experiment safely&lt;/strong&gt;: Try new approaches in side projects first&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Question everything&lt;/strong&gt;: Don&amp;rsquo;t accept solutions without understanding the tradeoffs&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h4 id="for-senior-developers"&gt;For senior developers&lt;/h4&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Leverage for velocity&lt;/strong&gt;: Use your experience to review and direct quickly&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Focus on architecture&lt;/strong&gt;: Let AI handle implementation while you design systems&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Teach the AI&lt;/strong&gt;: Create project-specific guidelines to improve output quality&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Push boundaries&lt;/strong&gt;: Explore more ambitious projects now that implementation is faster&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="the-real-multiplier-effect"&gt;The real multiplier effect &lt;a class="anchor" href="#the-real-multiplier-effect" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;The productivity boost isn&amp;rsquo;t just about writing code faster.&#10;For senior developers, agentic tools multiply:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Architecture exploration&lt;/strong&gt;: Test multiple approaches quickly&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Refactoring confidence&lt;/strong&gt;: Refactor fearlessly with AI helping maintain functionality&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Learning velocity&lt;/strong&gt;: Explore new languages and frameworks with a knowledgeable assistant&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Documentation quality&lt;/strong&gt;: Finally have time (and help) for comprehensive docs&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Testing coverage&lt;/strong&gt;: AI never skips tests, even for &amp;ldquo;simple&amp;rdquo; functions&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;This is why I&amp;rsquo;ve been able to ship 14 packages in 18 months.&#10;It&amp;rsquo;s not just that I&amp;rsquo;m writing code faster—I&amp;rsquo;m able to explore ideas, validate approaches, and iterate on designs at a pace that was previously impossible.&lt;/p&gt;&#10;&lt;h2 id="14-reality-check-what-ai-can-and-cant-do"&gt;14. Reality check: what AI can and can&amp;rsquo;t do &lt;a class="anchor" href="#14-reality-check-what-ai-can-and-cant-do" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Many people try AI coding and give up disappointed.&#10;That&amp;rsquo;s because they&amp;rsquo;re treating it like a magic genie that will solve the unsolved problems of the universe.&#10;&lt;strong&gt;It won&amp;rsquo;t.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;h3 id="what-ai-can-do-the-churn-work"&gt;What AI CAN do (the churn work) &lt;a class="anchor" href="#what-ai-can-do-the-churn-work" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;AI excels at tasks you could do yourself but would take hours:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Setting up CI/CD pipelines&lt;/strong&gt;: Boilerplate YAML configuration&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Writing tests&lt;/strong&gt;: Especially unit tests for existing code&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Fixing dependency issues&lt;/strong&gt;: Adapting to breaking changes in libraries&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;CRUD operations&lt;/strong&gt;: Basic create, read, update, delete functionality&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Data transformations&lt;/strong&gt;: Converting between formats, parsing, serialization&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Documentation&lt;/strong&gt;: README files, docstrings, API documentation&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Refactoring&lt;/strong&gt;: Renaming variables, extracting functions, reorganizing code&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Bug fixes&lt;/strong&gt;: Especially those with clear error messages&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;This is the &amp;ldquo;churn&amp;rdquo;—the necessary but time-consuming work that makes up 80% of development.&lt;/p&gt;&#10;&lt;h3 id="what-ai-cant-do-the-creative-work"&gt;What AI CAN&amp;rsquo;T do (the creative work) &lt;a class="anchor" href="#what-ai-cant-do-the-creative-work" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Don&amp;rsquo;t expect AI to:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Solve novel algorithmic problems&lt;/strong&gt;: It won&amp;rsquo;t invent the next PageRank&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Make architectural decisions&lt;/strong&gt;: It can&amp;rsquo;t decide if you need microservices&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Understand business logic&lt;/strong&gt;: It doesn&amp;rsquo;t know why your company does things&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Create truly innovative solutions&lt;/strong&gt;: It remixes what it&amp;rsquo;s seen, not invents&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Make judgment calls&lt;/strong&gt;: Security vs convenience, performance vs maintainability&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="the-sweet-spot"&gt;The sweet spot &lt;a class="anchor" href="#the-sweet-spot" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;I use AI for tasks where:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&lt;strong&gt;I know how to do it&lt;/strong&gt; but it would take time&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;The solution exists&lt;/strong&gt; somewhere in its training data&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Success is measurable&lt;/strong&gt; through tests or clear output&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;The problem is well-defined&lt;/strong&gt; with clear constraints&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;This isn&amp;rsquo;t about AI doing things you can&amp;rsquo;t do—it&amp;rsquo;s about AI doing things you don&amp;rsquo;t want to spend time doing.&#10;Once you understand this, AI becomes incredibly powerful.&lt;/p&gt;&#10;&lt;h2 id="15-looking-forward-the-future-of-development"&gt;15. Looking forward: the future of development &lt;a class="anchor" href="#15-looking-forward-the-future-of-development" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;As I showed in my &lt;a href="https://www.nijho.lt/post/local-ai-journey/"&gt;local AI journey&lt;/a&gt;, I&amp;rsquo;m deeply interested in where AI and development intersect.&#10;Agentic coding represents a fundamental shift in how we build software:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;From writing code to reviewing and directing&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;From memorizing APIs to understanding patterns&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;From debugging alone to collaborative problem-solving&lt;/strong&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;From slower iteration to rapid experimentation&lt;/strong&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;This isn&amp;rsquo;t about replacing developers—it&amp;rsquo;s about amplifying our capabilities.&#10;I&amp;rsquo;m still the architect, the decision-maker, and the quality gatekeeper.&#10;But now I can focus on the interesting problems while my AI assistant handles the implementation details.&lt;/p&gt;&#10;&lt;h2 id="16-conclusion-principles-over-process"&gt;16. Conclusion: principles over process &lt;a class="anchor" href="#16-conclusion-principles-over-process" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;My journey from vibe coding skeptic to agentic coding advocate might seem like a complete reversal, but it&amp;rsquo;s not.&#10;My core principle remains unchanged: &lt;strong&gt;never commit code you don&amp;rsquo;t understand&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;What&amp;rsquo;s changed is the tooling has finally caught up to the promise.&#10;With agentic AI assistants, I can maintain my standards while dramatically increasing my output.&#10;Most of those 32 packages on PyPI have users and are well-tested and documented projects that solve real problems.&lt;/p&gt;&#10;&lt;p&gt;The key is treating AI as what it is: an incredibly powerful assistant, not a replacement for thinking.&#10;Use it to explore ideas faster, implement solutions quicker, and test more thoroughly.&#10;But always, always understand what you&amp;rsquo;re building.&lt;/p&gt;&#10;&lt;p&gt;As I continue building in public and sharing my tools, I&amp;rsquo;m excited to see where this technology takes us.&#10;If you&amp;rsquo;re interested in trying agentic coding yourself, start small, maintain your standards, and prepare to be amazed by what you can build.&lt;/p&gt;&#10;&lt;p&gt;&lt;em&gt;What&amp;rsquo;s your experience with AI coding assistants? Have you tried moving from generative to agentic tools? I&amp;rsquo;d love to hear your thoughts!&lt;/em&gt;&lt;/p&gt;&#10;&lt;h2 id="links-and-resources"&gt;Links and resources &lt;a class="anchor" href="#links-and-resources" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="https://claude.ai/code" target="_blank" rel="noopener"&gt;Claude Code&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://pypi.org/user/basnijholt/" target="_blank" rel="noopener"&gt;My PyPI packages&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://github.com/basnijholt" target="_blank" rel="noopener"&gt;My GitHub&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/vibe-coding/"&gt;Original vibe coding post&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/local-ai-journey/"&gt;My local AI journey&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.nijho.lt/post/using-llms/"&gt;Using LLMs effectively&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;</description></item><item><title>Vibe coding worked—until the 15‑hour cleanup</title><link>https://www.nijho.lt/post/vibe-coding/</link><pubDate>Fri, 21 Mar 2025 00:00:00 +0000</pubDate><guid isPermaLink="false">/post/vibe-coding/</guid><description>&lt;h2 id="i-tried-vibe-coding-for-3-hours-my-application-worked-but-then-i-spent-15-hours-fixing-it"&gt;I tried &amp;ldquo;vibe coding&amp;rdquo; for 3 hours, my application worked, but then I spent 15 hours fixing it &lt;a class="anchor" href="#i-tried-vibe-coding-for-3-hours-my-application-worked-but-then-i-spent-15-hours-fixing-it" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;That&amp;rsquo;s not an exaggeration—it&amp;rsquo;s really what happened.&lt;/p&gt;&#10;&lt;p&gt;Recently, I tried &amp;ldquo;&lt;a href="https://en.wikipedia.org/wiki/Vibe_coding" target="_blank" rel="noopener"&gt;Vibe coding&lt;/a&gt;,&amp;rdquo; a term coined by Andrej Karpathy, a prominent AI researcher, co-founder of OpenAI, and former AI lead at Tesla.&#10;In &lt;a href="https://x.com/karpathy/status/1886192184808149383" target="_blank" rel="noopener"&gt;his viral tweet&lt;/a&gt; from February 2025, Karpathy described vibe coding as a programming approach where you &amp;ldquo;fully give in to the vibes, embrace exponentials, and forget that the code even exists.&amp;rdquo;&#10;It&amp;rsquo;s essentially about letting AI handle the coding based on natural language prompts without closely reviewing the generated code.&lt;/p&gt;&#10;&lt;p&gt;Intrigued by the hype, I decided to experiment with vibe coding using &lt;a href="https://www.cursor.com/" target="_blank" rel="noopener"&gt;Cursor&lt;/a&gt; on a new Python project I called &lt;a href="https://github.com/basnijholt/dotbins" target="_blank" rel="noopener"&gt;dotbins&lt;/a&gt; (&lt;a href="../dotbins"&gt;check out my detailed write-up here&lt;/a&gt;).&amp;quot;&#10;&lt;a href="https://github.com/basnijholt/dotbins" target="_blank" rel="noopener"&gt;Dotbins&lt;/a&gt; manages CLI tool binaries within Git repositories, automatically downloading the correct binary from GitHub for the user&amp;rsquo;s platform and architecture, significantly simplifying my dotfiles and bootstrapping process.&#10;I am super excited about this project but it is not what this post is about.&lt;/p&gt;&#10;&lt;p&gt;Initially, it was fun to get something working so quickly.&#10;Within just three hours, I had a functioning prototype—without carefully examining the code.&#10;But I had unknowingly created a monster—a true &lt;a href="https://en.wikipedia.org/wiki/Spaghetti_code" target="_blank" rel="noopener"&gt;spaghetti&lt;/a&gt; monster! 🍝&lt;/p&gt;&#10;&lt;p&gt;Once I started reviewing the AI-generated code, I realized it was totally incomprehensible.&#10;The AI had implemented the most complicated and roundabout ways to achieve simple tasks.&#10;It introduced redundant checks for impossible conditions, irrelevant error handling, and execution paths that would never trigger.&#10;The code worked superficially, but beneath the surface, it was chaotic and nearly impossible to understand or maintain.&lt;/p&gt;&#10;&lt;p&gt;This realization turned three hours of fun into fifteen hours of meticulous debugging, refactoring, and cleaning up the mess.&#10;Essentially, I had to rewrite the entire project.&lt;/p&gt;&#10;&lt;p&gt;My main takeaway: AI-assisted coding, or &amp;ldquo;vibe coding,&amp;rdquo; is incredibly powerful for quick prototyping but dangerous when used without oversight.&#10;According to &lt;a href="https://www.youtube.com/watch?v=IACHfKmZMr8" target="_blank" rel="noopener"&gt;this recent Y Combinator discussion&lt;/a&gt;, many startup founders are building products almost entirely with AI-generated code, &amp;ldquo;vibing&amp;rdquo; the code, meaning they let the AI write the code and don&amp;rsquo;t review it.&#10;For writing a couple of hundred lines of code it likely works pretty well, but for anything more complex, it&amp;rsquo;s a recipe for disaster.&#10;Personally, I would never invest in, build upon, or use such products—they&amp;rsquo;re essentially constructing technical prisons for themselves.&lt;/p&gt;&#10;&lt;p&gt;AI is fantastic for inspiration, quick prototyping, writing code, and refactoring—but letting it run wild without careful human review can quickly lead to severe technical debt and hidden bugs.&lt;/p&gt;&#10;&lt;p&gt;Thanks for reading!&lt;/p&gt;&#10;</description></item></channel></rss>