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.302 ·

Auto mode access check gains an extra condition that does nothing yet

The check for whether you can enter auto mode now has an extra blocking condition, which is fixed to never block for now

Nothing to try yet In Development
JSON All of v2.1.302
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Auto ModeArea: what it touches
In DevelopmentKind: in v2.1.302,
In DevelopmentSection of the release
What

Before letting you switch into auto mode, one of Claude Code's permission modes, Claude Code checks whether you are allowed to. That check now includes a new condition that can block auto mode. In this build the condition is fixed to never block, so whether you can enter auto mode works exactly as it did before.

Why

Nothing changes today. The new condition is a place where a future release can add a rule that stops auto mode from being available, without changing the rest of the check.

Read from
Feature flag
tengu_auto_mode_config Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.302: not a boolean we can read

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.302. It isn't a statement about your account. What a flag value here can and cannot tell you

See this entry in the whole of v2.1.302 →

Feedback