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 ·

Sandbox withholds write access to paths that could be redirected

The Windows and Linux sandbox now refuses an allowWrite grant whose path leads elsewhere or to nothing yet, and logs why

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

Unclear Whether this check applies to every sandbox setup or only some.

What

The sandbox now holds back an allowWrite grant (a path you allowed sandboxed commands to write to) when that path does either of these:

  • leads somewhere other than its own spelling, for example through a shortcut-style link
  • leads to nothing that exists yet

In both cases a sandboxed command could re-point the path somewhere else. The log notes the grant as withheld and suggests spelling the grant by its real path.

Separately, when blockReadsOutsideWorkingDirectories applies, one more configuration folder is added to the folders re-opened despite denyRead.

Why

Write access granted through a redirectable path is now stricter. If a write grant stops working, list the real folder rather than a link to it.

Read from
Names in the bundleallowWrite
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 doubtWhether this check applies to every sandbox setup or only some.
Anthropic's release notes agreeFixed a case where the Write and Edit tools could write to a path covered by a Read deny rule

See this entry in the whole of v2.1.323 →

Feedback