Claude Code 2.1.327 is dated November 17, 2026 in the official changelog. The changelog records permission and sandbox changes across recent releases, including stricter command checks, safer handling of writes, fail-closed behavior for some permission cases, and improvements to MCP authentication and reconnection. A version number alone does not establish that a client repository is affected. The relevant question is whether the agency's actual CLI, managed settings, shell, MCP servers and unattended tasks still produce the intended approval boundary.
Capture the rollout boundary
Record the CLI version, operating system, shell, repository path, managed settings source, MCP transport, permission mode and whether the task is interactive or unattended. Do not place credentials or private client content in the record. Note whether a custom gateway, agent teams, hooks or a sandbox exception is part of the workflow.
Run safe acceptance cases
On an authorized non-production clone, test one case per permission class:
- read a repository file;
- edit a harmless fixture;
- run a harmless shell command;
- trigger an allowed hook and a blocked hook;
- reconnect an MCP server without exposing its token;
- test a denied path and a path outside the working directory;
- resume a task after a controlled connection interruption.
Record the prompt, refusal, approval source, working directory, MCP state and resulting diff. An interactive success does not prove that an unattended build or a different shell will behave the same way.
Keep recovery bounded
When a task pauses, identify the exact command or path that changed behavior. Do not disable the sandbox or add a broad allow rule solely to meet a deadline. Choose among a managed policy correction, a narrow rule with an owner, a manual handoff or a rollback to the previously approved CLI while the new behavior is reviewed.
The handoff should contain the installed version, policy source, acceptance results, client data sensitivity, owner and restoration condition. This separates a tool rollout from a client application change.
Applicability and limits
This article concerns Claude Code CLI behavior and the organization, platform and plan settings that enable it. It does not claim a vulnerability, a customer incident or universal behavior across Claude products. Recheck the official changelog before implementation.
Primary source: Claude Code changelog.