{"version":"2.1.302","anchor":"new-auto-mode-eligibility-check-is-a-constant-false-stub","canonical_anchor":"new-auto-mode-eligibility-check-is-a-constant-false-stub","heading":"Auto mode access check gains an extra condition that does nothing yet","tier":"soon","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/new-auto-mode-eligibility-check-is-a-constant-false-stub","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Auto mode access check gains an extra condition that does nothing yet\n\nThe check for whether you can enter auto mode now has an extra blocking condition, which is fixed to never block for now\n\n**What**\n\nBefore 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.\n\n**Why**\n\nNothing 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.\n\n- Flag `tengu_auto_mode_config`: Not enough to say (read for one account on one subscription tier against v2.1.302; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Auto Mode\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}