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
HomeReleasesv2.1.323entry #38

Claude Code v2.1.323 ·

blockFileToolReadsOutsideWorkingDirectories handled in remote execution and /add-dir

Remote execution now removes blockFileToolReadsOutsideWorkingDirectories, and /add-dir warns that file tools still refuse a folder added later

Group of 2 Use it now Notable New Features
JSON All of v2.1.323
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
New FeaturesKind: in v2.1.323,
What probably matters to youSection of the release

Unclear It is not clear whether blockFileToolReadsOutsideWorkingDirectories is something you can set yourself, or what sets it.

What

blockFileToolReadsOutsideWorkingDirectories is a setting that stops Claude's file tools reading outside the working directories, the folders a session works in. Two places now take it into account.

  • Remote execution: when Claude Code prepares permissions for a remote run, it now removes blockFileToolReadsOutsideWorkingDirectories. It already removed blockReadsOutsideWorkingDirectories and blockWritesOutsideWorkingDirectories.
  • A new helper turns on blockWritesOutsideWorkingDirectories when blockFileToolReadsOutsideWorkingDirectories is true and a check passes. Otherwise it forces blockWritesOutsideWorkingDirectories on and adds deny rules that narrow which tools can be used.
  • /add-dir adds a working directory during a session. With the setting on, its result now notes: "The file tools still refuse it: they count only the folders that this session was launched with".

Why

With this setting on, adding a folder with /add-dir does not let the file tools read it. You now get a warning instead of a quiet mismatch. Remote runs do not carry this setting over as it is.

Read from
Names in the bundleblockFileToolReadsOutsideWorkingDirectoriesblockReadsOutsideWorkingDirectoriesblockWritesOutsideWorkingDirectories
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 `blockFileToolReadsOutsideWorkingDirectories` is something you can set yourself, or what sets it.
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