Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

Permission changes now pass through a check that can explain itself

Saved permission changes now go through a shared check that can alter them and add a note to the session saying why

Under the hood Internal Changes
JSON All of v2.1.323
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Internal ChangesKind: in v2.1.323,
Internal ChangesSection of the release

Unclear Which permission changes the check alters or drops, and on what grounds, is not known.

What

A permission rule is a saved choice about what Claude Code may do without asking you first. Several places that save these rules now pass them through one shared check before saving. The check can return a changed set of rules and a reason. When it gives a reason, Claude Code adds it to the session as a system note, a short message from Claude Code rather than from you or the model.

The places that now use this check are:

  • the network access prompt shown while Claude Code runs in a sandbox, a restricted mode that limits what commands can reach
  • the path used when Claude Code is started by a launcher
  • the "always allow" choice in a permission dialog
  • network rules

Before, these places saved the rules directly.

Why

A rule you approve may now be saved in a changed form or not saved at all, and Claude Code tells you why in the session when that happens.

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 doubtWhich permission changes the check alters or drops, and on what grounds, is not known.

See this entry in the whole of v2.1.323 →

Feedback