Anthropic · Claude
New in this edition · 48
- APIClaude Code
Slash command permissions and feedback uploads are restricted for background agents
A slash command’s `allowed-tools` permission is no longer accidentally applied to background agents woken during or after its turn. `/feedback` and `/bug` can now upload only sessions recorded by the signed-in account or organization.
Usage details
Who can use it: Claude Code 2.1.325; background agents, `/feedback`, and `/bug` flows.
How to use it: If you start a background agent in a slash command, define each agent’s permissions separately; when submitting feedback, verify that the session was recorded under the same account or organization.
Tip: On shared devices, check the upload preview before submitting a bug report; sessions belonging to another account are now blocked from being uploaded, but it is still best to keep the scope narrow.
✓ Verified by official sourceSource: Claude Code changelog - Pricing / PlanClaude Code
Background sessions are not billed to the wrong account or shell key
Background sessions started with a claude.ai login can no longer use or bill the API key or token in the launching shell. Switching to another account in the background is rejected, the system explains what will run if no suitable credentials are available, and a second Enter in the exit prompt no longer accidentally stops the background task.
Usage details
Who can use it: Claude Code 2.1.325; background session, claude.ai login, and named profile flows.
How to use it: Check the correct profile with `claude auth status` before starting a background session; if you need to switch identities, stop the session and explicitly log in again.
Tip: For cost tracking, keep environment keys clean in the shell that starts the background service, and verify the organization billed for the session each time you start a new service.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Bash deny, ask, and allow checks are stricter for compound commands
Fixes address some Bash commands bypassing deny/ask rules, compound commands running without approval, and allow rules running a different program from the one they specify. Commands using broad shell options and wrappers now request permission more consistently.
Usage details
Who can use it: Claude Code 2.1.325; Bash permission rules and shell wrappers.
How to use it: Test rules with examples containing `sudo`, `env`, compound commands, and wildcards; if no permission prompt appears, inspect the command’s actual program instead of broadening the allow/deny list.
Tip: Keep allow rules as narrow as possible, such as `Bash(program:*)`, and do not ignore startup warnings about variable wildcards.
✓ Verified by official sourceSource: Claude Code changelog - APIClaude Code
Bedrock provider restriction and credentials without HOME are fixed
If `allowedProviders` does not permit Bedrock, token counting no longer sends the conversation to Bedrock. AWS `credential_process` and Google Cloud default credentials also work at startup when the `HOME` environment variable is absent.
Usage details
Who can use it: Claude Code 2.1.325; Amazon Bedrock, Google Cloud, and service environments without HOME.
How to use it: Check the `allowedProviders` value in managed settings; when starting a service account, make AWS credential helpers or Google Cloud credentials accessible without depending on HOME.
Tip: In CI, run a smoke test for the provider allowlist and a separate test of credential helpers without HOME.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code
Cloud connector approvals are no longer answered automatically while plugins load
In cloud sessions, connector tool approval prompts are no longer answered automatically while plugins are still loading. Users can now see the actual connector and permission context after plugin loading finishes before making a decision.
Usage details
Who can use it: Claude Code 2.1.325; cloud sessions and connector tools that provide plugins.
How to use it: If a prompt appears during a connector call, wait for the plugin loading indicator to finish, then check the displayed connector name and action before approving.
Tip: Instead of calling plugins too early, use a health check at session startup to verify that loading is complete.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Sandbox cannot write to `.claude` settings and hooks in added directories
As in the launch directory, the sandbox now rejects writes to `.claude` settings, skills, agents, commands, and hooks in added directories. This prevents a directory opened with `--add-dir` from silently changing session settings.
Usage details
Who can use it: Claude Code 2.1.325; macOS, Linux, and WSL sandbox sessions.
How to use it: Add the extra directory with `--add-dir` and read its `.claude` contents if needed; if changes are required, make them in a trusted workflow outside the sandbox and with explicit approval.
Tip: In shared repositories, put `.claude` changes through a separate review step; this is safer than granting write access across the entire working tree.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Account email is more strictly protected as a command and tool identity
Account email checks now also reject its use as a client identity in commands run by scripts, file writes, web fetch operations, and MCP calls. This prevents the account’s email address from accidentally leaking into another tool’s identity field.
Usage details
Who can use it: Claude Code 2.1.325; script, file, WebFetch, and MCP calls.
How to use it: Do not use your account email as a command argument or tool identity; define a separate, purpose-specific service identity for automations.
Tip: In automations, replace your personal account email as a fixed identity with a short-lived service identity that has the fewest possible permissions.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Permission rules behave consistently across folders, plugins, and restarts
After `cd`, relative deny/ask rules retain their scope in projects and added directories; differences in letter case in plugin MCP names no longer cause a rule to be missed. Deny rules are applied to approvals received after a restart, and `settings.local.json` committed in some subfolders is no longer mistakenly treated as a user setting.
Usage details
Who can use it: Claude Code 2.1.325; Bash, MCP plugin, self-hosted runner, and Remote Control sessions.
How to use it: Specify an explicit path scope in permission rules and test `/permissions` behavior after a restart; use the same letter case as the actual server name in the manifest for plugin MCP names.
Tip: Test relative rules such as `Read(./.env)` with added directories and worktrees; don’t assume they work only at the project root for security.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code
Plugin marketplace network connections and installation warnings are more secure
When `ALL_PROXY` is used as the only proxy, plugin marketplace and plugin downloads now work through a CONNECT tunnel; if CONNECT is rejected, the operation fails explicitly. HTTPS authentication errors for private marketplaces explain that terminal prompts are disabled, and plugin installation warnings state that plugins can run code on the computer and access files and the shell.
Usage details
Who can use it: Claude Code 2.1.325; private plugin marketplaces and plugin installation.
How to use it: If you use a proxy, define `HTTPS_PROXY` and add the marketplace again; review the manifest and source code before approving the code execution warning shown during plugin installation.
Tip: For private marketplaces, use only a trusted Git source and an explicit `HTTPS_PROXY`; don’t mistake silent stderr output for a successful installation.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Bash commands inside the sandbox use the normal permission flow by default
Even when the sandbox is enabled, Bash commands now go through the normal permission check by default, removing the assumption that commands will run automatically. The same behavior applies to managed settings, and `sandbox.autoAllowBashIfSandboxed` must be explicitly set to true to restore the previous automatic flow.
Usage details
Who can use it: Claude Code 2.1.325; terminal, Desktop, IDE, and managed sessions that use the sandbox.
How to use it: If you intentionally want to keep running commands without permission prompts, define `sandbox.autoAllowBashIfSandboxed: true` in the highest-priority settings source; otherwise, approve commands as usual.
Tip: In enterprise environments, audit write and external network rules separately before enabling this setting; the sandbox alone does not replace user approval.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
The sandbox can no longer write to updater and worktree settings files by mistake
Sandboxed commands are now prevented from writing to the native updater download directory. Gaps in sandbox protection for worktree settings and hooks files, and for the linked worktree’s shared Git directory, have been closed.
Usage details
Who can use it: Claude Code 2.1.325; macOS/Linux/WSL sessions using the sandbox, worktrees, and linked worktrees.
How to use it: Rerun updater and worktree operations on the latest version; if a write is denied, explicitly define the actual target path and the sandbox allowRead/allowWrite scope.
Tip: When using a linked worktree, review the shared `.git` path as a separate security boundary; its presence under the project doesn’t make it safe.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
New security checks for worktree and self-hosted working paths
Isolated worktree sessions reject `git bisect run`, `git maintenance register|start`, and Scalar installation commands, and explain the supported approach. Symlink hook paths in `EnterWorktree`, `.git` folders containing symlinks or hard links, and symlinked session/repository paths on self-hosted runners are now blocked as well.
Usage details
Who can use it: Claude Code 2.1.325; worktree, plugin hooks, self-hosted runners, and isolated sandbox flows.
How to use it: Print the real path instead of using a symlink in a worktree hook; use a plain clone and avoid link- or hard-link-based layouts for `.git`. Run unsupported maintenance commands in the main trusted repository, outside the isolated session.
Tip: Verifying self-hosted runner paths with `realpath` before starting catches paths that the new version will reject.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code
Managed plugin and skill restrictions now apply to sessions already in progress
A bug that made the managed `strictPluginOnlyCustomization` restriction ineffective for agents and skills has been fixed. Even if the setting is applied after a session starts, the active session now enforces the organization’s rule allowing only approved plugin customization.
Usage details
Who can use it: Claude Code 2.1.325; organization sessions using managed settings, agents, and skills.
How to use it: Set `strictPluginOnlyCustomization` in the managed settings.json and recheck plugin/skill behavior in an active session.
Tip: After changing an enterprise setting, test existing sessions too; checking only when a new session starts isn’t enough.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Explicit permission is required to run skills with hooks in scheduled tasks
Scheduled tasks and `/loop` no longer run skills that declare `allowed-tools` or hooks without user approval. To run a skill truly unattended, you must add `Skill(name)` to `permissions.allow`; the Always allow option in Desktop, IDE, and SDK is offered only if the persistent rule will allow the task to run again.
Usage details
Who can use it: Claude Code 2.1.325; scheduled tasks, `/loop`, Desktop, IDE, and SDK hosts.
How to use it: Add `Skill(skill-name)` for the relevant skill to the `permissions.allow` section of your settings file, or approve the permission prompt when the task runs.
Tip: In scheduled tasks, add only genuinely trusted skills to the allowlist by name; a broad automatic permission rule could run unexpected code.
✓ Verified by official sourceSource: Claude Code changelog - APIClaude Code
`claude purge` is more reliable without a terminal and with piped stdin
`claude purge` no longer hangs silently when there’s no terminal to read from. The project picker and `-i` prompts also no longer ignore keyboard input when it arrives through an stdin pipe.
Usage details
Who can use it: Claude Code 2.1.325; headless and piped CLI runs.
How to use it: For headless use, provide a TTY if interactive selection is required before running `claude purge`; explicitly route input for `-i` prompts in a piped stream.
Tip: In CI, use a predetermined project scope instead of an interactive purge; remember that deletion is irreversible when automating deletion commands through a pipe.
✓ Verified by official sourceSource: Claude Code changelog - APIClaude Code
Subagent approvals, Agent SDK settings, and completed PR status are more accurate
The main session is no longer reverted to its previous permission mode after a subagent’s plan is approved. In Agent SDK `applyFlagSettings()`, a single invalid value now produces an error instead of silently deleting previous settings; a completed pull request no longer makes the session appear to be unnecessarily waiting for input if it is only awaiting user review or a merge.
Usage details
Who can use it: Claude Code 2.1.325; Agent SDK, subagent plans, and pull request sessions.
How to use it: Validate `applyFlagSettings()` calls in the SDK with valid values individually; after plan approval, check the active permission mode and what step the PR is actually waiting for.
Tip: Adding cases for a single invalid field and a completed PR to SDK integration tests catches silent state changes.
✓ Verified by official sourceSource: Claude Code changelog - AgentClaude Code
Subagent model selection and truncated output behavior fixed
Subagents using their own model are no longer switched to the wrong model by `opusplan` or `haiku` plan mode. When a subagent’s output is cut off at the token limit, it is now asked to produce a shorter, complete response instead of returning only the final fragment.
Usage details
Who can use it: Claude Code 2.1.325; subagents and sessions using the `opusplan` or `haiku` model setting.
How to use it: Specify the desired `model` explicitly in the subagent definition. For tasks approaching the output limit, allow the subagent to produce a second, shorter response.
Tip: Break long tasks into subagent assignments to reduce both the risk of truncated output and the cost of retries.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code
Background MCP tasks keep updating after connection loss
Fixed an issue where background MCP tasks stopped updating when a later reconnection followed a connection loss caused by another call to the same server. A pending task question no longer appears over a message while the user is still typing; it waits until the draft is sent or cleared.
Usage details
Who can use it: Claude Code 2.1.325; background MCP tasks and terminal/host sessions running while a user draft is open.
How to use it: Monitor the background MCP task from the `/tasks` screen; if you’re typing a draft, send or clear it first, then answer the question that appears.
Tip: When a connection drops, waiting a few seconds and checking `/tasks` instead of canceling the task may preserve the result of the reconnected job.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude for Teachers
Free access to Claude for Teachers extended through July 30, 2028
Anthropic extended free access to its Claude for Teachers program for verified U.S. K-12 educators through July 30, 2028. The program continues to offer premium Claude capabilities, a Learning Commons connection, and teaching skills.
Usage details
Who can use it: Verified K-12 educators in the U.S.; Claude for Teachers individual teacher offer.
How to use it: Go to Anthropic's Claude for Teachers page and verify your teacher account; once verified, use the free program access.
Tip: Check school and district policies before using student data; Anthropic's page states that authorization is required for identifiable student data.
✓ Verified by official sourceSource: Introducing Claude for Teachers - FeatureClaude Code
Code Mode worktree, approval, and resume flows are more controlled
Code Mode scripts now correctly preserve the worktree selected with `EnterWorktree`, path resolution, and MCP session state. A bug that prevented the Yes text entered in the approval dialog from reaching Claude has been fixed; when a session that ends during a script is resumed, Claude no longer starts working on its own without a new prompt.
Usage details
Who can use it: Claude Code 2.1.325; experimental Code Mode and sessions using worktrees.
How to use it: Enable Code Mode, enter a worktree, then run a script; after resuming, send a new prompt to continue and check MCP status with `/mcp`.
Tip: Before using Code Mode in production automation, add separate regression tests for worktree paths, approval text, and waiting after resume.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code
Console login and browser verification no longer show false success after cancellation
Pressing Esc immediately after the browser step during `/login` no longer accidentally changes the current login. Also fixed an issue where the browser displayed a success page for failed or canceled logins.
Usage details
Who can use it: Claude Code 2.1.325; `/login` and browser-based Console/Claude login.
How to use it: Start `/login`, wait until browser verification is complete, and if you cancel, check the actual status in the terminal; if the wrong account was opened, switch back to the current profile.
Tip: On shared machines, verify the correct account and organization name before closing the login window.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Desktop
Desktop third-party deployments no longer get stuck waiting for token refresh
Fixed an issue where sessions in third-party deployments of Claude Desktop remained in the `Stopping` state for a long time while waiting for token refresh. Sign-out and reconnect now complete faster.
Usage details
Who can use it: Claude Desktop third-party deployments that include Claude Code 2.1.325.
How to use it: Update Desktop and restart the third-party gateway session; if the `Stopping` state persists, check the token refresh and gateway connection logs.
Tip: Keeping the gateway token lifetime longer than the Desktop session duration reduces frequent shutdown and reauthentication loops.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Desktop
Desktop and SDK sessions reconnect folder MCP servers correctly
When a folder is moved or a session starts prewarmed, the folder's own `.mcp.json` and local MCP servers are no longer incorrectly listed as if they had been added by the host. WebSocket-based MCP servers are also connected correctly.
Usage details
Who can use it: Claude Code 2.1.325; Claude Desktop and Agent SDK sessions, moved folders, and WebSocket MCP.
How to use it: After moving a folder, restart the session and check the `/mcp` list; define the WebSocket server in the project folder's MCP configuration rather than the host's.
Tip: Checking the MCP list in prewarmed Desktop sessions before making an actual tool call helps catch an incorrect host/project distinction early.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code
Login startup and short auth commands run without locking up
Valid keyless Console or Anthropic profile tokens can now be read without waiting for the credentials lock. Fixes also address a lock left by short commands such as `claude auth status` in a Console profile, as well as the accumulation of temporary OAuth lock files.
Usage details
Who can use it: Claude Code 2.1.325; keyless Console login, Anthropic profiles, and short CLI commands.
How to use it: After updating, run `claude auth status`; if an old process is stuck, terminate it first and try the command again. For a new login, use `/login` or a Console profile.
Tip: Running short auth checks before real requests during CI startup surfaces profile-lock-related delays early.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Read-only Git operations in untrusted repositories now require approval
Read-only Git commands in repositories that are not the project's own or that are untrusted now require permission first. Use `--add-dir` instead of `additionalDirectories` to run the command in a trusted additional directory.
Usage details
Who can use it: Claude Code 2.1.325; Git operations in terminal, Desktop, IDE, and cloud sessions.
How to use it: Start Claude Code with `--add-dir /path/to/repository` to designate the repository as a trusted additional workspace; when prompted for permission for an individual read-only command, review and approve it.
Tip: Keep the scope of `--add-dir` narrow instead of creating a persistent allow rule for untrusted repositories, even for read-only operations.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Reading your own Artifacts and cloud Artifact permission hooks work correctly
Claude no longer asks for unnecessary permission when reading a user’s own Artifact or data. A fix also addresses cases where deny and ask rules and hooks for the Artifact tool were not applied in cloud sessions.
Usage details
Who can use it: Claude Code 2.1.325; Artifact tool and cloud sessions.
How to use it: Open your own Artifact and run the tool call; to enforce an organization rule, define a deny or ask rule for the Artifact tool in the settings file and test it in a cloud session.
Tip: Test the Artifact access policy separately with a real user and a cloud session; success in the local terminal alone is not enough.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code
Claude is informed when an MCP task is waiting for a response
When an MCP task is waiting for a user response, Claude now knows the task is pending and that the `/tasks` screen can be checked. This reduces the chance that the model will assume a background MCP task is complete.
Usage details
Who can use it: Claude Code 2.1.325; terminal, SDK, and host sessions that use MCP tasks.
How to use it: When an MCP task asks a question, open the `/tasks` screen and select the pending task; provide the required response to continue.
Tip: For long-running MCP jobs, clearly specify up front in the prompt which steps require a user response; this makes pending tasks easier to track.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code
MCP plugin reload and reauthentication states recover correctly
Fixed issues where a removed MCP server remained in the `/mcp` list during plugin reload and a server continued to show needs authentication after a briefly rejected token refresh. SDK tool calls to a reconnected MCP server no longer incorrectly return `Not connected`; headless elicitation is also no longer silently canceled when the connection changes.
Usage details
Who can use it: Claude Code 2.1.325; plugin reload, token refresh, Agent SDK, and headless MCP sessions.
How to use it: After reloading the plugin, refresh the list with `/mcp`; if authentication is required, use the Reconnect option and retry the SDK tool call.
Tip: Don’t start many tool calls at once while an MCP server is reconnecting; verify the connection is ready with a single health check.
✓ Verified by official sourceSource: Claude Code changelog - APIClaude Code
Model identity, Fable limits, and provider authentication messages fixed
A saved `sonnet[1m]` setting is no longer converted to a model identity rejected by the API on a new installation. `/fast` in a keyless Console session and `/model` on an unreachable network no longer show an incorrect organization restriction; the Fable limit message now explains the reset time and next steps.
Usage details
Who can use it: Claude Code 2.1.325; Sonnet 1M setting, Fable, and keyless Console/gateway sessions.
How to use it: After a new installation, verify the model identity with `/model`; when you reach the Fable limit, follow the reset time in the message and check `/usage` or plan options.
Tip: If you use a gateway, don’t mistake lack of network access for an organization policy error; first check the connection and the provider’s actual model list.
- APIClaude Code
OpenTelemetry prompt events include mid-turn and merged messages
A `user_prompt` event is now emitted for prompts sent while tool calls are in progress, carrying `delivery.mode: mid_turn` and the active turn’s `prompt.id` fields. Also fixed an issue where earlier text was missing from telemetry events when queued messages were merged in VS Code or a message contained an image.
Usage details
Who can use it: Claude Code 2.1.325; Claude Code and VS Code sessions using OpenTelemetry.
How to use it: Use a schema in your telemetry consumer that reads the `user_prompt` event’s `delivery.mode`, `prompt.id`, and merged text fields; update the old collector schema.
Tip: Validate mid-turn and queue-merge scenarios as separate events in telemetry tests; don’t rely only on end-of-turn events.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Security review and inline Git operations work in special worktrees
`/security-review` and inline Git commands in skills no longer stop with false errors in bare-repository worktrees, `--separate-git-dir` checkouts, and Android `repo` checkouts. Users can now continue working in these setups.
Usage details
Who can use it: Claude Code 2.1.325; bare repository, separate-git-dir, and Android repo checkouts.
How to use it: Open the repository using the relevant checkout format and run `/security-review`; if the operation still stops, verify the displayed Git path and worktree status.
Tip: Record the checkout type explicitly in CI before automating security reviews; this makes debugging much easier.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code
Sparse clone root files and adding repositories to self-hosted sessions fixed
On older Git versions, sparse plugin or marketplace clones using `worktree.sparsePaths` no longer exclude repository root files. A repository added mid-session to a multi-repository self-hosted runner session is now available as well.
Usage details
Who can use it: Claude Code 2.1.325; older Git versions such as Git 2.34 and self-hosted runner sessions.
How to use it: After updating the sparse configuration, clone again. In a self-hosted session, after adding a new repository, select it again using the repository picker or the relevant work command.
Tip: On older Git versions, verify root files and plugin manifests in a CI step after a sparse clone.
✓ Verified by official sourceSource: Claude Code changelog - FeatureClaude Code
Team sessions start in the correct folder and warn about temporary scratchpads
New sessions for tmux and iTerm2 teammates, as well as sessions opened with the left arrow from the Agents view, now start in the session’s own folder instead of the shell’s last `cd` location. Claude’s instructions also say not to put files intended to be kept permanently in a temporary scratchpad folder that can be cleared.
Usage details
Who can use it: Claude Code 2.1.325; sessions using tmux, iTerm2, and the Agents view.
How to use it: Open a new session from the Agents view or start a tmux/iTerm2 teammate; have persistent files written to the project folder or a designated plans folder.
Tip: In automation prompts, specify the persistent destination path for outputs; this prevents work from being lost when the temporary working folder is cleared.
✓ Verified by official sourceSource: Claude Code changelog - APIClaude Code
Context limits for unrecognized Claude models and mTLS password handling fixed
`CLAUDE_CODE_MAX_CONTEXT_TOKENS` now also sets the context for unrecognized model IDs beginning with `claude-`. Claude Code's ripgrep, local Git, and sandbox helper processes no longer pass the mTLS client key password into their environments.
Usage details
Who can use it: Claude Code 2.1.325; unrecognized `claude-*` models used through a gateway and mTLS environments.
How to use it: Set `CLAUDE_CODE_MAX_CONTEXT_TOKENS` to manage the gateway model's context; use `CLAUDE_CODE_DISABLE_1M_CONTEXT=1` to retain the old 200K assumption.
Tip: If you name gateway model IDs in the `claude-` format, verify the context value separately; the 1M default can cause overfilling with providers that have smaller windows.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Teleport safely stops stash selection in unusual Git states
In some unusual Git states, `/teleport` now stops and tells the user what to do instead of attempting to select the wrong stash. This prevents working changes from being moved accidentally when resuming remotely.
Usage details
Who can use it: Claude Code 2.1.325; `/teleport` and complex Git states.
How to use it: If `/teleport` stops, first inspect `git status` and the stash state, apply the recommended fix, then run the command again.
Tip: Using a clean working state or a named stash before teleporting reduces ambiguous stash selections.
✓ Verified by official sourceSource: Claude Code changelog - FeatureClaude Code
Prompt suggestions are more visible and less intrusive in VS Code and terminals
Prompt suggestions are now also shown in VS Code and similar integrated terminals, where they can be accepted with Tab. When background or scheduled tasks start eight consecutive turns, suggestions refresh less often to reduce unnecessary usage.
Usage details
Who can use it: Claude Code 2.1.325; VS Code and integrated terminals that support prompt suggestions.
How to use it: Press Tab when a suggestion appears in VS Code or the terminal. To turn suggestions off, set `promptSuggestionEnabled: false` in Claude Code settings.json.
Tip: Keeping suggestions on and turning them off only for long-running automatic tasks preserves quick repetitions while reducing unnecessary refreshes.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code
VS Code adds Console sign-in without API key creation and an MCP redirect field
The Claude Code VS Code extension now supports signing in with a Console account that does not create an API key. In SSH, WSL, and container windows, there is a separate field for pasting the redirect URL when signing in to an MCP server from the panel. The untrusted folder notice explains why the extension is disabled and how to enable it; errors for blocked programs, localhost connections, models, effort, providers, and MCP permissions are also clearer.
Usage details
Who can use it: VS Code extension containing Claude Code 2.1.325; untrusted folders, SSH/WSL/container windows, and managed organization settings.
How to use it: Open the Claude Code panel in VS Code; select a Console account at sign-in, paste the redirect URL in the MCP panel if needed, and approve trust for a new folder. While a command is running, check its output in the chat card and the model and effort options in their respective selectors.
Tip: If your organization uses `allowedProviders` or `maxEffortLevel`, check your administrator's limits first; the extension now handles unavailable options more accurately.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code
Fixed Windows resume and Linux sandbox path edge cases
Inaccessible PATH entries no longer cause unnecessary delays at startup on Windows; entries with different drive-letter casing or slash styles can be found with `/resume`, and project trust is preserved. On Linux, sandbox commands using the intersection of allowRead and denyRead under a symlink no longer produce a `bwrap` error.
Usage details
Who can use it: Claude Code 2.1.325; Windows `/resume` and Linux sandbox.
How to use it: On Windows, use `/resume` to select the saved session again; on Linux, run the sandbox path under a symlinked home directory and check the access results.
Tip: Normalize Windows CI paths to a single drive-letter format; on Linux, write the sandbox rule using the real path of the symlink target.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Responses no longer disappear in Agent view or narrow terminals
Fixed scheduled task responses being hidden in Focus view, background subagent prompts not appearing when fullscreen was off, long options overlapping in narrow terminals, and first-run lines disappearing. Control characters in the welcome header and the red error shown for commands that only the user can run are now displayed more safely and clearly.
Usage details
Who can use it: Claude Code 2.1.325; terminal, Focus view, Agents view, and first-run screens.
How to use it: Resize the session in a narrow terminal and open the prompt or Agents view; if a command can only be run by the user, type it into the prompt yourself to continue.
Tip: Increasing terminal width before first run prevents both display overflow and shortcut lines from disappearing.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code
Atlassian, Asana, and Sentry connectors no longer incorrectly appear to fail in cloud sessions
A working Atlassian, Asana, or Sentry connector is no longer reported as failed in a cloud session, even if the plugin lists it at a different URL. The mapping between the connector ID and the plugin URL has been fixed.
Usage details
Who can use it: Claude Code 2.1.325; Claude Code cloud sessions and related connector plugins.
How to use it: Keep the plugin up to date and reload the connector in your cloud session; if the error persists, compare the actual connector URL with the URL in the plugin manifest.
Tip: In custom plugins, keeping the connector URL consistent with the official connector ID prevents false error messages after updates.
✓ Verified by official sourceSource: Claude Code changelog - Pricing / PlanClaude Code
Spend errors for Cloud and Remote Control no longer show outdated administrator guidance
The `ask your admin to raise it` guidance has been removed from spending limit and shared budget errors under Cloud sessions and Remote Control. Users now see a more direct error flow that explains their current limit status.
Usage details
Who can use it: Claude Code 2.1.325; Cloud sessions and Remote Control.
How to use it: For a limit error, check `/usage-credits` or your organization’s usage page. If needed, submit a separate request to your administrator under the current organization spending policy.
Tip: To resolve a budget error, check not only whether the limit can be increased, but also that you’re signed in with the correct account and provider.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Dataviz skill improves recommendations for part-to-whole charts
The bundled dataviz skill's part-to-whole recommendations have been refined for static visuals and categories with a natural order, such as age ranges. This results in more suitable chart recommendations for the same data type.
Usage details
Who can use it: Claude Code 2.1.325; bundled dataviz skill.
How to use it: When calling the dataviz skill, specify whether the data is part-to-whole or naturally ordered, and whether the output is a static visual.
Tip: For ordered categories such as age bands, prioritize visuals that preserve the order over pie charts.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Sign-in and Voice error messages identify which setting is blocking the action
The `claude --desktop` sign-in error now identifies the API key, provider, or setting blocking account sign-in. `/voice` also clearly explains when a managed setting or project setting prevents changing modes. On macOS and Windows, users are also shown where to select a microphone when no microphone audio is detected.
Usage details
Who can use it: Claude Code 2.1.325; Desktop sign-in, `/voice`, macOS, and Windows.
How to use it: Fix the blocking setting identified in the `/login` or `claude --desktop` error message. For Voice, select the correct microphone in your system sound settings, then run `/voice` again.
Tip: First check whether enterprise settings override local settings; don’t try to bypass a managed rule by changing the local settings.json.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
First worktree run and brief sessions are more consistent
The first `--worktree` run in a new home directory no longer skips the plugin's `WorktreeCreate` hook. Brief-mode sessions such as Dispatch also no longer send a second response after a turn response has been given.
Usage details
Who can use it: Claude Code 2.1.325; `--worktree`, plugin hooks, and Dispatch-like brief sessions.
How to use it: In a new home directory, start `claude --worktree` with a plugin hook and verify the hook output; don't expect a second response for the same turn in brief sessions.
Tip: Running the first-run test once with a clean home directory catches hook differences that appear in CI only with cached installations.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code
Slack app tips now account for cloud session policies
Claude Code no longer displays Slack app tips when an organization policy denies cloud sessions. This avoids suggesting a workflow users can’t use.
Usage details
Who can use it: Claude Code 2.1.325; organizations that restrict cloud sessions and the Slack integration.
How to use it: Check the cloud session permission in your organization’s settings. If it’s disabled, Slack tips not appearing is expected behavior.
Tip: Verify your organization’s cloud session policy before covering the Slack workflow in user training.
✓ Verified by official sourceSource: Claude Code changelog - FeatureClaude Code
Stats and Insights reports show more accurate information
A bug that caused the Active days total in `/stats` to appear one day higher has been fixed. `/insights` no longer displays a report-ready message when there are no sessions suitable for analysis, and two values in the HTML report are now escaped safely.
Usage details
Who can use it: Claude Code 2.1.325; the `/stats` and `/insights` commands.
How to use it: Run `/stats` or `/insights` in a session. If there’s nothing to analyze, build up enough sessions first, then try the command again.
Tip: When exporting a usage report, interpret Active days and analysis eligibility as separate metrics.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Tag
Claude Tag Slack Artifact links now show a card when sign-in has expired
Fixed an issue where an Artifact link would not show a card if the poster's Claude sign-in had expired in a Slack workspace not managed by the organization. In this situation, the link now displays at least a plain-text card.
Usage details
Who can use it: Claude Code 2.1.325; Claude Tag, Slack, and Artifact links.
How to use it: Open the Artifact link in Slack; if a rich preview doesn't appear, use the link in the plain card and renew your Claude Tag session.
Tip: Don't rely on Slack previews; also include critical Artifact links directly in the message body.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
VS Code marketplace installation confirmation now uses a trust message
The marketplace confirmation button in the VS Code installation link now says `Trust marketplace and continue` more explicitly. This change makes the decision to trust the extension source visible in the installation flow.
Usage details
Who can use it: Claude Code 2.1.325; VS Code extension installation.
How to use it: When installing Claude Code from the marketplace, verify the publisher and select `Trust marketplace and continue` only if you trust it.
Tip: Setting marketplace trust policies in advance on organization devices prevents users from accidentally approving the source one by one.
✓ Verified by official sourceSource: Claude Code changelog