Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.257 ·

New permissions.blockReadsOutsideWorkingDirectories setting, with network-path detection for working directories

Network paths are detected before the stat check and reported as their own result type when adding trusted directories.

TierYou'll noticehow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaWorking Directorieswhat it touches
KindImprovementsin v2.1.257,
Group of 3 You'll notice No documentation found

Network paths are detected before the stat check and reported as their own result type when adding trusted directories.

A new setting, permissions.blockReadsOutsideWorkingDirectories, is now read from settings and propagated through settings serialization/merge. When enabled it switches directory validation to a stricter check (kHt(n) instead of fS(n)), adds blockReadsOutsideWorkingDirectories: true to the tool permission context, and is enforced in the sandbox filesystem policy, command-parsing/read-permission logic, and user-facing deny/ask messages ("Reads outside the working directories are blocked"). It is explicitly stripped out for remote-execution permission modes.

Alongside it, validating a directory to add as a trusted working directory (validateDirectoryForWorkspace) now checks whether the path is a network path before doing a normal stat, returning a new networkPath result type instead of treating it as an ordinary directory-check failure. This rejects UNC/network paths from being added as working directories, with guidance about drive-letter mapping on Windows.

Read from
Names in the bundlenetworkPath

See this entry in the whole of v2.1.257 →

Feedback