Anthropic · Claude
New in this edition · 37
- SettingClaude Code on the web
Remote settings queries restricted in cloud and self-hosted sessions
Settings, permission rules, hooks, and status queries may now return less information or be rejected over a cloud or self-hosted connection. The settings actually applied within the session are unchanged.
Usage details
Who can use it: Cloud and self-hosted runner sessions; enterprise security policies.
How to use it: Use the session’s own `/status`, settings, and permissions views; don’t assume you can read the entire configuration over a remote connection.
Tip: Write automations to tolerate incomplete remote responses.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - CapabilityClaude Code
Context overflow compaction fixed in Gateway and Foundry sessions
Fixed an issue that caused context length errors on every turn in many third-party gateway and Microsoft Foundry sessions. Sessions now continue compacting when appropriate.
Usage details
Who can use it: Claude Code sessions using third-party gateways and Microsoft Foundry.
How to use it: Update to 2.1.325; expect automatic compaction when the context fills up.
Tip: For long tasks, still manage context proactively with `/compact` or `/autocompact`.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - SettingClaude Code computer use
More risky key combinations blocked during macOS computer use
macOS computer use now rejects key combinations that hold Control or Option together with Space, as well as more system shortcuts that require permission.
Usage details
Who can use it: Sessions using Claude Code computer use on macOS.
How to use it: When a shortcut is rejected during a computer use request, ask the user to perform the required system action.
Tip: Design workflows that require explicit user consent instead of automating system shortcuts.
✓ Verified by official sourceSource: Claude Code v2.1.323 sürüm notları - APIClaude Code Mods
Mod model calls included in cost and usage metrics
`/cost`, `$.session.usage()`, `--max-budget-usd`, and cost/token metrics now also count mods’ `$.model.complete` and `$.model.classify` calls.
Usage details
Who can use it: Claude Code mods and sessions that track their budgets or usage.
How to use it: After a mod call, check the total with `/cost` or `$.session.usage()`; use `--max-budget-usd` for headless runs.
Tip: When evaluating mod costs, track their own model calls as a separate budget item.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - Plugin / IntegrationClaude Code plugins
Plugin skips unsafe paths and nested skill loading is restricted
The plugin loader now skips some unsafe paths and links, and `claude plugin validate` reports them. `.claude/skills` directories inside `--plugin-dir` are not automatically loaded in sessions started from a parent directory.
Usage details
Who can use it: Teams developing custom plugins, skills, and marketplaces.
How to use it: Run `claude plugin validate`; start a session from within the plugin, or explicitly move skills to an appropriate plugin location.
Tip: Distribute plugin packages using real, restricted paths instead of symbolic links.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - APIClaude Code Remote Control
Remote Control reports its own shutdown and registration failures with different exit codes
When `claude remote-control` stops on its own, it now exits with 4; when it fails to register, it exits with 69. The normal exit code of 0 is preserved for single-session runs.
Usage details
Who can use it: Teams running Remote Control with a service manager.
How to use it: Treat exit codes 4 and 69 in the service definition as restart or alert conditions.
Tip: When updating the supervisor configuration, continue to treat the single-session code 0 as success.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - CapabilityClaude Code
Session credentials isolated from sandbox helper processes
Programs launched by the sandbox itself, such as its network bridge, no longer carry Claude Code login tokens or API keys in their environment. Internal ripgrep, git, and helper processes also no longer receive the mTLS client key password.
Usage details
Who can use it: Enterprise setups using a sandbox, proxy, credential helper, or hook.
How to use it: Update to 2.1.325; explicitly provide any required credentials to the helper program using a secure secret mechanism.
Tip: Stop relying on Claude Code environment variables implicitly in credential helpers.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - CapabilityClaude Code
Security vulnerability fixed in Zstd response decompression
Claude Code fixed a security issue that occurred when processing zstd-compressed responses. The fix enables safer decompression of compressed server responses.
Usage details
Who can use it: Claude Code 2.1.325 and later; all platforms receiving compressed responses.
How to use it: Update Claude Code to version 2.1.325 or later; no separate setting is required.
Tip: Don’t delay updates on machines using enterprise setups or gateways.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - Plugin / IntegrationClaude Code MCP tasks
Background MCP questions can be answered later with Esc
Pressing Esc on a background MCP task question no longer sends an empty or incorrect answer to the server; the question remains in `/tasks` and can be answered later.
Usage details
Who can use it: Claude Code sessions using background MCP tasks.
How to use it: Press Esc while the question is displayed; later, open `/tasks`, press Enter to show the question again, and answer it.
Tip: To avoid accidentally answering an MCP question while writing a prompt, submit or clear your draft first.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - SettingClaude Code
Maximum overload retry delay raised to 300 seconds
The allowed maximum for `CLAUDE_CODE_OVERLOADED_RETRY_MAX_DELAY_MS` has increased from 64,000 to 300,000 milliseconds.
Usage details
Who can use it: Claude Code installations configured for automatic retries on overload errors.
How to use it: Set the environment variable to no more than `300000`; for example, `CLAUDE_CODE_OVERLOADED_RETRY_MAX_DELAY_MS=300000`.
Tip: Before setting a long delay on shared infrastructure, account for task timeouts and the CI budget.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - CapabilityClaude Code on the web
Cloud tool search MCP description limit increased to 16,384 characters
For MCP tool descriptions loaded using tool search in new cloud sessions, the truncation limit has increased from 4,096 to 16,384 characters.
Usage details
Who can use it: Claude Code on the web cloud sessions.
How to use it: Start a new cloud session and call the MCP tool using tool search; longer descriptions are now preserved.
Tip: Keep MCP tool descriptions concise and task-focused to improve search quality.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - AgentClaude Code
File and MCP sizing fixed for subagents using a different model
Subagents with their own model no longer incorrectly size file reads and MCP results using the main session’s model. A fix also prevents the subagent from being incorrectly switched to its planning model when using the `opusplan` or `haiku` setting.
Usage details
Who can use it: Claude Code subagents and sessions that use model switching.
How to use it: Explicitly assign a model to the subagent, then run a file or MCP operation; no additional settings are required.
Tip: Set the subagent’s model before the task starts to ensure the correct context budget for long results.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - SettingClaude Code
Consent required to change privacy settings during login
`/login` now asks users for consent before changing privacy settings. This prevents login from silently changing account privacy preferences.
Usage details
Who can use it: Claude Code 2.1.325 and later; accounts using `/login`.
How to use it: Run `/login` and explicitly approve or reject the change when prompted about privacy settings.
Tip: On corporate devices, compare the consent text with your administrator’s data policy.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - APIClaude Code CLI
First claude -p call waits for the account cache
When no account data is cached, `claude -p` no longer sends the first request immediately with the wrong identity; it waits until the account data is ready.
Usage details
Who can use it: `claude -p` sessions running in a clean environment or on a new CI worker.
How to use it: Run `claude -p` in a clean environment; account for the possibility that the first request may be delayed by a few seconds while credentials are prepared.
Tip: Set the CI timeout to allow for the initial authentication delay.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - FeatureClaude Code VS Code extension
Cell rerun tip added for Jupyter notebooks
After Claude reads or edits a Jupyter cell, a tip for rerunning the cell appears in VS Code and similar integrated terminals.
Usage details
Who can use it: Claude Code 2.1.325 and later; VS Code and similar integrated terminal surfaces.
How to use it: Have Claude read or edit a `.ipynb` file, then rerun the cell by following the relevant spinner tip.
Tip: To verify Claude’s output, rerun only the affected cells after making changes.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - CapabilityClaude Code
The path forward is made clear when an organization policy blocks a request
When an organization policy blocks a request, the error message now explains how to proceed: change the message with `/rewind` or run `/clear`.
Usage details
Who can use it: Claude Code sessions managed by organization policies.
How to use it: Follow the suggestion in the block message: run `/rewind` and narrow the prompt, or use `/clear` for new context.
Tip: Explicitly remove the risky part of the request instead of trying to bypass the policy block.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - Plugin / IntegrationClaude Code plugin marketplace
Marketplace ref field accepts a full commit ID on a branch or tag
Marketplace `ref` can now be pinned to any full commit ID on a branch or tag. There is a compatibility warning because clients older than this release cannot clone such a pin.
Usage details
Who can use it: Teams managing private plugin marketplaces; Claude Code 2.1.325 and later.
How to use it: Set the full commit SHA in the `ref` field of the marketplace definition and upgrade older Claude Code clients.
Tip: For enterprise deployments, pin marketplace refs to signed or verified commits.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - Plugin / IntegrationClaude Code plugins
MCP plugin bundles can be installed in read-only plugin directories
`.mcpb` and `.dxt` bundles are now extracted to the plugin directory instead of `.mcpb-cache` inside the plugin directory. This allows read-only plugin directories to be installed; packages fetched from a URL can be downloaded again on the first attempt.
Usage details
Who can use it: Plugin marketplace installations that use `.mcpb` or `.dxt`.
How to use it: Install the plugin with the latest Claude Code; you don’t need to grant write access to the read-only plugin directory.
Tip: Keep plugin directories read-only to reduce the risk of changes at runtime.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - CapabilityClaude Code
Approved plan saved to the default folder if the plan directory is unwritable
If the `plansDirectory` location is unwritable, the approved plan is no longer lost; it is saved to the default plan folder, and a warning indicates the reason and location.
Usage details
Who can use it: Claude Code sessions using `plansDirectory`.
How to use it: Approve the plan; if the custom folder is unwritable, check the default location shown.
Tip: In enterprise installations, verify in advance that the Claude Code process has write permission for `plansDirectory`.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - RetiredClaude Code plugin marketplace
The pluginDigests setting is deprecated
Remote marketplace plugins declared by managed settings are considered the organization’s plugins; the legacy `pluginDigests` field is now deprecated and ignored.
Usage details
Who can use it: Organizations that distribute plugin marketplaces through managed settings.
How to use it: Remove `pluginDigests` from managed settings; manage plugins with `prependPlugins` or `appendPlugins`.
Tip: For plugin version integrity, use a version range and a verified marketplace commit instead of a digest.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - CapabilityClaude Code
A note explains protected files during sandbox git operations
If `git checkout`, `git stash`, or an autostash pull inside the sandbox cannot update protected files such as `.claude`, Claude receives a note explaining why.
Usage details
Who can use it: Claude Code sessions using a sandbox.
How to use it: Read the operation note; for protected files, first provide appropriate permissions or a trusted workspace, then rerun the git operation.
Tip: Back up `.claude` settings before changing them with stash or checkout, and verify that the workspace is trusted.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - CapabilityClaude Code CLI
Shell commands no longer run in the wrong directory when the working directory is deleted
If the initial working directory is deleted, shell commands no longer silently run in the launch directory; they return a meaningful error and allow the command to be resubmitted.
Usage details
Who can use it: Claude Code CLI and sessions where the working directory may later be deleted.
How to use it: After the error, switch to a valid working directory and resubmit the command.
Tip: In scripts that delete temporary folders, don’t remove the working directory while a Claude Code session is running.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - CapabilityClaude Code CLI
Unwanted control sequences filtered from terminal text output
Terminal text output from `claude -p` no longer passes through control sequences other than formatting sequences. The behavior of pipe and file output has not changed.
Usage details
Who can use it: `claude -p` users who receive text output in the terminal.
How to use it: Run `claude -p` on the latest version; use pipe or file redirection for machine-processed output.
Tip: Route output through a pipe to keep CI logs safe and stable.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - APIClaude Code CLI
plugin eval now rejects an empty output directory
`claude plugin eval --output-dir ''` no longer silently writes the report to the current working directory; it exits with an error.
Usage details
Who can use it: Developers who run plugin evaluations through the CLI or CI.
How to use it: Provide an explicit, non-empty directory path for `--output-dir`.
Tip: In CI scripts, create the output directory before running the command and use an absolute path.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - SettingClaude Code
Unrecognized teammateMode values are no longer silently ignored
An invalid `teammateMode` setting is now reported as a skipped entry in the `claude -p` startup warning and `claude doctor` output, even though it is not applied.
Usage details
Who can use it: Claude Code setups using agent team settings.
How to use it: Check the `claude doctor` or `claude -p` output and replace the unrecognized `teammateMode` value with a valid one.
Tip: Run `claude doctor` in CI to validate managed settings files against version-compatible values.
✓ Verified by official sourceSource: Claude Code v2.1.325 sürüm notları - FeatureClaude Code Terminal.app
Option key behavior explained during Terminal.app setup
The first-run screen now explains what the “Use Option as Meta key” setting does, how Option affects typing, and how to undo the setting.
Usage details
Who can use it: Users launching Claude Code for the first time with macOS Terminal.app.
How to use it: Read the explanation on the setup screen and confirm your Option key preference.
Tip: Test your existing shortcuts before changing Option behavior on Turkish or special-character-heavy keyboards.
✓ Verified by official sourceSource: Claude Code v2.1.323 sürüm notları - FeatureClaude Code
The exhausted sticker pack no longer opens a misleading browser page
`/stickers` now says the pack is exhausted instead of opening a page in the browser when the sticker pack has been fully claimed.
Usage details
Who can use it: Claude Code users.
How to use it: Run `/stickers` in Claude Code; if the pack is exhausted, wait for the status shown.
Tip: Treat this message as a signal to wait for a new distribution, not as an error.
✓ Verified by official sourceSource: Claude Code v2.1.323 sürüm notları - SettingClaude Code
Variable for disabling subagent progress summaries documented
The `CLAUDE_CODE_DISABLE_AGENT_PROGRESS_SUMMARIES=1` setting disables subagent progress summaries and the requests made to generate them.
Usage details
Who can use it: Available since Claude Code 2.1.318, formalized in the 2.1.323 notes; headless and interactive sessions.
How to use it: Set `export CLAUDE_CODE_DISABLE_AGENT_PROGRESS_SUMMARIES=1` before launching Claude Code.
Tip: Disable it if quota or reducing noise is a priority; leave it enabled if you need visible progress on long tasks.
✓ Verified by official sourceSource: Claude Code v2.1.323 sürüm notları - SettingClaude Code
Startup warning added for variable wildcards in Bash permission rules
A startup warning is displayed for Bash permission rules that use `*` in a variable value; `Bash(PORT=* npm run dev)` is given as an example.
Usage details
Who can use it: Claude Code 2.1.323 and later; all installations using Bash permission rules.
How to use it: Restart Claude Code and check the startup warning; if needed, replace the rule with a narrower pattern.
Tip: Explicitly restrict commands and parameters instead of allowing variables with wildcards.
✓ Verified by official sourceSource: Claude Code v2.1.323 sürüm notları - APIClaude Code CLI
Plugin install JSON output now includes the number of unset configuration options
The `claude plugin install --json` output now reports the number of `userConfig` options that have not yet been set in the `unsetOptionCount` field.
Usage details
Who can use it: CLI and CI workflows that automate plugin installation.
How to use it: Run `claude plugin install --json <plugin>` and read the `unsetOptionCount` field.
Tip: If this value is not zero after installation, ask the user to complete the missing plugin settings.
✓ Verified by official sourceSource: Claude Code v2.1.323 sürüm notları - APIClaude Code CLI
Customize the exit resume hint with a custom command
Programs that launch Claude Code can now use `CLAUDE_CODE_RESUME_HINT_COMMAND` to show their own resume command in the exit hint.
Usage details
Who can use it: Developers who launch Claude Code with another tool or wrapper program.
How to use it: Set the `CLAUDE_CODE_RESUME_HINT_COMMAND` variable in the launcher environment to your own resume command.
Tip: Generate the full command users can copy and run, including any required project or session ID.
✓ Verified by official sourceSource: Claude Code v2.1.323 sürüm notları - FeatureClaude Code
Close hint and new shortcut guide added to diff panel
The diff panel now shows the `/diff to close` hint. The keys for opening and closing the panel are also listed in the `?` shortcut guide.
Usage details
Who can use it: Claude Code 2.1.323 and later; terminal users.
How to use it: Run `/diff` while a file is changed; open the `?` guide to see the shortcuts.
Tip: Keep the diff panel open and review changes quickly before accepting large changes.
✓ Verified by official sourceSource: Claude Code v2.1.323 sürüm notları - APIClaude Code Mods
Mod panels now include an isPromptCovered indicator
The mod panel’s drawing props now include the `isPromptCovered` field. Mods can detect when a dialog or the area above it covers the prompt.
Usage details
Who can use it: Claude Code mod developers.
How to use it: Read `isPromptCovered` from the mod panel’s drawing props to adjust the position or visibility of panel content.
Tip: Improve accessibility by keeping keyboard focus out of the panel when the prompt is covered.
✓ Verified by official sourceSource: Claude Code v2.1.323 sürüm notları - SettingClaude Code
Startup notice names the Perforce setting when it is not enabled
When Perforce settings are detected but the mode is off, Claude Code displays a one-time warning naming the `CLAUDE_CODE_PERFORCE_MODE` variable.
Usage details
Who can use it: Claude Code installations that use Perforce.
How to use it: Start Claude Code in an environment with Perforce settings; configure the `CLAUDE_CODE_PERFORCE_MODE` variable if needed.
Tip: In team environments, enable Perforce mode consistently with managed settings or leave it explicitly disabled.
✓ Verified by official sourceSource: Claude Code v2.1.323 sürüm notları - Plugin / IntegrationClaude Code
An informative warning appears when a plugin language server fails to start
If a plugin’s language server cannot start, Claude Code now displays a warning identifying the server and what to check.
Usage details
Who can use it: Installations that use Claude Code plugins.
How to use it: After installing a plugin, check the startup output or the result of `claude plugin list`; address the server and configuration mentioned in the warning.
Tip: Pin language server dependencies to the versions specified in the plugin documentation.
✓ Verified by official sourceSource: Claude Code v2.1.323 sürüm notları