{"version":"2.1.286","anchor":"claude-code-auto-mode-tier-env-var-any-set-value-selects-s","canonical_anchor":"claude-code-auto-mode-tier-env-var-any-set-value-selects-s","heading":"New CLAUDE_CODE_AUTO_MODE_TIER variable selects the strict auto mode tier","tier":"use","area":"Auto Mode","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/claude-code-auto-mode-tier-env-var-any-set-value-selects-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### New CLAUDE_CODE_AUTO_MODE_TIER variable selects the strict auto mode tier\n\nSetting `CLAUDE_CODE_AUTO_MODE_TIER` to any value selects the \"strict\" auto mode tier, and it is passed on to processes Claude Code starts\n\n**Unclear.** What the \"strict\" tier restricts in practice is not clear.\n\n**What**\n\n`CLAUDE_CODE_AUTO_MODE_TIER` is a new environment variable, a setting passed to Claude Code when it starts. It relates to auto mode, where Claude Code acts with less asking.\n\n- If it is not set, the default applies.\n\n- If it is set to anything at all, even \"full\", the tier becomes \"strict\".\n\n- A nearby prompt line reads `Everything else \u2192 tier \"full\": no restrictions`.\n\n- When set, it is added to the list of variables Claude Code writes in front of commands, next to `CLAUDE_SECURESTORAGE_CONFIG_DIR`, so it appears to be handed on to processes Claude Code starts.\n\nWhat the strict tier restricts was not traced.\n\n**Why**\n\nThis is an opt-in way to force a stricter auto mode. Because any value turns it on, setting it to \"full\" or \"0\" does not turn it off; remove the variable instead.\n\n- Area: Auto Mode\n- Names: `CLAUDE_CODE_AUTO_MODE_TIER`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 4\/5"}