Anthropic · Claude
New in this edition · 53
- AgentClaude Code agents
Agent teams and workflows preserve leader, approval, and usage-limit states
Agents in split panes now verify that requests come from the team leader; if the leader has ended, the request is rejected, and plan approval is requested again after `/clear` or `/resume`. Desktop Code tab workflows pause at usage limits and resume when the limit resets; agents stopped by the safeguard are prompted to retry with a narrower prompt.
Usage details
Who can use it: Claude Code agent teams, workflows, and Desktop Code tab.
How to use it: Keep the leader session open; approve the plan again after `/clear` or `/resume`. Wait on the limit card or switch to an eligible model from the options menu.
Tip: For long workflows, check when the limit resets and save critical intermediate outputs outside the workflow as well.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code
Background and Remote Control sessions fixed for identity drift and TLS disconnections
Sessions resumed in the background can no longer switch to a different login instead of a named profile, API key, or workload identity; if a profile is missing, the session stops and explains why. Login, token refresh, and logout no longer wait indefinitely on unresponsive TLS handshakes; when a gateway login is refreshed, the next message continues.
Usage details
Who can use it: Claude Code terminal, background sessions, Desktop, and Remote Control.
How to use it: Upgrade to 2.1.323; reopen active sessions after changing profiles. If a gateway session expires, run `/login` in another terminal.
Tip: To prevent identity drift in automations, pin a named profile or explicit API identity and log warnings from background sessions.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Additional approval boundaries added for artifact updates and app-originated prompts
Artifact updates that may be visible to people outside the organization, or whose visibility cannot be verified, now require confirmation even when an allow rule exists. Prompts that the app marks as “not typed” are no longer passed to agents as user requests; `/skill` or `@file` references among selected files are no longer applied accidentally.
Usage details
Who can use it: Claude.ai, Cowork, Desktop, and Claude Code artifact/workflow flows.
How to use it: Check artifact visibility and approve external-sharing warnings; enter file/skill calls on a separate prompt line.
Tip: Use explicit human approval rather than an allow rule in automations that expose artifacts externally.
✓ Verified by official sourceSource: Claude Code changelog - AgentClaude Desktop Code
Sessions started in Auto mode can open sub-sessions for a task
In a local Code session, a session started by Claude can open new sessions for a task if the Auto mode safety check allows it. The limits are 10 per message you write and 5 at a time.
Usage details
Who can use it: Claude Desktop v5.11492.0 local Code sessions; excludes scheduled runs.
How to use it: Enable Auto mode in a Code session and give it a task; if the safety check allows it, Claude will start sub-sessions automatically.
Tip: Parallel sub-sessions can increase file conflicts; divide tasks among independent folders or worktrees.
✓ Verified by official sourceSource: Claude Desktop changelog - CapabilityClaude Code
Bypasses in Bash, Write/Edit, sandbox, and permission hook checks have been closed
The possibility of running without requesting permission through `sudo`, `env`, wildcards, zsh options, `cp`/`mv`, `rm`, `lsof`, and some `sandbox.excludedCommands` paths has been fixed. Write/Edit tools can no longer bypass Read deny rules, the sandbox can no longer be disabled during a session, the plan file can no longer be written outside the project, and incorrect decisions based on permissions changed by a hook have been prevented.
Usage details
Who can use it: Claude Code across all interactive, `-p`, SDK, Auto, and bypass flows.
How to use it: Update to 2.1.323; retest your permission rules using full commands, wrappers, and actual target paths.
Tip: Use narrowly scoped allow/deny rules and `--permission-mode auto` in production instead of bypassing permissions; do not silently skip security prompts through automation.
✓ Verified by official sourceSource: Claude Code changelog - FeatureClaude Code
Claude Code adds experimental Code Mode
Code Mode has been added as an experimental, opt-in mode in which Claude writes JavaScript for tool calls instead of calling its tools directly. Organization admins can disable the mode at the organization level.
Usage details
Who can use it: Claude Code 2.1.323 and later; experimental and opt-in.
How to use it: Update to Claude Code 2.1.323 and apply the activation setting in the official Code Mode instructions; organization admins can disable the mode in managed settings.
Tip: Try it first in a low-risk repository with limited tool permissions; verify that JavaScript-based calls are subject to your usual permission rules.
- FeatureClaude Desktop
Claude Desktop exports ADMX and Profile Manifest configuration templates
The Developer > Export Configuration Template menu generates ADMX and Profile Manifest policy templates for standard Claude Desktop, third-party inference, or both.
Usage details
Who can use it: Claude Desktop v5.11492.0; administrators.
How to use it: In Claude Desktop, open Developer > Export Configuration Template, select the target configuration type, and export the template.
Tip: After adapting the template to your organization’s policies, deploy it to a small test group in stages; older clients may reject unknown keys.
✓ Verified by official sourceSource: Claude Desktop changelog - Plugin / IntegrationClaude for Manufacturing
Claude for Manufacturing plugin launches with 17 skills and four connectors
The new plugin for manufacturing teams supports workflows such as preparing quotes, quality reports, troubleshooting, and supplier requests with 17 skills. It works with Autodesk Fusion, Infor, Microsoft 365, and Oracle NetSuite connectors, and completes actions with user review/approval.
Usage details
Who can use it: Available as a Claude Marketplace plugin on Team and Enterprise plans.
How to use it: In Claude, install the plugin from Customize > Plugins and type “Set us up” in the chat; Claude configures the systems and connectors and reports which skills can run.
Tip: For first-time use, connect access to manufacturing records through least-privilege accounts, and always require human approval for quotes or purchasing changes before they are published.
✓ Verified by official sourceSource: Introducing Claude for Manufacturing - AvailabilityClaude Meetings
Claude Meetings rolls out in beta to Team and Enterprise plans
Claude Meetings has begun rolling out in beta within Claude and Claude Desktop for Team and Enterprise plans. It can join Google Meet calls as a visible participant, take notes, answer questions, and create documents, whiteboards, or artifacts.
Usage details
Who can use it: Team and Enterprise plans; initially, Google Meet. Unavailable to some ZDR, HIPAA-ready, and CMEK organizations.
How to use it: Add Claude to a meeting from the Claude.ai calendar or turn on automatic joining in Meetings settings; an Enterprise admin must first enable the feature for the organization or relevant group.
Tip: Let everyone in the meeting know in advance that it will be transcribed; note that responses using connected tools may count toward plan usage.
✓ Verified by official sourceSource: Introducing Claude MeetingsSource: Claude Help Center release notes - APIClaude Tag
Slack sessions and more granular admin controls arrive for Claude Tag
In the Enterprise beta, Claude Tag sessions started from Slack can now be listed and their transcripts read by adding them to the Compliance API. Admins can use a confirmation dialog before turning the feature off, Retry if channel settings fail to load, and the Scope filter under Activity > Network events.
Usage details
Who can use it: Claude Enterprise; Claude Tag and Compliance API beta features.
How to use it: Enable Claude Tag in Enterprise administration; query Slack sessions in the Compliance API. Select Scope under Admin > Claude Tag > Activity > Network events.
Tip: Reduce review costs by narrowing compliance exports to the relevant scope rather than the entire organization.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code on the web
Reconnection fixed for Cloud, self-hosted, and Remote Control sessions
Loss of messages, large images, subagent responses, and streamed text in restarted cloud sessions has been fixed; self-hosted sessions getting stuck in Starting/Sending have also been fixed. `Try again` on the connection card now attempts to reconnect instead of sending the words as a user message; web sessions can reconnect automatically.
Usage details
Who can use it: Claude Code on the web, self-hosted runner, and Remote Control.
How to use it: When a session disconnects, click `Try again`; reopen old sessions after updating and, if needed, monitor the status on the connection card.
Tip: For long tasks, write intermediate outputs to the repository; even if the connection is restored, critical results won’t depend on chat history.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Compaction, resume, transcript, and large-file session recovery fixes released
Fixed lost messages that Claude hadn't responded to, or new messages being attached to an old interruption, during repeated `/compact`, `/context`, `/resume`, and worktree switches. Resolved memory spikes during large file changes, separate saving of subagent transcripts/tool results, and CLI, SDK, and VS Code sessions getting stuck after low-memory events.
Usage details
Who can use it: Claude Code CLI, SDK, Desktop, VS Code, and cloud sessions.
How to use it: Upgrade to 2.1.323; close and reopen active sessions during the update, then check history with `/resume` after recovery.
Tip: Make large edits in separate commits; this makes it easier to restore file state even if there's a transcript recovery issue.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Cowork
GitHub and package registry write operations blocked in Cowork restricted network tasks
Tasks with restricted network access can only clone and fetch from GitHub; they cannot push, use Git LFS, or use SSH remotes. Downloads and npm audit remain available for `registry.npmjs.org`, `registry.yarnpkg.com`, and `crates.io`, while publishing, login, and other requests are rejected.
Usage details
Who can use it: Cowork tasks with restricted network access; those with Domain allowlist set to All domains and third-party deployments are unaffected.
How to use it: Check the task’s network policy; if publishing is required, use an explicitly permitted deployment environment or the All domains policy.
Tip: Have a separate CI/CD step publish to production after review, rather than publishing from the Cowork task itself.
✓ Verified by official sourceSource: Claude Desktop changelog - OtherClaude Usage Policy
Updated Usage Policy takes effect and clarifies new usage limits
The policy in effect as of November 12 adds a separate prohibition on deceptive campaigns and artificial engagement, and clarifies rules for undermining elections, weapons software and autonomous weapons actions, non-consensual surveillance, and law enforcement decisions. Human oversight and notifying affected people that AI is being used remain requirements for high-risk use; stoppability and safe-state requirements have been added for hardware that performs physical actions.
Usage details
Who can use it: All users of Claude.ai, Claude Code, API, developer platforms, cloud providers, and authorized resellers.
How to use it: Before production, reassess your use case against the Universal Usage Standards, High-risk Use Case Requirements, and Additional Use Case Guidelines sections at https://www.anthropic.com/legal/aup.
Tip: For workflows using agents or physical hardware, document that a human can intervene and that the system enters a safe state if the connection is lost.
✓ Verified by official sourceSource: 2026 Usage Policy updateSource: Usage PolicySource: Usage Policy PDF, effective November 12, 2026 - Plugin / IntegrationClaude Desktop Code
Organization connectors set to Needs approval now require approval in Code sessions
Local, SSH, and WSL Code tab sessions now require approval for connector tools set to Needs approval in the claude.ai organization policy, regardless of permission mode. In workflows other than Auto and plan mode, approval may offer the option to grant permission for the session.
Usage details
Who can use it: Claude Desktop Code; excludes scheduled runs and third-party deployments.
How to use it: Accept the approval prompt when a connector tool is called; if you need ongoing permission, select `Allow for this session`.
Tip: Scheduled tasks cannot receive human approval, so set connectors to a policy appropriate to the task's risk instead of Needs approval.
✓ Verified by official sourceSource: Claude Desktop changelog - APIClaude Code MCP
MCP SDK v1 client removed; v1 variable now enables v2 compatibility mode
`MCP_SDK_GENERATION=v1` no longer runs the old v1 client; it runs the v2 MCP client in compatibility mode, with an earlier handshake and relaxed OAuth input checks.
Usage details
Who can use it: Claude Code MCP clients and older MCP servers.
How to use it: Keep `MCP_SDK_GENERATION=v1` temporarily for older servers; test the v2 handshake and OAuth flow with newer servers.
Tip: Don't treat compatibility mode as a permanent solution; move your MCP server to the v2 handshake and current OAuth expectations.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code MCP
User approval now required to complete MCP server sign-in
The tool that completes MCP server sign-in now requires approval even in bypass and Auto mode. In `dontAsk` flows, where the user cannot be prompted, `/mcp` must be opened to sign in.
Usage details
Who can use it: Claude Code MCP server sign-ins.
How to use it: Accept the approval prompt shown when connecting an MCP server; in `dontAsk` mode, open `/mcp` and complete the sign-in flow there.
Tip: If you use `dontAsk` in automations, complete MCP authentication in an interactive session first.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code plugins
Security and visibility safeguards expanded for plugin and marketplace installs
Marketplace/plugin installation fails if a git submodule is not at the repository's recorded commit; if a plugin command writes to stderr, a warning is shown instead of success. claude.ai conversations and Cowork tasks check plugin files for potential secret keys and ask before sending them; errors in plugins enabled through managed settings are now visible in SDK/Desktop.
Usage details
Who can use it: Claude Code plugin, marketplace, claude.ai, and Cowork flows.
How to use it: Install the plugin with `claude plugin install` or `/plugin`; review warnings. Read managed plugin errors from the `init.plugin_errors` field in the SDK.
Tip: Pin marketplace commits and treat stderr output as an error in CI before distributing plugins.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Boundaries for proxy, managed env, and autocompact settings clarified
Organization settings and policy requests no longer use a proxy only through `ALL_PROXY`; `HTTPS_PROXY` is required. Managed `policyHelper` does not take environment variables from user/`--settings` files; `CLAUDE_AUTOCOMPACT_PCT_OVERRIDE` no longer applies to auto-memory and some `/btw` flows in hosted cloud.
Usage details
Who can use it: Claude Code enterprise, hosted cloud, and managed settings.
How to use it: Set `HTTPS_PROXY` for the proxy; move `policyHelper` requirements to managed `env` or the launching shell.
Tip: Test organization-wide proxy and helper changes with a single test account first; don’t rely on user settings.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Sandbox, symlink, worktree, and sensitive permission rules tightened
The Bash sandbox now rejects symlinks leading out of writable directories, git worktree operations in other sessions' worktrees on macOS/Linux, and some unsafe `glab` operations. “Don't ask again” rules that appear to contain secrets or would write to a tracked settings.local.json are now kept only for the session; startup stops when sandbox settings are invalid.
Usage details
Who can use it: Claude Code on macOS, Linux, and WSL; all sessions with security policies.
How to use it: Add the actual target path to the allowlist; perform worktree operations in the worktree where the session started. Fix invalid `--settings` JSON and restart.
Tip: Write Allow rules using the actual command and target path rather than a wildcard; test `.git`, `.claude`, and symlink targets separately.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
security-review and inline git operations now require approval first
`/security-review` now requires approval before running inline git commands in the skill in risky directories such as bare repository worktrees; this restriction applies to flows outside auto mode and bypass.
Usage details
Who can use it: Claude Code 2.1.323; terminal, SDK, and related skill flows.
How to use it: Run `/security-review` or the relevant skill and accept the approval prompt; use a normal clone to run it in a safe directory.
Tip: Instead of removing the approval step when automating security reviews, run the repository in a separate, disposable worktree.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude ve Anthropic platformları
Supported Regions Policy clarifies coverage for use in unsupported regions
Effective November 12, the policy explicitly excludes use by people physically located in unsupported regions and by organizations established or headquartered in unsupported regions. The same rule also applies to organizations directly or indirectly majority-owned or controlled by people or organizations in those regions.
Usage details
Who can use it: Anthropic apps, API, developer platform, Claude models on cloud platforms, and authorized resellers.
How to use it: Compare the organization's physical location, country of establishment, and ownership/control structure with the list at https://www.anthropic.com/legal/supported-regions.
Tip: For access through cloud or resale, include the legal entity and ownership status in compliance checks, not just the user's IP location.
- SettingClaude Desktop third-party deployments
New managed setting keys added for third-party deployments
Configurations for `autoModeClassifierModel`, `deploymentLogo`, `enforceConsoleSignInOrgList`, beta `remoteFileDownloads`, and Microsoft Purview `sensitivityLabels` have been added. Mermaid code block and Markdown previews, along with Web search/Web fetch controls in the Connectors menu, are also available.
Usage details
Who can use it: Claude Desktop third-party and Enterprise-managed deployments; some keys are available only in device profiles or beta.
How to use it: Get the latest template using Developer > Export Configuration Template; add the relevant keys to the managed configuration and update clients. For Connectors, open + > Connectors or Customize > Connectors.
Tip: Upgrade all devices to v5.11492.0 before adding new keys to the MDM profile; older Linux/Windows versions may reject unknown keys.
✓ Verified by official sourceSource: Claude Desktop changelog - FeatureClaude Code for VS Code
VS Code trust prompt and live Bash/PowerShell output added
Before the first session in an untrusted folder, VS Code now displays a Claude Code trust prompt; declining disables folder settings and MCP servers. Live output from a running Bash or PowerShell command also streams into the chat below the command card.
Usage details
Who can use it: Claude Code VS Code extension, 2.1.323.
How to use it: Open a folder in VS Code and start your first Claude Code session; trust the folder. While a command is running, watch its output below the command card in the chat.
Tip: Decline to trust repositories whose source you have not reviewed to prevent project settings and MCP servers from being used automatically.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Desktop Code
Host MCP servers run under Claude Code with built-in SSH
On Mac and Linux hosts, the built-in SSH library now runs MCP servers in `claude_desktop_config.json` under Claude Code on the host when `sshTransport: builtin` is used. Servers follow host MCP rules and stop when the session ends.
Usage details
Who can use it: Claude Desktop Code; built-in SSH, Mac/Linux host.
How to use it: Set `sshTransport` to `builtin` in the managed configuration and update the host’s MCP servers in `claude_desktop_config.json`.
Tip: Verify which user and PATH the MCP commands run with on the host; host permissions differ from those on the local machine.
✓ Verified by official sourceSource: Claude Desktop changelog - SettingClaude Desktop
Built-in browser restricts client certificates to an allowed-host list
The built-in browser and preview panels now send client certificates only to sites listed in device management's `builtinBrowserClientCertificateHosts` list. A site that requests a certificate but is not on the list will not load; `*` can be used for a proxy that requests a certificate on every site.
Usage details
Who can use it: Claude Desktop v5.11492.0; device-managed deployments.
How to use it: Add `builtinBrowserClientCertificateHosts` to the managed configuration and enter the required hostnames; use `*` if a certificate is required for every site.
Tip: Using a narrow host list instead of `*` prevents client certificates from being sent to unnecessary sites.
✓ Verified by official sourceSource: Claude Desktop changelogSource: Claude Desktop configuration changelog - FeatureClaude Code Artifact tool
.docx support added for Artifact tool asset uploads
The Artifact tool can now upload `.docx` files as assets.
Usage details
Who can use it: Claude Code 2.1.323 and later.
How to use it: Open the file upload option in the Artifact workflow and select a `.docx` file, or call the asset upload through a plugin/skill.
Tip: For large documents, extracting the relevant sections before uploading reduces context usage.
✓ Verified by official sourceSource: Claude Code changelog - FeatureClaude Cowork
File downloads added for Cowork tasks running on your computer
A Download option was added to the menu for files from tasks running on your computer; a copy of the file can be saved to a location you choose.
Usage details
Who can use it: Claude Desktop v5.11492.0; Cowork tasks running on your computer.
How to use it: Open the file menu in the task output, select `Download`, and choose a destination folder.
Tip: Preserve traceability by adding the source task and version information to the downloaded file’s name or alongside it.
✓ Verified by official sourceSource: Claude Desktop changelog - CapabilityClaude Code
CLI session deletion, logout, and usage error messages are clearer
`claude rm` and the agents view now say that they remove a conversation from the list rather than deleting it; the conversation remains available with `claude --resume`. `/logout` in a background session now logs out all sessions on the computer and deletes MCP logins and plugin secrets; cloud/Remote Control limit errors and `/usage-credits` no longer provide a web address.
Usage details
Who can use it: Claude Code CLI, background sessions, and cloud/Remote Control.
How to use it: Use `claude --resume` to continue a conversation; confirm the impact before running `/logout` in the background to log out of all sessions.
Tip: Do not run `/logout` on an automation account; it also clears credentials for other sessions.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code on the web
Fixes for cloud repositories, GitHub Enterprise, Actions logs, and scheduled task flows
GitHub Enterprise Server PR updates now connect to their own server; very large GitHub Actions logs can be downloaded. New cloud sessions opened with a repository from iOS now get a separate branch, long clone/fetch operations have more resilient timeouts, and a save check prevents the GitHub trigger from being moved incorrectly when a repository is removed.
Usage details
Who can use it: Claude Code on the web; GitHub Enterprise Server, iOS, and scheduled tasks.
How to use it: Check the repository and branch when opening a cloud session; reconnect GitHub Enterprise using your own host.
Tip: Before removing a repository from a scheduled task, disable the trigger or don’t leave the page without saving the selection of a new repository.
✓ Verified by official sourceSource: Claude Code changelog - FeatureCode Review
CSV cost export added to Code Review admin settings
A button has been added to Code Review admin settings to export review costs per repository as a CSV by day, week, or month. Reports can be generated for a single repository, a GitHub organization, or the entire organization.
Usage details
Who can use it: Code Review admin settings.
How to use it: Open Code Review admin settings, select the period and scope, and click the `Download CSV` button.
Tip: Start by exporting repository-level data; expand to the organization after identifying anomalies.
✓ Verified by official sourceSource: Claude Code changelog - Pricing / PlanClaude Code
Reset time and options are clearer for Fable and spending limits
Fable limit messages in `-p`, SDK, IDE, and cloud sessions show the reset time and options for continuing. `/usage` now preserves available limit bars in sessions using a setup token or `CLAUDE_CODE_OAUTH_TOKEN` and explains which ones are missing; the usage credit prompt also appears in the app in Remote Control.
Usage details
Who can use it: Claude Code terminal, SDK, IDE, cloud, and Remote Control sessions.
How to use it: Run `/usage`; check the reset time on the limit card and choose to wait or switch from the usage credit menu.
Tip: When the Fable limit is reached, keep in mind that even small side requests such as naming can consume quota.
✓ Verified by official sourceSource: Claude Code changelog - APIClaude apps gateway
Model, MCP, and logging behavior improved in Gateway and OpenTelemetry output
Gateway `/v1/models` returns `max_input_tokens` for models with a definite context window; OpenTelemetry reports MCP names according to the current connector directory. Fixes were made to JSON log escaping, proxy timeout, the default OTLP protocol, and preserving other fields when resource attribute input is malformed.
Usage details
Who can use it: Enterprise deployments using Claude apps gateway and OpenTelemetry.
How to use it: Upgrade the Gateway to 2.1.323; test your `/v1/models` response and OTLP collector with the new `max_input_tokens` and corrected JSON/HTTP protobuf behavior.
Tip: On the collector side, combine `max_input_tokens` with model capacity and check context before making a request.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Desktop
Import, managed settings, and authentication resilience improved
Claude (third-party) imports now preserve scheduled tasks, projects without sessions, and accepted instructions; session, project, and task remnants are cleared when copying files or folders. Slow sign-in refreshes now offer a retry without losing the message; local managed `cleanupPeriodDays` is applied when needed.
Usage details
Who can use it: Claude Desktop v5.11492.0; third-party import and managed configurations.
How to use it: Run the Import as my own flow again; upgrade devices to v5.11492.0 and put the managed cleanup setting in the device or server configuration.
Tip: After importing, review tasks while they are closed and verify the correct identity and folder permissions.
✓ Verified by official sourceSource: Claude Desktop changelog - Pricing / PlanClaude Code
An options menu is now available when usage credits are disabled or depleted
If model usage credits are disabled or depleted, Claude Code now displays a menu with options to stop, switch to usage credits, or upgrade.
Usage details
Who can use it: Claude Code 2.1.323; sessions that hit usage credit or plan limits.
How to use it: When you reach the model limit, select `Stop`, `Switch to usage credits`, or `Upgrade` from the menu that appears.
Tip: Before starting critical, lengthy tasks, use `/usage` to check when your Fable and session limits reset.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code MCP
MCP approvals now work more consistently with exact server names and tool schemas
Project `.mcp.json` approvals now match the server's exact name; differently written names require approval again. When `/mcp` excludes schemas the API would reject, it shows how many tools were excluded and why; ToolSearch also reports tools with short names that are already available.
Usage details
Who can use it: Claude Code MCP and ToolSearch.
How to use it: Match the server name in `.mcp.json` exactly to the name in the MCP registration; check the excluded-tool counts in `/mcp` and ToolSearch output.
Tip: Using a single canonical name instead of generating server names automatically reduces repeated approval prompts.
✓ Verified by official sourceSource: Claude Code changelog - APIClaude Code plugins
Mod hook and plugin tool scope are now more clearly defined
Wildcard/namespace/negated hooks on `engine.create` now only observe; named hooks are required to add or retain nouns. Tools added or removed with `tool.list` now apply to the model and all agents; invalid engine.create formats are rejected by `plugin validate`.
Usage details
Who can use it: Claude Code mod and plugin developers.
How to use it: Separate mod hooks into named `engine.create` hooks and validate with `claude plugin validate --strict`.
Tip: Run regression tests on plugins that rely on the old wildcard hook behavior before upgrading.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Cross-session message limit raised to 100,000, and unknown models now assume 1M
The number of messages sessions on the same machine can send to one another without a user prompt has increased from about 20 to 100,000; the same limit now applies to the Desktop Code tab. The default context for model IDs Claude Code doesn't recognize has increased from 200K to 1M.
Usage details
Who can use it: Claude Code 2.1.323; includes sessions with third-party providers for unrecognized model IDs.
How to use it: Use `/autocompact` for earlier compaction; set `CLAUDE_CODE_DISABLE_1M_CONTEXT=1` to revert to the 200K assumption for unrecognized models.
Tip: Set this environment variable in advance if your provider's actual context window is smaller than 1M; otherwise, `/clear` may be required in a full session.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code plugins and MCP
Plugin hot reload, MCP reconnects, and connection errors are more informative
Fixes address reauthentication prompts after MCP sign-in expires, tools not appearing after reconnect, old calls being lost when a server connects late, and hook responses over 16 MiB being silently skipped. Errors involving plugin hot reload, marketplace renames, disabled/default plugins, and long Windows paths are now handled more visibly or reliably.
Usage details
Who can use it: Claude Code plugin, MCP, Agent SDK, and `claude -p`.
How to use it: Select Reconnect from `/mcp`; after installing a plugin, check `/plugin` and the reasons shown in the output of `claude plugin list`.
Tip: Keep MCP hook output under 16 MiB and choose stable, unique server and marketplace names.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Code plugins
Plugin version compatibility is now governed by the engines field in plugin.json
The engines["claude-code"] field in plugin.json determines the range of Claude Code versions in which the plugin can be installed, updated, or loaded. Installation and updates select the newest version compatible with the range.
Usage details
Who can use it: Claude Code 2.1.323 and later; plugin developers and administrators.
How to use it: Add the supported Claude Code version range to your plugin's plugin.json under engines["claude-code"], then update with `claude plugin install` or `/plugin`.
Tip: To avoid breaking changes, narrow the lower and upper version bounds to the versions you have tested.
✓ Verified by official sourceSource: Claude Code changelog - APIClaude Code plugins
plugin validate adds TypeScript hook type checking and mod noun reporting
`claude plugin validate` type-checks the plugin's TypeScript hooks module; findings produce warnings, while `--strict` causes failure. It also reports `$` nouns added, retained, or changed by the mod's `engine.create` hooks.
Usage details
Who can use it: Claude Code plugin developers; 2.1.323 and later.
How to use it: Run `claude plugin validate`; use `claude plugin validate --strict` in CI to turn warnings into errors.
Tip: Add the `--strict` check to CI before release to catch incompatibilities in the hook API early.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Improvements to plugin-heavy sessions, installation, cleanup, and WebFetch performance
Startup delays are shorter and missing-plugin reasons are now visible in claude.ai/Desktop sessions with more than 2,000 plugins enabled; the install script no longer downloads the same version twice. WebFetch is faster and uses less memory on deep pages, cleanup treats unreadable folders as errors, and `CLAUDE_CODE_AUTOMOUNT_ROOTS` can be used when needed for Linux autofs.
Usage details
Who can use it: Claude Code Desktop, cloud, Linux, and plugin-heavy installations.
How to use it: Update the install script; set `CLAUDE_CODE_AUTOMOUNT_ROOTS` if the autofs root is multiple levels deep.
Tip: Using project-based activation instead of enabling many plugins reduces startup time and the error surface.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code Remote Control
Remote Control reconnects, permission display, and device identity have been fixed
Fixes address connection drops after Wi-Fi/VPN changes, pending terminal permissions not appearing on mobile, slots not being freed when the disk stops, and sessions incorrectly appearing to be running. A host restarted from the same folder after more than four hours now preserves the same computer identity for up to 30 days.
Usage details
Who can use it: Claude Code Remote Control and mobile/web clients.
How to use it: Restart the Remote Control host with the latest version; open the permission prompt on mobile and complete the step awaiting a response in the terminal.
Tip: Restarting the host from the same folder preserves device pairing; avoid switching folders to create a new identity.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code on the web
No repository option added for new sessions in self-hosted environments
An option has been added to start without linking a repository when opening a new Claude Code web session in a self-hosted environment.
Usage details
Who can use it: Claude Code on the web self-hosted environments.
How to use it: When creating a new session, select `No repository` in the repository picker.
Tip: Use this option for research or tool configuration tasks that don't require a repository to reduce unnecessary GitHub access.
✓ Verified by official sourceSource: Claude Code changelog - RetiredClaude Code
subagentStatusLine removed; plugin agent setting deprecated
The `subagentStatusLine` setting has been removed; subagent lines now use the default display, and the old key has no effect even if it remains in the file. The plugin's `agent` setting continues to work, but now triggers a warning at startup and in the output of `claude plugin list` and `validate`.
Usage details
Who can use it: Claude Code settings and plugin developers.
How to use it: Remove the `subagentStatusLine` dependency; replace the use of `agent` in the plugin manifest with the newly supported configuration.
Tip: Keep deprecation warnings visible in CI output and plan the migration before the next release.
✓ Verified by official sourceSource: Claude Code changelog - SettingClaude Code
Auto mode model can be selected with a managed setting for third-party providers
Support for `CLAUDE_CODE_AUTO_MODE_MODEL` has been added to managed settings; it lets you specify the model used for Auto mode safety checks in Claude Desktop sessions using third-party providers. The setting takes effect when the relevant Claude Desktop version includes this Claude Code version.
Usage details
Who can use it: Managed Claude Desktop sessions and third-party providers.
How to use it: In managed settings, set the `CLAUDE_CODE_AUTO_MODE_MODEL` environment variable to the model ID to use; deploy a Desktop version that includes 2.1.323.
Tip: Verify that the safety-check model is actually available from the provider and that your organization’s policy allows it.
✓ Verified by official sourceSource: Claude Code changelog - APIClaude Code SDK
30-second progress signal added for long-running hooks
Long-running hooks in `claude -p` and SDK sessions send a progress heartbeat every 30 seconds. This prevents a host such as Claude Desktop from assuming the turn is stuck and terminating it.
Usage details
Who can use it: Claude Code CLI `-p` mode and Agent SDK hosts; the host must include the new version.
How to use it: Upgrade the CLI or SDK to 2.1.323; on custom hosts, handle heartbeat events as connection-liveness signals.
Tip: Monitor heartbeats instead of simply increasing the host timeout; a real hang can be distinguished by a stopped heartbeat.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code
Numerous reliability fixes for VS Code, Windows, and accessibility workflows
Fixes cover the sign-in screen, CRLF diffs, dictation, queued messages, and Fable warnings in VS Code, as well as PATH, deleted working directories, and long plugin paths on Windows. Screen readers, combining characters, terminal control sequences, key chords, and expanded dialog text are now handled more accurately.
Usage details
Who can use it: Claude Code CLI, VS Code/JetBrains panels, and Windows clients.
How to use it: Upgrade to Claude Code 2.1.323; start a new session in VS Code, and reload the window if old panel state persists.
Tip: Keeping project and plugin paths short on Windows is still useful; the fix does not guarantee that every tool will work with paths up to the 260-character limit.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code on the web
Scheduled task and deletion warnings are now visible in web sessions
A startup failure notice has been added for scheduled tasks that require a sandbox when the environment they run in does not have the necessary settings. The cloud session deletion dialog now clearly states that scheduled tasks running in that session will be paused.
Usage details
Who can use it: Claude Code on the web; cloud and self-hosted sessions.
How to use it: Open the failure notice on the task card and match the sandbox requirement to the runtime environment; when deleting a session, move tasks to another session before confirming the task warning in the dialog.
Tip: Test that the required sandbox is available in an environment before attaching scheduled tasks to a session.
✓ Verified by official sourceSource: Claude Code changelog - AvailabilityClaude Code on the web
Web repository picker and sandbox branch behavior are now safer
If GitHub SSO organizations don't appear in the repository picker, the reason is shown along with a `Reconnect GitHub` link; the error for adding an inaccessible repository has also been replaced with a brief message and a reconnect button. When switching from an open folder to a web session with the VS Code sandbox enabled, VS Code no longer changes the branch automatically and explains why.
Usage details
Who can use it: Claude Code on the web and VS Code integration.
How to use it: Select `Reconnect GitHub` on the Repository picker or Git providers page; choose the target branch yourself in the VS Code dialog.
Tip: When making enterprise SSO changes, verify repository visibility on the GitHub connection page before checking Claude Code.
✓ Verified by official sourceSource: Claude Code changelog - Plugin / IntegrationClaude Desktop
Web search and Web fetch can be managed separately from the Connectors menu
Web search and Web fetch now appear as built-in tools under Connectors in the + menu and under Customize > Connectors. Each person can set them to Always ask or Blocked; `builtinToolPolicy` or `disabledBuiltinTools` set by device policy cannot be overridden.
Usage details
Who can use it: Claude Desktop v5.11492.0; only Web fetch is listed on Bedrock.
How to use it: Open + > Connectors or Customize > Connectors; select Always ask or Blocked for Web search/Web fetch.
Tip: Use Always ask for enterprise searches to keep external data access visible for every query.
✓ Verified by official sourceSource: Claude Desktop changelog - CapabilityClaude Code
WebFetch, artifact database, and file upload issues fixed
WebFetch no longer treats an empty model response as page content, no longer shifts empty cells in HTML tables, and uses less memory on deep pages. Page-by-page sorting guidance for large artifact collections, correct artifact previews, and rejection of filenames containing control characters have been added; cloud/Remote Control uploads are retried after a 507.
Usage details
Who can use it: Claude Code WebFetch, Artifact tool, cloud, and Remote Control.
How to use it: Upgrade to 2.1.323; read large artifact collections page by page, and if a cloud upload fails, watch the retry status on the card.
Tip: Provide WebFetch with the relevant sub-URL instead of a deep page to reduce both memory and context usage.
✓ Verified by official sourceSource: Claude Code changelog - CapabilityClaude Code Remote Control
Remote Control sessions show a Try again button when the computer signs out
A `Try again` button has been added to the error shown when the computer running the session signs out of Claude Code.
Usage details
Who can use it: Claude Code Remote Control.
How to use it: Click `Try again` on the error card; if the issue persists, sign back in to Claude Code on the computer and restart Remote Control.
Tip: Keep the Remote Control host up to date on machines that need a sign-in refresh.
✓ Verified by official sourceSource: Claude Code changelog