New setting blocks file writes outside the working directories
blockWritesOutsideWorkingDirectories stops Claude's file tools writing outside your working folders and protects settings files, but is not sent to remote runs
Does not limit shell commands, MCP tools (tools supplied by outside servers) or hooks (your own scripts that Claude Code runs at set moments).
When a write is refused, the message tells you to add the folder with /add-dir or remove the setting.
The description of blockReadsOutsideWorkingDirectories now says that no allow rule lifts it.
For remote execution, the sandbox settings now drop blockWritesOutsideWorkingDirectories as well as blockReadsOutsideWorkingDirectories before the settings are forwarded. Before, only the read setting was dropped.
Why
This gives a firm limit on where Claude's file tools can write. Two things to watch: shell commands, MCP tools and hooks can still write elsewhere, and the setting is not passed on to remote runs, so a remote session will not enforce it.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtOnly the new messages are confirmed, so it is unclear whether this setting itself is new or already worked before.
Anthropic's release notes agreeAdded permissions.blockWritesOutsideWorkingDirectories: Write, Edit and NotebookEdit refuse paths outside the working directories in every…
