Claude Code v2.1.324: no changelog of its own; the 2.1.325 notes add sandboxed Bash prompts and a /login privacy prompt#
Published by Alex Sorokoletov
Part of the Claude Code Version Tracker series. | Official Env Vars | Official Changelog
Claude Code 2.1.324, the release after 2.1.323, has no changelog entry of its own. The changelog's next release, 2.1.325, records that sandboxed Bash commands now follow the normal permission flow by default, that read-only git commands ask first in a repository you have not trusted, and that /login asks for permission to change your privacy settings.[1]
Sandboxed Bash commands follow the permission flow by default#
The 2.1.325 changelog changes sandboxed Bash commands to follow the normal permission flow by default.[1] A command that Claude Code runs inside its sandbox now goes through the same permission step as any other Bash command, and it can surface the usual allow-or-deny prompt before it runs. For a session with the sandbox turned on, that permission step now covers sandboxed commands as well.
Read-only git commands ask first in an untrusted repository#
The same changelog changes read-only git commands to ask first in a repository that is not the project's or one you have trusted.[1] A read-only git command, a git status or git log for instance, now brings up a prompt when it runs in a checkout outside your project or your trusted list. Inside the project you opened, or a repository you have already trusted, these commands are unaffected.
/login asks before changing your privacy settings#
The changelog also changes /login, the sign-in command, to ask for permission to change your privacy settings.[1] Signing in now stops for your consent at the point where it would set a privacy option, so a sign-in does not move that setting without a prompt.
In the 2.1.325 changelog#
| Area | Change |
|---|---|
| Sandboxed Bash | Sandboxed Bash commands follow the normal permission flow by default. |
| Read-only git | Read-only git commands ask first in a repository that is not the project's or one you trusted. |
| Sign-in | /login asks for permission to change your privacy settings. |
| Connectors | Fixes a working Atlassian, Asana or Sentry connector being reported as failed in cloud sessions. |
More steps now pause for a prompt#
The changes the 2.1.325 changelog records point the same way, toward asking before acting: sandboxed Bash commands follow the permission flow, read-only git commands in an untrusted repository ask first, and /login asks before it touches your privacy settings. The first two matter most in an unattended context such as the SDK, claude -p or a CI job, where a permission prompt is a stop: a run that reaches a sandboxed command or an untrusted git checkout holds for a decision. Because 2.1.324 carries no notes of its own, the 2.1.325 entry is the only published record of what changed around it.[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#
- Claude Code Official Changelog, v2.1.325 release notes
Related Versions#
- Claude Code v2.1.323: Code Mode, hook heartbeats, background sign-in fixes
- Claude Code v2.1.321: Fable 5.2 default, MCP OAuth secret-leak fix, Bash permission fixes
- Claude Code v2.1.319: background MCP tasks, auto-denied permission prompts
- Claude Code v2.1.318: sign-in expiry warnings and an experimental Code Mode
Previous Claude Code analysis: v2.1.323 (November 12, 2026)
All 90 Claude Code analyses: Claude Code Version Tracker · Official Claude Code changelog