Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.311 ·

Commands that may write Claude Code's own settings get flagged

Commands that write, or may write, to Claude Code's own settings files are now flagged, and no allow rule is suggested for them

You'll notice Improvements
JSON All of v2.1.311
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.311,
ImprovementsSection of the release

Unclear It is not clear whether, in auto mode, you are still stopped and asked before a flagged command runs.

What

Claude Code now flags shell commands that write, or may write, to its own settings files. When such a command needs your approval:

  • 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.
  • 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."
  • allow rules: Claude Code no longer suggests a rule to always allow the command.

Before, 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.

Why

This 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether, in auto mode, you are still stopped and asked before a flagged command runs.

See this entry in the whole of v2.1.311 →

Feedback