Anthropic · Claude
New in this edition · 54
- AvailabilityClaude Code
Claude Code fast mode expands to Vertex regions
Claude Code 2.1.322 supports fast mode on Vertex in the global, US, and EU regions. If Vertex rejects a fast request, the client falls back to standard speed.
Usage details
Who can use it: Claude Code 2.1.322 and Vertex models that support fast mode; global, US, and EU regions.
How to use it: Update Claude Code to version 2.1.322 or later and use the `/fast` command or the fast mode setting with a supported model.
Tip: Because quotas and model support on Vertex can vary, monitor the latency and cost of the standard-speed fallback in logs.
✓ Verified by official sourceModels: Claude Fable 5.2, Claude Mythos 5.2, Claude Opus 5.5Source: Claude Code changelogSource: Claude Code release v2.1.322 - APIClaude Code
MCP hook responses over 16 MiB now cause calls to be rejected
In stdio and HTTP MCP servers, PreToolUse `mcp_tool` hook responses larger than 16 MiB are no longer skipped; the tool call is explicitly rejected. This prevents large hook output from entering the context unchecked.
Usage details
Who can use it: Claude Code 2.1.321; stdio and HTTP servers using PreToolUse MCP hooks.
How to use it: Keep hook responses under 16 MiB; write large data to a file and return the file path to Claude.
Tip: Check the response size limit in the MCP server in advance and report rejections as meaningful errors.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - CapabilityClaude Code
NotebookEdit and Edit reliability fixed for network paths
Fixes address NotebookEdit deleting/overwriting the first cell and Edit changing the wrong match, replacing the entire file with an empty `old_string`, or editing a notebook as if it were plain text on UNC, WSL, and `/net` paths.
Usage details
Who can use it: Claude Code 2.1.321; Windows network paths, WSL, and other network filesystems.
How to use it: Update Claude Code and rerun notebook/file editing workflows on network paths.
Tip: After writing to a network filesystem, automatically check the diff and the contents of the first and last cells.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - AgentClaude Code
Background subagent reports are preserved after compaction and restart
Auto mode no longer loses a subagent report that started before compaction; after a restart, the subagent's message to the main conversation is no longer left unanswered; and a background agent mistakenly thought to have stopped can be restarted. This improves the reliability of long-running, interrupted agent workflows.
Usage details
Who can use it: Claude Code 2.1.321; background agent, compaction, and cloud restart scenarios.
How to use it: In the updated version, start the subagent as usual; if no report arrives, check its status and the option to reopen it in the Agents/Tasks view.
Tip: For long-running tasks, write subagent reports to the Tasks history as well as relying on the latest notification.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - Plugin / IntegrationClaude in Chrome
Chrome tools in Claude Code comply with organizational policy
Claude in Chrome tools provided by Claude Code follow the organization’s Claude in Chrome policy in embedded applications such as the Claude Desktop Code tab. Enterprise tool restrictions now also apply to this embedded use.
Usage details
Who can use it: Claude Code 2.1.321, Claude Desktop Code tab, and customers who manage organizational policies.
How to use it: Have the organization administrator manage the Claude in Chrome policy; after updating Claude Code, check the permissions for embedded tools.
Tip: Manage permissions for the Chrome extension and Desktop Code tab under the same organizational policy, rather than separately.
✓ Verified by official sourceSource: Claude Code changelog - ModelClaude Code
Fable 5.2 added to Claude Code, and Fable is now the default
Claude Code 2.1.321 added the `claude-fable-5-2` model and made the Fable model the default. Saved Fable 5.1 selections move to the `fable` selection immediately on Pro and Max, and on Team and Enterprise when the organization allows it.
Usage details
Who can use it: Claude Code 2.1.321; subject to plan and organizational model permissions.
How to use it: Update the version; use `/model claude-fable-5-1` to force the old model or `/model claude-fable-5-2` to select the new ID.
Tip: Before switching models, compare token costs, thinking behavior, and tool compatibility with a short eval on critical projects.
✓ Verified by official sourceModels: Claude Fable 5.2, Claude Fable 5.1Source: Claude Code changelogSource: Claude Code release v2.1.321 - ModelClaude API
Claude Fable 5.2 and Claude Mythos 5.2 are now available
Anthropic has made Claude Fable 5.2, with a 1 million token context, a 128,000-token maximum output, and continuous adaptive thinking, generally available, and opened Claude Mythos 5.2 to verified organizations. Both models are faster than their predecessors and cost $8 per 1 million input tokens and $40 per output token.
Usage details
Who can use it: Fable 5.2 is available on Claude API, Claude Platform, Amazon Bedrock, Google Cloud, and Microsoft Foundry; Mythos 5.2 is available only to organizations accepted into Anthropic's verification programs.
How to use it: Set the `model` field in a Messages API request to `claude-fable-5-2`; for Mythos, apply to the verification program and use `claude-mythos-5-2`.
Tip: For long tasks, start by measuring with the default `high` effort; move to a higher level only when evals show a quality improvement.
✓ Verified by official sourceModels: Claude Fable 5.2, Claude Mythos 5.2Source: Claude Fable 5.2 and Mythos 5.2Source: Claude Platform release notes - Plugin / IntegrationClaude Code cloud sessions
Memory and reconnection issues fixed in cloud connector and MCP sessions
Fixes address hangs or out-of-memory errors with connectors that return very long resource names, MCP servers appearing connected without tools after reconnecting, and incorrect reporting of cloud proxy permission status. Large uploads are retried after HTTP 507.
Usage details
Who can use it: Claude Code cloud sessions, connectors, MCP servers, and uploads behind a proxy.
How to use it: Update Claude Code; retest connector resource lists and MCP reconnect flows.
Tip: Keep resource names short on connector servers and design retries to be idempotent.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - AvailabilityClaude Code cloud sessions
Messages with large images and subagent messages are preserved after a cloud restart
If a restart occurs before Claude gives its first response, a message containing a large image is not dropped; a subagent’s pre-restart message does not go unanswered in the main conversation. This improves continuity for cloud sessions after a restart.
Usage details
Who can use it: Claude Code cloud sessions and restart/reconnect flows.
How to use it: After the session reconnects, check the main conversation and subagent history; verify the transcript before resending a task that appears to be missing.
Tip: Keep large images and critical subagent tasks idempotent to prevent automatic retries from creating duplicate work.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - APIClaude API
A new toolset is now required for computer use
Fable 5.2 and Mythos 5.2 support the computer use feature through `computer_toolset_20260801`. The old `computer_20251124` definition returns a 400 error on surfaces other than Amazon Bedrock.
Usage details
Who can use it: Claude API, Claude Platform, and supported cloud surfaces; Amazon Bedrock will temporarily continue to accept the old tool.
How to use it: Define the `computer_toolset_20260801` toolset in requests instead of the old `computer_20251124`.
Tip: Before moving to production, search all platforms for the old tool name and remove it; don't rely on temporary compatibility in Bedrock.
✓ Verified by official sourceModels: Claude Fable 5.2, Claude Mythos 5.2Source: What's new in Claude Fable 5.2Source: Claude Platform release notes - CapabilityClaude Cowork
Cowork hooks can no longer change question and plan results
In Cowork cloud sessions, the PostToolUse hook can no longer change the AskUserQuestion response or ExitPlanMode plan in the result; Claude reads the original result. This prevents hooks from compromising the integrity of user decisions and plans.
Usage details
Who can use it: Claude Cowork cloud sessions and organizations using PostToolUse hooks.
How to use it: Use hooks only for observation or side effects; redesign workflows that rely on changing question and plan results.
Tip: Read critical approvals from Claude’s original question/plan result, not from hook output.
✓ Verified by official sourceSource: Claude Code changelog - Pricing / PlanClaude API
Fable 5.2 and Mythos 5.2 price drops to $8/$40
The new models' standard price is $8 per MTok of input and $40 per MTok of output, down from the $10/$50 price listed for Fable 5.1 and Mythos 5.1. The Claude Code announcement lists cache reads at $0.20 per MTok.
Usage details
Who can use it: Claude API and related Anthropic-managed cloud surfaces; final pricing from cloud providers may vary by provider.
How to use it: Change the model ID in your existing client to `claude-fable-5-2` or, with authorized access, `claude-mythos-5-2`; monitor usage costs in Console.
Tip: For long inputs, measure prompt caching alongside the new pricing to compare whether switching from the old model is actually cheaper.
✓ Verified by official sourceModels: Claude Fable 5.2, Claude Mythos 5.2Source: Claude Platform release notesSource: Claude Code changelog 2.1.321 - FeatureClaude API
API fast mode enabled for Fable 5.2 and Mythos 5.2
The output token speed of the two new models can be increased by up to 2.5x with the `speed: "fast"` option in Messages API requests. Fast mode is available for Fable 5.2 and Mythos 5.2 at $16 per MTok of input and $80 per MTok of output.
Usage details
Who can use it: Claude API, Anthropic and Google managed Google Cloud; through `-fast` model deployments in Microsoft Foundry. Mythos access is limited to verified organizations.
How to use it: Add `speed: "fast"` to the Messages API body; in Microsoft Foundry, call the `claude-fable-5-2-fast` or `claude-mythos-5-2-fast` deployment and do not send the `speed` field.
Tip: Use Fast mode for streaming and latency-sensitive work; note that it is not supported together with the Batch API or Priority Tier.
✓ Verified by official sourceModels: Claude Fable 5.2, Claude Mythos 5.2Source: Claude Platform release notesSource: Fast mode - CapabilityClaude Code
If Fast mode is limited, it falls back to standard speed on the same model
When Fast serving is rate-limited, overloaded, or in error, Claude Code does not lose the response, switch models, or retry for minutes; it first tries the same model at standard speed.
Usage details
Who can use it: Claude Code 2.1.321 and supported models that use Fast mode.
How to use it: Use Fast mode as usual; no additional setting is required for fallback to work.
Tip: When measuring speed SLAs, record Fast and standard fallback events as separate metrics.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - SettingClaude apps gateway
Gateway error messages no longer expose credentials
Claude apps gateway error messages show the gateway address without a username or password. This preserves useful endpoint information for support while preventing secrets from leaking into error text.
Usage details
Who can use it: Claude apps gateway 2.1.321 and Claude Code/Claude Desktop behind the gateway.
How to use it: Get the gateway address from the error message; check only secure gateway logs for authentication details.
Tip: Still mask usernames and passwords in URLs in log collection systems; logs from older versions are unaffected.
✓ Verified by official sourceSource: Claude Code changelog - APIClaude apps gateway
Gateway upstream endpoint is now set with `base_url`
The gateway no longer considers the environment's `ANTHROPIC_*_BASE_URL` variables for Bedrock, Vertex, and Foundry upstreams. Administrators who want to use a different endpoint must explicitly set `base_url` in the upstream definition.
Usage details
Who can use it: Administrators using a Bedrock, Vertex, or Foundry upstream on Claude apps gateway.
How to use it: Add `base_url` to the gateway upstream configuration and verify that it does not rely on environment variables.
Tip: For proxy migrations, define the gateway config explicitly in version control rather than silently relying on environment variables.
✓ Verified by official sourceSource: Claude Code changelog - APIClaude apps gateway
Layered gateway policies combine MCP servers
Under `policy_mode: layered`, managed MCP servers are now collected across all matching policies, including `match: {}`. A gateway using this mode may expose more managed servers after an upgrade.
Usage details
Who can use it: Claude apps gateway and enterprise organizations using layered policy.
How to use it: Review your gateway policy file; if you use `policy_mode: layered`, test the MCP merge and access boundaries across all matching policies.
Tip: Export the active MCP list before and after the upgrade to check for unexpected tool expansion.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code
Managed marketplace names and plugin sources are enforced
A name defined in managed `extraKnownMarketplaces` cannot be added from another source, hides the entry from the external source, and reinstalls plugins listed by the marketplace from there. Data inherited from another source is also set aside for cleanup; settings and secrets can be restored with the restore command.
Usage details
Who can use it: Claude Code 2.1.321 for organizations using managed settings.
How to use it: Define the `extraKnownMarketplaces` source in the organization setting; use the `claude plugin restore-set-aside` command to restore set-aside data.
Tip: Keep marketplace names unique and stable across the organization; don’t rely on personal marketplaces with the same name.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
MCP OAuth and Bash permission bypasses closed
Secrets such as refresh tokens can no longer be sent to another host through MCP OAuth redirects; issues with read-only Bash escaping the sandbox, writes evaluated in the wrong directory, and deny/protected-file checks on cp/mv targets have been fixed. This release also resolves various permission prompt races more accurately.
Usage details
Who can use it: Claude Code 2.1.321; MCP OAuth, Bash sandbox, and file permission policies.
How to use it: Update Claude Code; retest OAuth redirect hosts for MCP servers and Bash deny/ask rules.
Tip: Add redirect, symlink, and different working-directory scenarios to security regression tests.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - CapabilityClaude API
Thinking block behavior during model switches clarified
On Claude API and Google Cloud Google-managed surfaces, reasoning from previously supported models is preserved when a conversation switches to Fable 5.2 or Mythos 5.2. When a conversation switches from these models to another model, new thinking blocks are discarded, but the request succeeds.
Usage details
Who can use it: Claude API and Google Cloud Google-managed; transition rules in the model documentation apply to other providers.
How to use it: Configure your model router to send `claude-fable-5-2`/`claude-mythos-5-2` thinking blocks only to the same two model families.
Tip: For every route that switches models, validate scenarios that preserve thinking blocks and scenarios that discard them with separate regression tests.
✓ Verified by official sourceModels: Claude Fable 5.2, Claude Mythos 5.2, Claude Opus 5.5, Claude Sonnet 5.5, Claude Haiku 5.5Source: Claude Platform release notes - SettingClaude Code
Mods activate without approval in auto and bypass modes
Mods written by Claude now open without asking for approval in auto and bypass modes, even if some managed restrictions such as `allowUnsandboxedCommands: false` or `allowManagedDomainsOnly` are in place. Mods are not loaded in `dontAsk` mode.
Usage details
Who can use it: Claude Code 2.1.321; auto, bypass, and dontAsk sessions using mods.
How to use it: Check permission behavior in `/config` and the permission mode in the organization’s managed settings; if you don’t want mods without approval, use a more controlled mode instead of `dontAsk`.
Tip: Also test that mods’ own tool calls are subject to deny rules and organization policy in your enterprise policies.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Mods’ own tool calls don’t show permission prompts
`$.tool.call` and `$.mcp.call` calls in mods do not generate permission prompts under the user’s ask rules, `dontAsk`, or `-p` execution. Deny rules and organization policy still apply.
Usage details
Who can use it: Claude Code 2.1.321 and terminal, headless, or SDK sessions using mods.
How to use it: Define the security boundary with deny rules and managed policy; don’t rely on user prompts alone to protect mod calls.
Tip: Especially in `-p` and auto mode, restrict the MCP tools mods can call with a narrow allowlist.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Session startup, terminal commands, and git status are more reliable
Fixes address issues where a failed git status appeared clean or the first file was mistakenly marked as staged, multiple Bash commands ran in the wrong directory, and zsh `KSH_OPTION_PRINT` produced empty output. On Linux NFS failure, `claude -p` now returns an error and 1 instead of silently returning 0.
Usage details
Who can use it: Claude Code 2.1.321; sessions using Bash, git, zsh, and Linux NFS.
How to use it: Update to the new version; handle error codes in `claude -p` text/JSON output, and don't treat git status unavailable as an error.
Tip: In CI, check that the transcript and git status output were actually produced before treating exit code 0 as success.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - SettingClaude Code
The `--settings <file>` flag is added for Remote Control
`claude remote-control` now accepts a settings file to apply to every session it starts. If the file changes, no new session is started; Remote Control must be restarted for the changes to take effect.
Usage details
Who can use it: Claude Code 2.1.321 and terminal/remote clients using `claude remote-control`.
How to use it: Run `claude remote-control --settings /path/to/settings.json`; restart the process when the settings file changes.
Tip: Keep the shared settings file in version control and don't put secrets in it as plain text.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Remote Control sessions stay in their starting directory
A connected Remote Control client can no longer move a session to a different directory from the one where it started. This prevents the remote client from operating in the wrong workspace.
Usage details
Who can use it: Claude Code 2.1.321 Remote Control sessions.
How to use it: Start Remote Control from the correct working directory; start a new session to change directories.
Tip: Record the starting directory as an absolute path in automation commands, and don't try to reuse the session connection.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code
Remote Control and Desktop sessions recover more reliably after disconnects
A crashed Remote Control process can receive a new message sooner; Queue for later messages no longer slip into the middle of an active turn; and issues where a disconnected session appeared connected or showed login expired have been fixed. Messages getting stuck in Desktop Code tab and repeated `/compact` calls have also been fixed.
Usage details
Who can use it: Claude Code 2.1.321 Remote Control, web/mobile clients, and Desktop Code tab.
How to use it: Update Claude Code and the Desktop client; check the connection status again in a new session.
Tip: For long tasks, track connection status separately from session history loading; a connected badge alone isn't enough.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - Pricing / PlanClaude
Paid plans get temporary Fable usage and limit resets
From November 9–16, Pro and Team standard seats can use Fable models up to 50 percent of their weekly limits at no additional cost and get one Fable reset. Max, Ultra, Team premium, and legacy seat-based Enterprise premium seats get between one and three resets, depending on subscription duration.
Usage details
Who can use it: Pro, Max, Ultra, Team standard/premium, and legacy seat-based Enterprise premium; Free, self-serve Enterprise, usage-based Enterprise, and applicable standard Enterprise seats are excluded.
How to use it: In Claude, open Settings > Usage and select `Reset for free` under Limit resets.
Tip: A reset does not raise your limit; it only restores usage spent on Fable. Save it for a genuinely demanding task before it expires.
✓ Verified by official sourceModels: Claude Fable 5.2, Claude Fable 5.1, Claude Fable 5Source: Claude Fable 5.2 launch offers - AvailabilityClaude
New models added to the Covered Models scope
Fable 5.2 is designated a generally available Covered Model, and Mythos 5.2 a limited-access Covered Model. For these models, a default minimum 30-day data retention period and automated safety review apply; zero data retention is unavailable unless Anthropic explicitly authorizes it.
Usage details
Who can use it: Fable 5.2 is available in Claude apps, Claude Platform, Bedrock, Google Cloud Agent Platform, and Microsoft Foundry; Mythos 5.2 is limited to approved partners.
How to use it: Before selecting a model, check Covered Models and your organization’s retention agreement; if you need ZDR, discuss the Enterprise Frontier Safeguards option with your Anthropic account team.
Tip: For work requiring compliance, choose models based not only on quality but also on retention and safety review requirements.
✓ Verified by official sourceModels: Claude Fable 5.2, Claude Mythos 5.2Source: Covered ModelsSource: Claude Fable 5.2 and Mythos 5.2 - APIClaude API
Prefix check for preserved thinking is now required on new models
Fable 5.2 and Mythos 5.2 validate submitted thinking blocks whose system prompt, tools, or preceding message prefix has changed, regardless of account age, and return a 400 error when they don't match. This extends behavior that was the default only for certain new accounts on Fable 5.1.
Usage details
Who can use it: Claude API and surfaces that support the new models; applications that produce thinking blocks and resend them in a subsequent turn are affected.
How to use it: Do not change the message prefix before switching models; if a change is required, follow the migration guide or consider the supported beta option `thinking.block_binding.prefix_mismatch_behavior: "drop_block"`.
Tip: Test router or fallback code to ensure it does not automatically carry over old thinking blocks after switching models.
✓ Verified by official sourceModels: Claude Fable 5.2, Claude Mythos 5.2Source: What's new in Claude Fable 5.2 - CapabilityClaude Code
cp and mv invoked by path now use the same security checks
Using a full path such as `/bin/cp` is now subject to the same path checks as short `cp` and `mv` calls. This reduces the chance of bypassing the permission policy by writing out the full command name.
Usage details
Who can use it: Claude Code 2.1.321; Bash commands and file permission rules.
How to use it: Define both command behavior and target directories in permission rules; do not make separate exceptions for commands invoked by full path.
Tip: In security tests, try the `cp`, `/bin/cp`, `mv`, and `/bin/mv` variants in the same scenario.
✓ Verified by official sourceSource: Claude Code changelog - APIClaude API
Advisor tool requires model compatibility with new models
When using Fable 5.2 or Mythos 5.2 as the executor, the advisor must be one of these two models; any other advisor model returns 400. Fable 5.2 can be used as an advisor for any executor model.
Usage details
Who can use it: Claude API applications using the beta advisor tool.
How to use it: When migrating the executor to the new models, set the `model` field in the advisor definition to `claude-fable-5-2` or `claude-mythos-5-2`.
Tip: Validate executor and advisor model pairs at application startup to reduce the risk of receiving a 400 in production.
✓ Verified by official sourceModels: Claude Fable 5.2, Claude Mythos 5.2Source: Claude Platform release notesSource: What's new in Claude Fable 5.2 - AgentClaude Code
Pending subagent reports are answered in a single model call
Auto mode in headless sessions, Desktop, and VS Code now answers simultaneously pending background subagent reports in a single model call, as in the terminal. This reduces unnecessary calls in parallel agent workflows.
Usage details
Who can use it: Claude Code 2.1.321; headless, Claude Desktop, and VS Code auto mode.
How to use it: Start background subagents as usual; pending reports are grouped automatically.
Tip: As you track the reduction in call count, also measure the size of reports in each call and context usage.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Dropped images are reread less often in sessions with many images
In sessions with many images that don't fit in a single request, Claude is told which images it has already seen, and rereading unchanged images is limited. This reduces wasted context and image tool calls.
Usage details
Who can use it: Claude Code 2.1.321; image-heavy sessions that don't fit in a single request.
How to use it: Send images with meaningful file names; refer to the output of the first read instead of asking to read the same image again.
Tip: For large image sets, send changed files separately and avoid reuploading the same file.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Context estimates and WebFetch errors are reported more accurately
The overcounting of context usage by tool definitions has been fixed; when the model returns an empty response, WebFetch now reports an explicit error instead of sending it to Claude as page content. Prompt suggestion also avoids unnecessary API calls for tool-call responses.
Usage details
Who can use it: Claude Code 2.1.321; sessions using long context, WebFetch, and prompt suggestion.
How to use it: After updating, recheck the `/context` output and the WebFetch scenario where the model returns an empty response.
Tip: Do not treat empty web responses as valid sources; use a fallback or retry when an explicit error is returned.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - AgentClaude Code
Stopped workflow status is reported correctly to Claude
When a user stops or pauses a workflow, Claude no longer says the workflow is still running. The agent's next step is determined by the actual status.
Usage details
Who can use it: Claude Code 2.1.321 workflow and cloud session flows.
How to use it: Stop a workflow and check Claude's status message; resume only work that is actually running.
Tip: Show stopped, paused, and running as separate statuses in your operations interface.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - SettingClaude Code
Email check now blocks only an explicitly risky command
The account email check no longer asks for confirmation except for a shell command that contains the account email address and names User-Agent. This prevents other commands and scheduled runs from being interrupted by unnecessary prompts.
Usage details
Who can use it: Claude Code 2.1.321 and sessions that pass the email address to shell commands.
How to use it: Review commands that contain email addresses; use a secure secret or stdin instead of putting sensitive information on the command line.
Tip: Treat this change as a narrowed warning rule, not a security approval; separately prevent email leaks.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Accessibility fixes for screen readers, the prompt panel, and file names
Fixes address screen reader startup delays, the mode turning off when returning from agent view, and leftover characters in y/n questions being treated as yes. File names containing hidden directional characters are rejected; plugin permission requests are also read aloud explicitly as plugin instead of as a hidden character.
Usage details
Who can use it: Claude Code 2.1.321; screen reader, agent view, and file submission flows.
How to use it: Update to the new version; turn screen reader mode back on and test the startup, question, and file submission flows.
Tip: In accessibility testing, also cover system clock rollbacks and names containing invisible characters.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - FeatureClaude Code
Fast mode labels show the current model
The `/fast`, `/config`, and `/model` screens show the current model's name when Fast mode is supported; the wording in the VS Code row that implied only Opus has been removed. This makes Fast access for Fable 5.2 and other supported models clearer.
Usage details
Who can use it: Claude Code 2.1.321 and models that support Fast mode.
How to use it: Open the `/fast` or `/config` screen; enable Fast for a supported model.
Tip: Prepare internal usage guidelines that show the speed option alongside its cost; Fast mode is not the standard price.
✓ Verified by official sourceSource: Claude Code changelog - Pricing / PlanClaude apps gateway
Gateway spend limit reset time shown in local time
Claude apps gateway spend limit errors now show the reset time in the user's local time zone, for example, `resets 4pm (America/Los_Angeles)`. The message was simplified so it does not reveal gateway setting names.
Usage details
Who can use it: Claude Code and Claude Desktop gateway users.
How to use it: Check the time and time zone in the limit message; don't confuse the UTC or server time in the gateway log with the time shown to the user.
Tip: Also record the local time zone in enterprise support records to correctly match the same reset event across different regions.
✓ Verified by official sourceSource: Claude Code changelog - APIClaude Code
An unnecessary rejected self-hosted runner now exits with 0
If the server indicates that the runner isn't needed because the session has ended or paused, or the job has become invalid, the runner now exits with 0 instead of error code 1. This prevents a normal no-op from being treated as a CI failure.
Usage details
Who can use it: Claude Code self-hosted runner 2.1.321.
How to use it: Treat runner exit code 0 as normal termination in CI automation; monitor logs and separate error codes for actual startup failures.
Tip: Make sure your automation checks the runner session status as well as the exit code.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Headless sessions reload changed skill mods
Headless Claude Code sessions reload mods when files in `.claude/skills` change. Use `CLAUDE_CODE_PLUGIN_DIR_WATCH=0` to disable unwanted watching.
Usage details
Who can use it: Claude Code headless sessions and mods changed under `.claude/skills`.
How to use it: Use the default behavior; to disable it, set `CLAUDE_CODE_PLUGIN_DIR_WATCH=0` in the runtime environment.
Tip: If you use automatic reloading, write mod files atomically to prevent a partially written file from being loaded.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code
Plugin updates no longer re-download for each worktree
Plugin auto-updates and `/plugin` marketplace updates no longer re-download a plugin for every worktree or folder in the same repository. Dependencies for the updated plugin are also installed.
Usage details
Who can use it: Claude Code 2.1.321; projects using marketplace plugins and multiple worktrees.
How to use it: Update the plugin marketplace as usual; check that the plugin is not re-downloaded and dependencies are installed across worktrees in the same repository.
Tip: Verify the cache directory and plugin lock behavior after the update using a clean worktree.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - Plugin / IntegrationClaude Code
Nested skills folders inside plugins are no longer loaded
Claude no longer loads `.claude/skills` folders inside the plugin directory under `~/.claude/plugins` when working with files at that location. This change prevents plugin resources from being mistakenly treated as project skills.
Usage details
Who can use it: Claude Code 2.1.321; plugins that use nested skills under `~/.claude/plugins`.
How to use it: Move plugin skills to the supported plugin root and check the list of loaded skills with `claude --debug`.
Tip: When updating plugin packages, regression-test the skill path and visible command menu together.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Only the beginning and end are shown for long background commands
Background command notifications and TaskStop results exceeding 1,000 characters now send Claude only the beginning and end of the output. This reduces unnecessary context consumption by long logs.
Usage details
Who can use it: Claude Code 2.1.321; background commands longer than 1,000 characters.
How to use it: When needed, read the full output from the log file written by the command; do not use the notification text as a complete log.
Tip: For automated analysis, save full logs to a file and have Claude read the relevant line range.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code for VS Code
VS Code shows a warning when two credentials are configured
When both an auth token and an API key are configured, the VS Code extension displays a warning above the prompt box, matching the one in the terminal. This makes it clear which credential will be used.
Usage details
Who can use it: Claude Code for VS Code 2.1.321 and users who configure both a token and an API key.
How to use it: Check `ANTHROPIC_AUTH_TOKEN` and API key definitions in VS Code settings and environment variables; keep only your chosen authentication method.
Tip: On enterprise machines, check project, user, and process environments separately; clearing only the VS Code setting may not be enough.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Programs launched on Windows handle PATH settings more safely
When locating programs such as git launched by Claude Code on Windows, relative and UNC PATH entries and network share links are skipped; PATH changes in settings are also taken into account. This reduces the risk of running the wrong executable and problems with network paths.
Usage details
Who can use it: Claude Code 2.1.321 on Windows.
How to use it: Add program paths to the trusted PATH in settings; do not use relative or UNC PATH entries.
Tip: On enterprise machines, compare `git --version` and Claude Code's initial command duration before and after the update.
✓ Verified by official sourceSource: Claude Code changelog - FeatureClaude Code
Background agent that cannot create a worktree now shows the full error
If a `claude --bg --worktree` session cannot create a worktree, the row in the Agents view now shows the error from the beginning instead of an internal label or the last 200 characters. This makes it easier to diagnose the cause in the UI.
Usage details
Who can use it: Claude Code 2.1.321 Agents view and `--bg --worktree`.
How to use it: Open the failed row in the Agents view; fix the repository or permission settings based on the full error shown at the beginning.
Tip: In CI reports, save the entire error text, not just the last line.
✓ Verified by official sourceSource: Claude Code changelog - AgentClaude Code
Skills, commands, and agents that disappeared after worktree changes return
Project skills, commands, and agents reappear mid-session when their folder is removed and restored; an issue where they disappeared from the menu after Claude entered a worktree in SDK and Desktop sessions has also been fixed. This affects workflows that use git stash or worktree switching.
Usage details
Who can use it: Claude Code 2.1.321; terminal, SDK, and Desktop sessions.
How to use it: Update Claude Code, restore the folder, and reopen `/agents` or the skill or command menu.
Tip: In worktree automation, check skill/agent visibility before starting a task; don't rely on an old-version cache.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - Plugin / IntegrationMicrosoft 365 connector
Teams write permissions can be made permanent in new Microsoft 365 setups
For Microsoft 365 connectors added for the first time after November 9, an organization administrator can set the Teams send, post, and reply tools to Always allow; members can also select Always allow for these tools if permitted. HIPAA organizations are excluded from this exception.
Usage details
Who can use it: Claude Team and Enterprise organizations setting up a new Microsoft 365 work/school connector after November 9, 2026; excludes HIPAA scope.
How to use it: Go to Organization settings > Connectors > Microsoft 365; set the Teams send/post/reply tools to Always allow, Needs approval, or Blocked.
Tip: Use Always allow only for low-risk tools with role-based restrictions; leave email and calendar write operations set to Needs approval.
✓ Verified by official sourceSource: Connect to Microsoft 365Source: Set up the Microsoft 365 connector - Pricing / PlanClaude apps gateway
Spend is recorded sooner on a busy gateway replica
The gateway spend limit check skips fewer checks on a busy replica and records spend sooner. This makes the limit message appear closer to the actual usage.
Usage details
Who can use it: Organizations using Claude apps gateway and enforcing spend limits.
How to use it: Update the gateway; monitor the spend view and replica logs together.
Tip: Set limit alert thresholds with a small margin to account for replica delays, rather than exactly at the limit.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code
Ultra plan and upgrade text now appear in the Claude Code interface
The descriptions for session-feedback, `allowedProviders`, and `forceLoginMethod` now include Ultra; Upgrade to Max options have been updated to Upgrade to Max or Ultra. This aligns plan access and sign-in text with the current paid plans.
Usage details
Who can use it: Claude Code 2.1.321; relevant organization settings for Pro, Max, Ultra, and other paid plans.
How to use it: Update Claude Code; plan or sign-in method text updates automatically, and you don't need to enable any additional settings.
Tip: Update documentation for users so that references to Max alone also include Ultra.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Desktop Code tab
Desktop Code tab can send up to 20 messages to other sessions
The Claude Desktop Code tab session increased the number of messages it can send to other sessions before requiring the user to type again from 10 to 20. Long-running parallel workflows require less manual intervention.
Usage details
Who can use it: Claude Desktop Code tab and sessions compatible with Claude Code 2.1.321.
How to use it: Update the desktop app; the behavior is enabled automatically.
Tip: For teams using many background messages, monitor context usage and waiting behavior.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code
Claude Desktop in ~/Applications is detected on macOS
The `/desktop` command no longer acts as if Claude Desktop is missing when it is installed in `~/Applications`. Users are directed to the correct Desktop app.
Usage details
Who can use it: Claude Code 2.1.321 on macOS.
How to use it: Install Claude Desktop in `~/Applications` and run the `/desktop` command in Claude Code.
Tip: For enterprise deployments, include both `/Applications` and `~/Applications` paths in installation checks.
✓ Verified by official sourceSource: Claude Code release v2.1.321 - FeatureClaude Code
Older models are grouped under More models in the model picker
In the `/model` picker, More models is now a row at the bottom that does not renumber the other rows. Older models open under this row.
Usage details
Who can use it: Claude Code 2.1.321.
How to use it: Type `/model` and select the More models row to open the list of older models.
Tip: Write numbered model-selection instructions in team documentation using model names; row numbers may change between versions.
✓ Verified by official sourceSource: Claude Code changelog