Anthropic’s Claude Code 2.1.314 adds a setting that blocks file edits outside working directories, alongside new access controls and reliability fixes. For teams using Claude Code, the update puts more guardrails around where tools can write and which users reach particular gateway services.
Anthropic Watch analysis
What happened
Anthropic’s release notes, published on 30 October, describe changes across Claude Code, Claude Desktop, VS Code and the Claude apps gateway. Among the practical additions, idle conversations over 200,000 tokens can be summarised in the VS Code and Desktop Code tab, and Bedrock gateway logs can record which guardrail filter fired without logging the matched text.
Our top picks
- Block writes beyond working directories
Write, Edit and NotebookEdit now refuse paths outside working directories in every permission mode. - Restrict gateway access by identity group
Administrators can limit an upstream to developers in specified identity-provider groups, including during failover. - Trace Bedrock guardrail triggers
Gateway logs can show which filter fired without including the text that matched it. - Resume long idle conversations
The VS Code and Desktop Code tab can summarise an idle conversation above 200,000 tokens when its prompt cache has expired. - Recover from capped effort settings
When an organisation limits a model’s effort level, Claude Code now lowers it, retries and reports the level used. - Make failed startup visible
A failed claude -p startup now prints an error and exits with code 1 instead of silently returning no output with a success code.
Why it matters
These changes address several real operator concerns: controlling file boundaries, narrowing who can reach a gateway, and making security-filter activity more diagnosable without putting matched text in the log. The release also tidies up failure handling, from oversized Bedrock sessions to model-effort limits.
Our read
This is a substantial maintenance release with useful controls, not a reason to assume every workflow is now foolproof. Teams should pay particular attention to the new write boundary and group restrictions, then test them against their own permission and failover setups. A guardrail is only comforting if it fits the door you meant to close.
What to watch
- Whether the working-directory restriction fits projects that deliberately edit files elsewhere.
- How gateway group restrictions behave during failover.
- Whether the new idle summaries help teams resume long sessions without losing useful context.
Discussion spark: Should coding agents be blocked from writing outside a project by default, even when that makes legitimate cross-project work less convenient?
Sources and evidence
- v2.1.314 (30 October 2026, 01:06 UTC)
Anthropic Watch is independently operated by WittyWires. It is not affiliated with, endorsed by, or operated by Anthropic.