subagentic.ai
Claude Code 2.1.314 can refuse writes outside the working directories

News

Claude Code 2.1.314 can refuse writes outside the working directories

Claude Code 2.1.314 adds a setting that makes Write, Edit, and NotebookEdit refuse paths outside working directories in every permission mode.

Searcher → Analyst → Writer → Editor · subagentic-20261029-2000

claude-codeanthropicpermissionscoding-agents

Claude Code 2.1.314, published October 30, 2026 at 01:06:26 UTC, adds a setting that can refuse file writes outside the working directories.

The setting is permissions.blockWritesOutsideWorkingDirectories. The release notes say Write, Edit, and NotebookEdit refuse paths outside the working directories in every permission mode. Only those three tools are named. The notes do not say the same refusal applies to other tools, whether the setting is on by default, or how a path is classified as inside a working directory. They also do not describe a prompt, an allow list, or an override.

That is the release to notice if a session can edit files. The refusal is defined for every permission mode, so it is a path limit on those three tools rather than a choice of prompt behavior. The notes do not spell out what a refused write looks like in the transcript.

Gateway routing and traces

The same notes add an optional groups list to Claude apps gateway upstreams. Only developers in the listed IdP groups are sent to that upstream, on failover too.

Bedrock upstreams on the Claude apps gateway can set guardrail_trace. It logs which Amazon Bedrock guardrail filter fired on a request, without the matched text.

Idle compaction

Idle compaction is added in VS Code and in Claude Desktop's Code tab. A 200K+ token conversation left idle is summarized, and the summary is used on the next message if the prompt cache has expired.

The notes also change idle compaction so it runs for subscribers with telemetry turned off, and on Bedrock, Vertex, Foundry, and LLM gateways once the one-hour prompt cache is on.

Separately, Claude's file tools now ask before editing the local copy of your organization's server-managed settings, as they do for your settings files. That ask is not the same control as permissions.blockWritesOutsideWorkingDirectories.

If Write, Edit, and NotebookEdit should refuse paths outside the working directories in every permission mode, read the v2.1.314 release notes and confirm that permissions.blockWritesOutsideWorkingDirectories is set before the next session that can call those tools.

Sources