The latest articles on DEV Community by Dimitar Stoyanov (@dimitar_stoyanov_3fe3b0bf). https://dev.to/dimitar_stoyanov_3fe3b0bf https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3930992%2F11f7c5bc-b8f7-4612-94d2-f513311b46a2.jpg https://dev.to/dimitar_stoyanov_3fe3b0bf en Dimitar Stoyanov Thu, 14 May 2026 10:32:41 +0000 https://dev.to/dimitar_stoyanov_3fe3b0bf/how-to-keep-claude-code-on-opus-46-without-breaking-your-normal-install-2lh https://dev.to/dimitar_stoyanov_3fe3b0bf/how-to-keep-claude-code-on-opus-46-without-breaking-your-normal-install-2lh <p>There's been a lot of discussion recently around how Claude Code updates affect behavior, predictability, and token usage.</p> <p>When Claude Code updates, it's not just the model that changes - the CLI harness, system prompts, tool-calling behavior, and context management all evolve too. Newer is often better. But not always for every workflow.</p> <p>In my own setup, I noticed that some skills, agents, and project workflows I'd built behaved differently after recent updates. Not necessarily worse, but differently enough that predictability started to matter.</p> <p>For AI-assisted development, that matters.</p> <h2> The problem </h2> <p>Sometimes you want the latest model. Sometimes you want the setup your workflow was built around.</p> <p>There's no built-in way to run an older Claude Code version side-by-side with the latest one. If you pin the model with <code>--model</code>, you still get the latest harness — and harness changes can affect behavior just as much as model changes.</p> <h2> The solution: <code>claude46</code> </h2> <p>I made a small open-source helper that gives you a separate <code>claude46</code> command:</p> <ul> <li> <strong>Claude Code pinned to 2.1.110</strong> (the pre-Opus-4.7 harness)</li> <li> <strong>Opus 4.6 1M</strong> as the default model</li> <li> <strong>Auto-updates fully blocked</strong> for that launcher only</li> <li>Your normal <code>claude</code> install is <strong>left untouched</strong> and free to update</li> </ul> <h3> One-liner install </h3> <p>macOS / Linux:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight shell"><code>curl <span class="nt">-fsSL</span> https://raw.githubusercontent.com/sparklingneuronics/claude-code-helpers/v0.2.0/install-claude46.sh | bash </code></pre> </div> <p>Windows (PowerShell):<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight powershell"><code><span class="n">irm</span><span class="w"> </span><span class="nx">https://raw.githubusercontent.com/sparklingneuronics/claude-code-helpers/v0.2.0/install-claude46.ps1</span><span class="w"> </span><span class="o">|</span><span class="w"> </span><span class="n">iex</span><span class="w"> </span></code></pre> </div> <p>Then just run <code>claude46</code> instead of <code>claude</code>.</p> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6fuze4ahpyoonx5tnh6l.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6fuze4ahpyoonx5tnh6l.png" alt=" " width="800" height="383"></a></p> <h2> Is it better? </h2> <p>Not universally. I still use newer versions. But for workflows tuned around previous behavior — especially skills and agents built on top of Claude Code — having a stable pinned setup is useful.</p> <p>The same idea as pinning a compiler or framework version: you want to choose when to upgrade, not have it happen under you.</p> <h2> How it works </h2> <p>The bash installer downloads Claude Code 2.1.110 to <code>~/.local/share/claude46/</code> and writes a wrapper script that sets <code>DISABLE_AUTOUPDATER=1</code>, <code>DISABLE_UPDATES=1</code>, and <code>ANTHROPIC_MODEL=claude-opus-4-6[1m]</code> before exec-ing the pinned binary.</p> <p>The Windows installer does the same via <code>npm install --prefix</code> into <code>%LOCALAPPDATA%\claude46\</code>, writing a <code>.cmd</code> wrapper with the same env vars.</p> <p>Both are tested end-to-end via CI on real runners.</p> <h2> Links </h2> <ul> <li>Repo: <a href="https://github.com/sparklingneuronics/claude-code-helpers" rel="noopener noreferrer">github.com/sparklingneuronics/claude-code-helpers</a> </li> <li>MIT licensed, no telemetry, no API proxy</li> </ul> ai claude cli tutorial