Claude Code 2.1.314 can refuse writes outside the working directories in every mode

Claude Code 2.1.314 adds a setting that blocks file writes outside your project folders, plus group-based routing on the Claude apps gateway. It affects teams that manage Claude Code settings.

what changed

Claude Code 2.1.314 was listed on 30 October 2026. These are the changes that matter most for teams:

  • A new setting, permissions.blockWritesOutsideWorkingDirectories, makes the Write, Edit and NotebookEdit tools refuse paths outside the working directories. It applies in every permission mode.
  • The Claude apps gateway accepts an optional groups list on each upstream. Only developers in the listed identity provider groups are routed to that upstream.
  • VS Code and the Claude Desktop Code tab now compact long conversations that were left idle.
  • /ultrareview now checks workspace trust before it runs git. The Bash shell also stops inheriting which aliases.

why it matters

Until now, how far file edits could reach depended on the permission mode a developer chose. This setting gives an admin one rule that holds in all modes. It helps most where people run Claude Code with fewer prompts and want a hard edge around the project folder.

The gateway change matters for teams that run more than one upstream, for example one for a regulated group and one for everyone else. Group lists let you keep the second group off the first upstream without a separate gateway.

The workspace trust check and the alias change are small, but both close gaps where a repository or shell setup could affect what runs.

what we would do

  • Add permissions.blockWritesOutsideWorkingDirectories to the managed settings you share, and test it on a task that legitimately writes elsewhere, such as a monorepo or a sibling package.
  • Decide which repositories need extra working directories, and list them on purpose instead of widening the rule.
  • If you run the Claude apps gateway with several upstreams, map each one to the IdP groups that should use it, and test with a person who is in no listed group.
  • Check any scripts that relied on a which alias inside the Bash shell.

sources

Drafted with Claude from the linked sources, reviewed by us.