Claude Code v2.1.314: writes confined to the working directories, idle compaction in the IDE#

Published by

Part of the Claude Code Version Tracker series. | Official Env Vars | Official Changelog

Claude Code v2.1.314, the release after v2.1.312, adds permissions.blockWritesOutsideWorkingDirectories: Write, Edit, and NotebookEdit refuse paths outside the working directories in every permission mode.[1] It also brings idle compaction to VS Code and Claude Desktop's Code tab, and keeps sessions running when an organization's admin caps a model's effort level.[1]

A write boundary that holds in every mode#

permissions.blockWritesOutsideWorkingDirectories makes the Write, Edit, and NotebookEdit tools refuse any path outside the working directories, and it applies in every permission mode.[1] For a session that otherwise runs with broad permissions, this draws a hard line on where edits can land, independent of how approvals are set.

Idle compaction reaches the IDE#

VS Code and Claude Desktop's Code tab now get idle compaction. A conversation past 200K tokens that is left idle is summarized, and that summary is used on your next message if the prompt cache has expired.[1] A long IDE conversation that sat untouched no longer pays the full context cost to pick back up once its cache is gone.

Sessions recover from provider and org limits#

When an organization's admin caps a model's effort level, Claude Code now lowers the effort, retries the request, and names the level it used, so a capped model keeps running where it had failed turn after turn with "Invalid effort level."[1] Several provider fixes recover from a repeating failure instead of failing every turn:

  • Bedrock sessions with many images remove older images and compact, where they had failed every turn and on /compact with "400 Input is too long."[1]
  • Microsoft Foundry sessions fall back to an older model of the family when the resource has no deployment for the default Sonnet, Opus, or Haiku.[1]
  • Requests behind a gateway that rejects tool search's tool_reference blocks are sent again once without tool search, and the session remembers.[1]
  • MCP servers that also work without sign-in are used signed out once their stored sign-in stops working.[1]

Other connection and CLI fixes:

  • TLS connections no longer fail with UNABLE_TO_GET_ISSUER_CERT when the system certificate store holds a renewed root cross-signed with its predecessor.[1]
  • When startup fails, claude -p prints the error and exits 1.[1]
  • claude ultrareview and claude remote-control refuse an untrusted folder at once in a CI job with a terminal when CI is set.[1]

For Claude apps gateway admins#

Two additions land on gateway upstreams:

AdditionWhat It Does
groups on gateway upstreamsAn optional list of IdP groups. Only developers in the listed groups are sent to that upstream, including on failover.[1]
guardrail_trace on Bedrock upstreamsLogs which Amazon Bedrock guardrail filter fired on a request, without the matched text.[1]

Most of these fixes sit on managed and gateway paths#

The effort cap, Bedrock images, Foundry deployments, gateway tool_reference, and managed TLS trust all run through a provider or an administrator's policy, and each surfaced as a repeating failure.[1] For a team running Claude Code behind its own model infrastructure, a repeating failure means messages keep failing until a person steps in; a downgrade, retry, or fallback that the session then remembers is what keeps the seat usable. The write boundary belongs to the same surface: permissions.blockWritesOutsideWorkingDirectories holds in every permission mode, so the boundary does not loosen when a session runs with broader approvals.[1]

This analysis is conducted for educational and research purposes under fair use principles. All trademarks and software referenced belong to their respective owners.

Sources#

  1. Claude Code Official Changelog, v2.1.314 release notes

Let's Connect

BlueskyLinkedInThreads

Previous Claude Code analysis: v2.1.312 (October 29, 2026)

Next Claude Code analysis: v2.1.315 (October 31, 2026)

All 84 Claude Code analyses: Claude Code Version Tracker · Official Claude Code changelog

← Back to all posts