{"version":"2.1.311","anchor":"settings-file-write-suspicion-in-auto-mode-permission-checks","canonical_anchor":"settings-file-write-suspicion-in-auto-mode-permission-checks","heading":"Commands that may write Claude Code's own settings get flagged","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/settings-file-write-suspicion-in-auto-mode-permission-checks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Commands that may write Claude Code's own settings get flagged\n\nCommands that write, or may write, to Claude Code's own settings files are now flagged, and no allow rule is suggested for them\n\n**Unclear.** It is not clear whether, in auto mode, you are still stopped and asked before a flagged command runs.\n\n**What**\n\nClaude Code now flags shell commands that write, or may write, to its own settings files. When such a command needs your approval:\n\n- auto mode: if the classifier, the automatic checker that can approve actions, may approve it, Claude Code still marks it as needing approval but may release the hold on it.\n\n- otherwise: the prompt says \"This command writes to one of Claude Code's own settings files.\" or \"This command may write to one of Claude Code's own settings files.\"\n\n- allow rules: Claude Code no longer suggests a rule to always allow the command.\n\nBefore, these commands were always tagged with a fixed message. Usage data now also records why the command was flagged and whether the hold was released.\n\n**Why**\n\nThis changes how you are asked about commands that touch Claude Code's own settings, especially in auto mode, and stops a one-click allow rule from covering them.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}