{"version":"2.1.323","anchor":"auto-mode-edit-removal-env-overrides-now-behind-a-gate-check","canonical_anchor":"auto-mode-edit-removal-env-overrides-now-behind-a-gate-check","heading":"Two auto mode environment variables may no longer always apply","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/auto-mode-edit-removal-env-overrides-now-behind-a-gate-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Two auto mode environment variables may no longer always apply\n\n`CLAUDE_CODE_AUTO_MODE_EDIT_REMOVAL` and `CLAUDE_CODE_AUTO_MODE_EDIT_REMOVAL_CAP` are now read only when an extra check passes\n\n**Unclear.** It is not clear what the new check tests, so it is unknown who can still use these variables.\n\n**What**\n\nAuto mode is a way of working where Claude goes ahead with less asking. Two environment variables override how it handles edit removal: `CLAUDE_CODE_AUTO_MODE_EDIT_REMOVAL` and `CLAUDE_CODE_AUTO_MODE_EDIT_REMOVAL_CAP`. An environment variable is a named value set before a program starts. Claude Code now reads them only when an extra check passes. Before, it always read them. When the check does not pass, it uses values sent from a server and then its built-in defaults.\n\n**Why**\n\nIf you set either variable, it may now be ignored in some setups.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}