{"version":"2.1.323","anchor":"auto-mode-git-status-env-overrides-now-only-honored-when-a-g","canonical_anchor":"auto-mode-git-status-env-overrides-now-only-honored-when-a-g","heading":"Auto mode git status environment variables now apply only in some cases","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/auto-mode-git-status-env-overrides-now-only-honored-when-a-g","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Auto mode git status environment variables now apply only in some cases\n\nThe three auto mode git status environment variables are now read only when an extra check passes, not every time\n\n**Unclear.** What the extra check tests, and so where these variables still work, is not known.\n\n**What**\n\nAuto mode lets Claude Code decide on its own which actions need your approval. Three environment variables let you override how it handles git status, the summary of changed files in your project. An environment variable is a value you set in your shell before starting Claude Code. The three are:\n\n- `CLAUDE_CODE_AUTO_MODE_GIT_STATUS`\n\n- `CLAUDE_CODE_AUTO_MODE_GIT_STATUS_UPLOADS`\n\n- `CLAUDE_CODE_AUTO_MODE_GIT_STATUS_LIMIT`\n\nBefore, Claude Code always read them. It now reads them only when an extra check passes. Otherwise it uses values sent from the server, and if there are none, its built-in defaults.\n\n**Why**\n\nIf you set these variables, they may stop having any effect in some setups.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}