Anthropic · Claude
New in this edition · 36
- FeatureClaude Code
`/code-review` reviews against the default target branch and verifies the PR diff
For most models, `/code-review` without a specified target reviews the current branch against the default branch. When given a PR number with `--fix` or a PR URL, it stops if `gh pr diff` fails or is rejected rather than performing an incorrect review.
Usage details
Who can use it: Claude Code 2.1.329; most models and repositories with GitHub CLI access.
How to use it: Use `/code-review` for a branch review; for a PR, use `/code-review <pr-number> --fix` or a PR URL.
Tip: Before reviewing a PR, test that `gh pr diff` works with the same credentials.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - FeatureClaude Code
`/tasks` now brings together scheduled jobs, `/loop` wakeups, and forks
The `/tasks` view also lists the current session's scheduled tasks, `/loop` wakeups, their targets, and conversation forks. Pressing `x` to stop an item now prompts for confirmation first.
Usage details
Who can use it: Sessions using Claude Code 2.1.329.
How to use it: Type `/tasks` in Claude Code; select the item you want to stop, press `x`, then choose the confirmation option.
Tip: Use this view as a single checkpoint instead of checking background job statuses separately.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - AgentClaude Code
Subagent stopping, wake-ups, and model/effort handoff are more consistent
Fixed stopped background agents restarting during resume, and completed subagents inheriting their sibling's model/effort settings. Tasks completed in the background are reported to the main conversation more accurately; the Agent tool's issue ignoring the `effort` parameter for named teammates was also fixed.
Usage details
Who can use it: Claude Code 2.1.329; background agents and agent teams.
How to use it: Run a background agent or agent team and use the stop/resume flow; check the completion notification in the main conversation.
Tip: Set the model and effort values explicitly for named teammates.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - AvailabilityClaude Code
Settings persistence and macOS session continuity fixed for network lockups
An unreadable `~/.claude.json` during a network outage or file lock is no longer reset to defaults. On macOS, if Keychain cannot be read or written, the relevant session now reports the issue until it expires and prevents other sessions from signing out unnecessarily.
Usage details
Who can use it: Claude Code 2.1.329; settings file on all platforms, Keychain on macOS.
How to use it: Update to this version and use settings and session operations as usual; if the issue persists, check `~/.claude.json` and Keychain permissions.
Tip: Avoid having tools that update the settings file conflict with Claude Code over file locks.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - CapabilityClaude Code
Code Mode hook, memory, and script constraints are clearer
In Code Mode, a failing PreToolUse hook no longer rejects the script tool by default; `onFailure: "block"` is required to reject it. Line ranges over 256 MiB are rejected, Code Mode can start when telemetry or feature flags are disabled, and scripts can use their own `log`, `preview`, or `sleep` definitions.
Usage details
Who can use it: Claude Code 2.1.329; Code Mode and command/HTTP/MCP hooks.
How to use it: To stop the operation, add `onFailure: "block"` to the relevant hook configuration; start Code Mode as usual.
Tip: Split large file reads into chunks to reduce the risk of hitting the memory limit.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - CapabilityClaude Code
Code Mode can start even when OpenTelemetry is enabled
Code Mode can now be used with OpenTelemetry events and metrics enabled. It sends events for tool calls made by Code Mode; tracing remains disabled.
Usage details
Who can use it: Claude Code 2.1.329; setups using OpenTelemetry events and metrics.
How to use it: Leave your OpenTelemetry events and metrics settings enabled and start Code Mode using your existing activation method.
Tip: Check event volume and your sensitive data policy before monitoring in production.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code gateway
Gateway visibly warns on every startup when `allow_cidrs` is empty
The startup warning shown when `access_control.allow_cidrs` is empty is now repeated at every startup as a boxed notice in text logs. The notice explicitly warns against exposing the gateway to the public internet.
Usage details
Who can use it: Claude Code deployments using Gateway.
How to use it: Check `access_control.allow_cidrs` in the Gateway configuration; define the permitted CIDR ranges and restart.
Tip: Define your organization's CIDR ranges before exposing the Gateway to the internet in production.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Permission, sandbox, and auto mode edge cases are handled more safely
Auto mode no longer asks for unnecessary manual approval when deleting a symlink outside the workspace or one that points to itself; Linux `/sandbox` also clarifies that `allowUnixSockets` entries do not actually open sockets. False record errors caused by unreadable local settings files when adding permission rules have also been fixed.
Usage details
Who can use it: Claude Code 2.1.329; auto mode, Linux sandbox, and permission settings.
How to use it: Inspect the active boundaries with `/sandbox`, and check the `/status` or `/config` message when adding a permission rule.
Tip: Verify the target path before trusting auto mode with destructive operations such as deleting symlinks.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
macOS computer use applies stricter safety rules and a 30-second launch timeout
macOS computer use has adopted new safety rules that reject certain actions and limit access to some apps. An app launch that does not complete is abandoned after 30 seconds.
Usage details
Who can use it: Claude Code 2.1.329; macOS computer use.
How to use it: Sign in to a session using computer use on macOS; follow the safety message shown when an action is rejected or an app takes too long to launch.
Tip: For apps that take a long time to launch, manually confirm the app is ready before retrying the task.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - Plugin / IntegrationClaude Code
MCP authentication, reconnection, and file types are more robust
Cleared MCP authentication no longer returns through an ongoing token refresh, and HTTP servers with slow reconnections are retried. PDF, image, DOCX, XLSX, and PPTX files sent as octet-stream by MCP or websites are no longer mistakenly saved as `.bin`.
Usage details
Who can use it: Claude Code 2.1.329; MCP servers and web tools.
How to use it: Clear the server’s authentication in `/mcp` and reconnect; try sending a file as usual.
Tip: Wait for the `/mcp` status message while the server reconnects instead of repeatedly starting the login flow.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - AvailabilityClaude Code self-hosted runner
Self-hosted runner handles LFS, SSH aliases, and remote MCP startup more reliably
Git LFS repositories can start with pointer files and fetch content with `git lfs pull`. Startup instructions have been improved for remote repositories using an SSH host alias, GitHub SSH certificate, or GHE.com user; remote MCP and runner startup status are also reported more accurately after a timeout.
Usage details
Who can use it: Claude Code self-hosted runner and repositories using Anthropic-managed git.
How to use it: Update the runner; in an LFS repository, run `git lfs pull` after the session starts and follow the suggested commands for SSH errors.
Tip: In runner health checks, verify the checkout and MCP tool list in addition to the HTTP response.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - Pricing / PlanClaude Code
Usage credits and spending screens show the actual status
The prompt to sign in again after following the usage credits link for Pro and Max users has been fixed. `/usage` and `/model` distinguish between credits being disabled, depleted, or at the monthly limit; the spend limit menu also no longer shows a changed limit if the server rejects it.
Usage details
Who can use it: Claude Code 2.1.329; Pro and Max users, and models using usage credits.
How to use it: Open `/usage-credits`, `/usage`, or `/model`; check the limit status and the server confirmation in the spend limit menu.
Tip: After opening the credits link, don't change models without checking the actual limit.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - AvailabilityClaude Code
Previously scheduled tasks must be rescheduled in newly logged-in sessions
Most tasks saved by previous versions must be rescheduled in a newly logged-in session. Resuming the same session with `--resume` keeps those tasks running; Exit and stop tasks stops them on the next resume.
Usage details
Who can use it: Claude Code 2.1.329; logged-in sessions using scheduled tasks.
How to use it: Reschedule the old task in `/tasks` in the new session; use Exit and stop tasks to stop it.
Tip: Record the schedules of critical tasks separately before upgrading.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - APIClaude Code self-hosted runner
`--repository-folder` rejects repository conflicts on a capacity-1 runner
A self-hosted runner running with `--capacity 1` can use most folders in the base folder with `--repository-folder`. Startup is rejected if another repository session conflicts in the same folder.
Usage details
Who can use it: Claude Code self-hosted runner; `--capacity 1`.
How to use it: Start the orchestrator with `--repository-folder <folder>` and don't send a second concurrent repository session to the same folder.
Tip: Use fixed, unique folder names for each repository in single-capacity runner pools.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code
`/mcp` shows the remote server’s JSON-RPC error message
A new Server message row has been added to the server page for remote HTTP MCP servers that reject the connection. The row displays the JSON-RPC error message returned by the server directly.
Usage details
Who can use it: Claude Code 2.1.329 and remote HTTP MCP servers.
How to use it: Open `/mcp`, select the relevant remote server, and read the error in the Server message row.
Tip: Fix the method or authentication issue indicated in this message instead of relying on the generic connection error.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - CapabilityClaude Code
Selecting a session with `/teleport` no longer overwrites the open conversation
When a cloud session is selected through `/teleport`, a new session starts without replacing the open conversation. The previous conversation can be restored with `/resume`.
Usage details
Who can use it: Claude Code 2.1.329 and cloud sessions.
How to use it: Type `/teleport` and select a cloud session; use `/resume` to restore the current conversation.
Tip: To preserve important local context, use this new-session behavior instead of closing the conversation before teleporting.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - APIClaude Code
Automatic limit retry for `max_tokens` errors removed
The automatic retry behavior added in 2.1.326, which retries using the limit specified in a `max_tokens` error, has been removed. If a gateway model supports a lower output limit, Claude Code no longer retries automatically with that value.
Usage details
Who can use it: Claude Code 2.1.329; gateway or custom model endpoints.
How to use it: Find out the actual output limit of your gateway model and, if needed, set `CLAUDE_CODE_MAX_OUTPUT_TOKENS` to that limit.
Tip: For gateways, explicitly specify model limits lower than the Anthropic default in your deployment configuration.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Auto mode runs `git status` less often in large repositories
In large repositories, Auto mode runs `git status` less often to avoid delaying most requests. Changes that delete the working tree may be blocked until the working tree is checked.
Usage details
Who can use it: Claude Code 2.1.329 and large Git repositories using Auto mode.
How to use it: Use Auto mode as usual; if a deletion is blocked, check the working tree status and approve again.
Tip: Treat this behavior as a safety check to prevent loss of changes, not as a delay.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Some teammate panels now start with `/bin/sh`
Some teammate panels start through `/bin/sh` instead of Bash or the user's interactive shell. As a result, shell startup files may not be read by every teammate process.
Usage details
Who can use it: Claude Code 2.1.329 and teammate panels.
How to use it: Explicitly set the environment variables required by the teammate in its working environment rather than relying on a startup file.
Tip: For tasks that depend on PATH or aliases, verify the teammate shell with a small diagnostic command.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - SettingClaude Code
The trust prompt shows where folder hooks are defined
The dialog shown when folder trust is requested now also identifies the source of hook definitions. This lets you see which settings file will run before you approve.
Usage details
Who can use it: Claude Code 2.1.329 and local sessions using the trust dialog.
How to use it: Open a project folder in Claude Code; review the hook definition line in the trust dialog.
Tip: Before granting trust, compare the hook path with the settings file you expect in the repository.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - AvailabilityClaude Code
macOS login refresh checks Keychain write access
Login refresh on macOS now checks write access using a Keychain item named `Claude Code-write-check`. This is intended to reduce repeated logouts when Keychain cannot be read or written.
Usage details
Who can use it: Claude Code 2.1.329; macOS.
How to use it: No settings changes are needed; use login refresh as usual after updating Claude Code.
Tip: If the issue persists, check Claude Code’s write permission and lock status in Keychain.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code
Plugin and Claude Docs connector connections recover more reliably
An uninstalled plugin's MCP server no longer remains connected in a headless session. A bug that caused Claude Docs connector tools to disappear when a plugin or MCP server at the same address failed—and incorrectly suggested `/login` as a fix—has been corrected.
Usage details
Who can use it: Claude Code 2.1.329; headless sessions, plugins, and Claude Docs connector.
How to use it: After updating the plugin list, run `/reload_plugins` or start a new session; check for Claude Docs tools in `/mcp`.
Tip: Troubleshoot conflicts by disabling plugins and connectors that use the same address one at a time.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - AvailabilityClaude Code self-hosted runner
Self-hosted runner keeps clones from multiple hosts in separate paths
A second host copy with the same owner/repository name is now stored under `_repos/clones/<host>/`. Repositories with unusual characters in their address paths are also cloned into the new folder; rules and volumes tied to the old folder are not applied to the new clone.
Usage details
Who can use it: Claude Code self-hosted runner.
How to use it: Update the runner and check the relevant repository clone paths under `_repos/clones/<host>/`.
Tip: Move rule and volume definitions to the new clone path for each host.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - SettingClaude Code self-hosted runner
Self-hosted runner reports ignored default permission mode at startup
Claude Code 2.1.328 added a warning at self-hosted runner startup that sessions ignore the default permission mode in the host's `settings.json`. This makes the difference between the administrator setting and actual session behavior visible.
Usage details
Who can use it: Claude Code self-hosted runner.
How to use it: Start the runner and read the permission mode warning in the startup logs; define the active mode in managed settings.
Tip: Verify the settings the runner actually applies in a test session instead of relying on the host setting.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code
Team sharing and passes screens now reflect server results accurately
If the server rejects a guide upload, `/team-onboarding` no longer shows the guide as shared. After a server error, `/passes` also no longer shows an incorrect pass count or the usage credits option when no guest passes remain.
Usage details
Who can use it: Claude Code 2.1.329; Team and Enterprise onboarding and passes flows.
How to use it: Reopen `/team-onboarding` or `/passes`; compare the result with the server's confirmation.
Tip: If sharing fails, check the organization's upload permissions before resending the invitation.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - CapabilityClaude Code
Terminal setup and IDE diff saves preserve file integrity
`/terminal-setup` no longer breaks VS Code settings around comment blocks or loses the Shift+Enter binding when a string is missing. Accepting an IDE diff also preserves the file's final newline and BOM.
Usage details
Who can use it: Claude Code 2.1.329; developers using VS Code and terminal setup.
How to use it: Run `/terminal-setup` and save an IDE diff with Accept; check the settings and the end of the file.
Tip: For encoding- or BOM-sensitive files, verify the file's final bytes in CI after Accept.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - CapabilityClaude Code
Visibility fixed in terminal panels and accessibility flows
Panels, questions, and rows that were cut off in short windows have been fixed in Fullscreen, `/help`, history search, and the background task list. Resumed sessions also no longer incorrectly show truncated edits, questions, and plans as Rejected or Declined.
Usage details
Who can use it: Claude Code 2.1.329; terminal interface and accessibility users.
How to use it: Open `/tasks`, `/help`, or `/resume` in a short terminal window and check that the lists are complete and focus works.
Tip: If lines are cut off when you narrow the terminal, enlarge the window; don't assume an unseen prompt was confirmed.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - CapabilityClaude Code
Long sessions, Windows startup, and cloud plugin loading are faster
Memory usage in long sessions with many files and startup/first search on Windows have been improved. Cloud sessions retry plugins that could not be downloaded at startup; Desktop Remote Control becomes ready faster after a response.
Usage details
Who can use it: Claude Code 2.1.329; Windows, Claude Desktop, and cloud sessions.
How to use it: Update Claude Code; restart the cloud session and wait for the plugin to be retried automatically at the next startup.
Tip: After an initial plugin download issue, wait for the next automatic retry instead of repeatedly restarting.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - CapabilityClaude Code for VS Code
Button and reason visibility fixed in long VS Code permission prompts
In Claude Code 2.1.328, clipping of the No button, response field, and title in short panels or with long commands, URLs, and descriptions was fixed. Reasons no longer disappear or get cut off midway in blocked or failed tool calls.
Usage details
Who can use it: Claude Code for VS Code.
How to use it: Open a permission prompt containing a long command or URL; if the reason is not visible, enlarge the panel and use the latest extension.
Tip: Make sure you can see the entire reason instead of responding to permission prompts in a narrow panel.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
An explicit warning appears in the conversation if a managed hook fails to load
When hooks in Managed settings fail to load, Claude Code reports this in the conversation, in Claude Desktop, and in other non-interactive hosts. Instead of failing silently, it displays an error that an administrator can address.
Usage details
Who can use it: Claude Code 2.1.329; Claude Desktop and non-interactive Claude Code hosts.
How to use it: Start a session that uses managed settings; if loading fails, check the warning in the conversation stream.
Tip: When you see the warning, check your organization’s managed settings deployment first rather than changing local settings.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
zsh command parsing, compaction, and terminal streaming are more robust
In Claude Code 2.1.328, zsh words beginning with `=` no longer incorrectly trigger command path expansion. Automatic compaction no longer incorrectly reuses the previous system prompt; issues with long or malformed Markdown, rare screen freezes, paste handling, and lost Esc input were also fixed.
Usage details
Who can use it: Claude Code 2.1.328; zsh and long terminal sessions.
How to use it: Update Claude Code and rerun commands such as `echo ====` in zsh; use compaction as usual in long sessions.
Tip: If the terminal connection is slow, check that the pasted command actually appears in the prompt before running it.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code
`/status` explains why managed marketplaces are not updated automatically
A Marketplace auto-update line has been added to `/status`. It names managed marketplaces that do not receive automatic updates and explains why.
Usage details
Who can use it: Claude Code 2.1.329 and installations using managed marketplaces.
How to use it: Run the `/status` command; inspect the Marketplace auto-update line.
Tip: Check the stated reason for the update restriction with your administrator.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - CapabilityClaude Code
The task counter shows all background jobs in one total
The `/tasks` header and footer now count all shells, monitors, MCP calls, agents, workflows, and scheduled jobs in a single total. In Stop and SubagentStop hooks, Monitor scripts are identified as `monitor`.
Usage details
Who can use it: Claude Code 2.1.329.
How to use it: Run multiple background jobs and check the total in the `/tasks` header; look for the `monitor` label in hook logs.
Tip: Remember that the total is not just the number of agents; shell and MCP jobs are included too.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - AvailabilityClaude Code
Remote Control titles and rename/diff views are fixed
In `claude remote-control` sessions, `/rename` and UserPromptSubmit hook titles are now visible on claude.ai and mobile. Remote Control diffs no longer list renamed and edited files twice.
Usage details
Who can use it: Claude Code Remote Control, claude.ai, and mobile clients.
How to use it: Use `/rename` in a Remote Control session and check the title on claude.ai or mobile; open the diff for a renamed file.
Tip: Don't evaluate files containing both renames and edits solely by their total line count.
✓ Verified by official sourceSource: Claude Code v2.1.329 sürüm notları - AvailabilityClaude Code for VS Code
VS Code shows a Review trust link to reopen a rejected trust prompt
After you reject a trust prompt in VS Code, a Review trust line appears above the message box. You can reopen the trust prompt without reloading the window.
Usage details
Who can use it: VS Code change documented in Claude Code 2.1.329.
How to use it: Choose to reject the trust prompt, then click the Review trust link above the chat input.
Tip: Use this link to grant repository trust later instead of opening a new window.
✓ Verified by official sourceSource: Claude Code changelog