Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.248 ·

DISABLE_AUTOUPDATER now needs a real truthy value

DISABLE_AUTOUPDATER=0 or false no longer disables updates; only truthy values count now.

Use it now Notable Improvements
JSON All of v2.1.248
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Auto UpdaterArea: what it touches
ImprovementsKind: in v2.1.248,
What probably matters to youSection of the release
What

Auto-update suppression used to fire on any non-empty value. It now goes through the shared truthiness parser, which accepts only 1, true, yes or on (case-insensitive, trimmed), so DISABLE_AUTOUPDATER=0 or =false no longer disables the updater as it did in 2.1.247. DISABLE_UPDATES is unchanged.

Details
  • The new check reads the process environment directly rather than the merged environment accessor, so whether a DISABLE_AUTOUPDATER set inside a settings file env block still takes effect depends on that path, which this code does not settle.
Evidence

DISABLE_AUTOUPDATER

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up DISABLE_UPDATES, on Roll out an LLM gateway for your organization. Some Claude Code behavior is built into the installed version rather than set at your gateway, so moving developers to a new release can change behavior across your deployment even when the gateway configuration hasn't changed. To control … llm-gateway-rollout see the edit
Added since A small documentation edit on Development containers touched a line naming DISABLE_AUTOUPDATER after this was published. The Dev Container Feature always installs the latest Claude Code release. To pin a specific Claude Code version for reproducible builds, install it from your Dockerfile with `npm install -g @anthropic-ai/[email protected]` instead of using… devcontainer see the edit
Confirmed since Anthropic's documentation has since written up DISABLE_AUTOUPDATER, on How Claude Code uses prompt caching. A new Claude Code version typically updates the system prompt or tool definitions, so the first conversation you start after an upgrade builds its cache from the top. [Auto-update](/docs/en/setup#auto-updates) downloads new versions in the… prompt-caching see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up DISABLE_AUTOUPDATER, on How Claude Code uses prompt caching.

See this entry in the whole of v2.1.248 →

Feedback