The haiku model name now picks Claude Haiku 5.5 on Anthropic's own API. Bedrock, Vertex and other providers stay on Haiku 4.5. Haiku 5.5 has a 1M-token context window and its own pricing. Desktop admins can now start Claude Code through a corporate launcher with the claudeCodeProcessWrapperEnabled setting. New inferenceIdpOidc and inferenceIdpAuthFlow settings extend company sign-in to more setups, including Bedrock proxies. Admins can also set a Microsoft Foundry base URL for Claude Code sessions from the desktop app.
Four features are in the build but not switched on yet. One is a startup check for team and enterprise users. It would block startup if organization policy or settings fail to load. Another would tell Claude which of its settings files a shell command changed. New keyboard actions for moving between tabs are listed but do nothing yet.
Waiting permission requests no longer time out while you are answering an input prompt. Large repositories stall less when starting a cloud session. MCP servers no longer show an old error after their tool list refreshes successfully. Remote Control now shows the session as running again after it reconnects mid-turn. Sessions that Claude Code starts on its own now keep your Chrome on or off choice. Away and back signals from people viewing a remote session are no longer passed on.
Written by our agent from the shipped bundle, not by Anthropic.
The MCP clientSecretHelper must now print a JSON object, managed config adds OIDC sign-in and session retention, and Workspace becomes Capabilities
Settings & config
isDeferred$.tool.register accepts an isDeferred true or false option, so plugin tools can load only when found through tool search
/claude-testClaude Test gains sign-in-dependent access and messages for when it is still loading or its browser helper failed to load
ElsewhereWith CLAUDE_CODE_PEWTER_OWL_TOOL set, the affected tool path now reports whether the turn ends and what to tell you, not a response ID
New inferenceIdpOidc and inferenceIdpAuthFlow settings extend company sign-in to more setups, including Bedrock proxies
Want the reasoning? Read walks the 42 entries that probably matter to you, each one opening to what changed and why.
Read this release → Every row →Anything you can use today, anything that visibly changes, and anything worth poking at. One line each, open for detail.
The MCP clientSecretHelper must now print a JSON object, managed config adds OIDC sign-in and session retention, and Workspace becomes Capabilities
Unclear It is not clear whether these options can be used from the command-line Claude Code or only from the desktop app.
Managed settings are now prefetched by default for first-party users, fetch failures are classified, and a dark-launched org-config check is measured
Unclear It is not settled whether anything in this release uses the verdict to actually stop a session.
Admin policy now applies a bare Bash rule to PowerShell too, offers Auto mode in Code unless autoModeEnabled is false, and treats an empty folder list as none
CLAUDE_CODE_HOST_SKILL_CATALOG refuses "." and ".." and drops its child-session check, CLAUDE_CODE_DESKTOP_SKILL_SWITCHES is read, and some startup details are skipped
Unclear What the skill switches do, and in which runs the environment details are skipped, is not known.
New inferenceIdpOidc and inferenceIdpAuthFlow settings extend company sign-in to more setups, including Bedrock proxies
Unclear These settings are read by the desktop app's settings readers, and it is not clear whether the Claude Code command line also honours them.
A new managed setting, claudeCodeProcessWrapperEnabled, makes the desktop app start Claude Code through the launcher named in processWrapper
With inferenceGatewayManagedClaudeCode on, Desktop runs Claude Code in gateway mode for gateway sign-ins, turning off usage analytics
Admins of Claude Desktop third-party deployments get settings for the built-in browser and for how long sessions are kept
The managed MCP config schema gains a policy-only transport, an OIDC redirectHost option, and checks for cloud-metadata hosts and unsafe helper arguments
Admin-managed settings gain a Built-in browser group, a desktop target for requireFullVmSandbox, and the $schemaVersion and $schema keys
manifest.json#Some plugins can now list their skills in a manifest.json that switches individual skills off; a broken file loads none of them
Unclear It is not clear which plugins count as account-managed, so it is unclear which plugins read manifest.json.
A new coworkVmIpv6Enabled setting gives the Cowork VM IPv6, credential helpers can return headers, and pin changes apply without restart
Organization-managed settings for Cowork and third-party deployments gain controls for scheduled tasks, keep-awake, plugin MCP servers and sharing
Unclear It is not clear how many of these settings the Claude Code command line reads, as opposed to the desktop app.
Admins of third-party Claude Desktop deployments get managed settings for default model effort, model catalog and Chrome password managers
Desktop enterprise settings gain a Microsoft Foundry base URL, passed to Claude Code sessions as ANTHROPIC_FOUNDRY_BASE_URL
The list of policy settings groups now includes a label called "Workspace VM network", next to "Network proxy"
Unclear Nothing shows which settings, if any, belong under this label.
Admin settings for the Claude Desktop app gain sshTransport, desktopHome and dangerousMaxVersion
In organization policy settings, a group entry can now restate the settings of a named item, and each item may appear only once per group
The gateway external identity provider setting now describes a redirectHost: "localhost" option, where the return address used to be fixed at 127.0.0.1
Unclear Whether this setting applies to the Claude Code command-line tool or only to the desktop app.
A credential helper script can now be given up to 32 arguments and a separate path to use on Windows
Unclear It is not clear whether these fields affect the command-line Claude Code or only the desktop app.
Admin policy for the desktop app gains a live-apply rule for plugin marketplaces and a per-server tool policy override in managedMcpServers
For url marketplace sources, a credentialHelper may print HTTP headers as a JSON object instead of only an Authorization value
Unclear It is not clear whether helpers could already print headers before, or whether this is newly possible.
A new disableLocalConfigCache admin setting keeps only the organization ID and restrictions on disk, alongside other Claude Desktop policy changes
What would fix it?
Smaller changes and internals, grouped as the pipeline found them. Nothing is dropped, it is only further down.
10 more of these are in What probably matters to you, above.
If the managed MCP server list cannot be read, every MCP server is now blocked; entries can also be policy-only
Unclear What Claude Code does when the managed MCP server list fails to be read is not shown.
The loop that checks for new sessions to start now limits requests to free capacity, spaces out polls and waits for running hooks before exiting
Self-hosted runners now accept an optional slot count in the server's hints about starting work, and log it
The 'Gateway auth scheme' setting is now marked as running on the desktop app, alongside its existing third-party scope
modelPrefer1mContext and disableConfigDeprecationWarnings are now marked to take effect as soon as a remote policy changes them
Unclear It is not confirmed that the hot-applied mark makes these changes take effect without a restart.
Claude Code can now say it refused to start because required organization settings could not be loaded, or were refused for this sign-in
Managed settings now explain what a retired setting did, and a local address on a fail-closed setting falls back to the safe value
Unclear It is not settled whether this applies to the Claude Code command-line tool or only to code bundled with the desktop app.
Cowork admin changes to the banner and userPluginUploadsEnabled now apply to sessions that are already running
Hosted managed config now rejects an MCP server's OAuth client secret unless it is a Google client, and points others to oauth.clientSecretHelper
Unclear It is not clear how much of this checking applies to the command-line tool rather than to Desktop and the hosted control plane.
When Claude Code sets up a provider's environment, it now also blanks CLAUDE_CODE_USE_ANTHROPIC_AWS, CLAUDE_CODE_USE_ANTHROPIC_GOOGLE_CLOUD and CLAUDE_CODE_USE_GATEWAY
On third-party providers, Haiku model names are no longer skipped by the check that sets up the Sonnet default model
Unclear What the check now does for a Haiku model name is not known.
Managed tool policy patterns for MCP tools from plugins now match regardless of case, and two policy sets can be merged keeping the strictest
Unclear Whether these policy changes apply to the Claude Code command-line tool or only to the desktop app.
Managed settings now check that an organization ID is a valid UUID, and documentation links appear only for settings the desktop app reads
An admin setting that offers a prompt import now says it is off unless set, and that show needs enabled or a sign-in import
The error for a gateway host Claude Code cannot resolve now says to connect to your organization's network, without mentioning a VPN
Two gateway connection errors now say to connect to your organization's network, dropping the "(or VPN)" wording
The warning about MCP servers blocked by enterprise policy now shows whenever the set of blocked servers changes
8 more of these are in What probably matters to you, above.
The list of services Claude Code connects to over the network now includes a 'Performance timing' entry beside 'Analytics events'
Unclear It is not clear whether Claude Code actually sends performance timing data in this version or only lists it.
/api/v2/rum path on Anthropic's host#The essential telemetry endpoints now include an /api/v2/rum path on Anthropic's host alongside the Datadog hosts
The hardwareBuddyEnabled setting is now marked as for the desktop app, alongside new repository MCP and session-append entries
Unclear How any of these three additions reaches a Claude Code user is not known.
Managed settings now treat coworkVmWindowsShareFallbackEnabled as retired and read disableMobileSimulatorTools from a new place
Published verbatim by Anthropic for v2.1.293. Text is unmodified from the upstream changelog. Everything else on this page came out of the bundle instead, which is why the two lists don't match.
Of these 56 bullets, 9 name something an entry on this page also names, 15 name something no entry here does, and 32 name nothing specific enough to line up either way. The pairings are made on names both sides wrote down, a flag or a setting or a slash command, so read one as probably the same thing rather than as a fact, and read the middle number as candidates rather than as a miss count.
claude-haiku-5-5), now the default Haiku model on the Anthropic API — 1M context, $0.10/$0.50 per Mtok ($0.50/$2.50 for prompts over 100K)
Probably haiku-alias-moves-to-claude-haiku-55, haiku-alias-now-defaults-to-claude-haiku-5-5-with-third-par, claude-haiku-5-5-model-family-recognised, claude-haiku-55-model-added-with-vertex-region-override agentType to the subagentStatusLine payload, so scripts can tell custom subagent types apart
No entry names this isDeferred to $.tool.register for mods: false lists the tool's schema in the prompt from the start instead of behind tool search
Probably mods-can-register-deferred-tools, toolregister-accepts-isdeferred ← moved the session to the background; if a queued message can't move, ← now stays put and says so
Nothing to match on /model effort ←/→ wrapping past the highest or lowest level, which could accidentally save Low as a model's default effort
No entry names this #99212/model picker: pressing Right on the highest effort level wraps to Low and saves it as the default Closed
/tui disconnecting Claude in Chrome in a session started with --chrome, and ignoring --no-chrome
Probably spawned-sessions-now-forward-chrome-no-chrome SendMessage in sessions, including resumed ones, where a host, a permission rule or a --tools list removed that tool
Probably resumed-subagent-run-flag-documented-for-sendmessage-waits, orphaned-background-agent-resume-messages-depend-on-whether, agent-subagent-report-and-messaging-prompt-strings-refactore, restarted-background-agent-notices-adapt-when-the-agent-cann #92183[BUG] Desktop app disallows SendMessage, so subagents cannot be messaged or resumed Closed
--agent sessions being told a built-in tool was disabled for the whole session when only their own tool list left it out
No entry names this /clear
Probably safety-stop-count-field-on-results claude logs, stop, kill, rm and claude daemon status, stop, uninstall sometimes signing you out when your login had expired or was about to
No entry names this worker being shown as "Agent" when it starts, and the agent detail dialog's title losing the agent type once the agent finishes
Probably tool-not-found-errors-tailored-for-the-agent-tool-and-disabl, background-agent-completion-notice-omits-send-it-a-message, subagent-results-now-report-cancontinueagent Artifact("(unprintable path)") while a publish call was still streaming in
No entry names this /ultrareview upload on Linux wrongly refusing some repositories, such as one inside another checkout, over a settings file that "could not be parsed" while a sandboxed command was running
No entry names this /ultrareview upload's refusal over split-index files advising a git command that could leave git unable to read its index
No entry names this claude remote-control
No entry names this #92661PushNotification reports "Remote Control inactive" (no_transport) in sessions served by `claude remote-control` Open
#99781PushNotification reports "Remote Control inactive" in sessions started with claude rc Closed
classic.* events being skipped while the plugin hooks worker restarts, which left settings hooks to answer without them
No entry names this claude plugin test failing for mods that call $.session.append; tests can read the appended rows back with the new mock.session
No entry names this claude plugin eval refusing every Bash-granting run on Macs with Docker Desktop (links under ~/.docker/bin); the refusal now names which part of a credential store held the link
No entry names this #93368`claude plugin eval` refuses every Bash-granting evaluation under Docker Desktop's default `~/.docker` layout; `DOCKER_CONFIG` does not bypass Open
#94308`claude plugin eval` refuses every Bash-granting run on a Mac with Docker Desktop (symlinks in ~/.docker/cli-plugins) Closed
desktop policy sets Claude Desktop's built-in browser keys, such as builtinBrowserEnabled
Probably desktop-3p-config-built-in-browser-policy-keys-added #100016[BUG] Claude gateway rejects builtinBrowserEnabled in policy desktop block Open
claude agents offering bypass permissions that background sessions then ignored when consent was saved only in .claude/settings.local.json or a --settings file; it now asks for consent first, and a session that ignores bypass shows a short notice that stays
No entry names this ← backgrounding a session after 10 seconds while the prompt held unsent text (it now cancels the move) or a question was waiting for your answer
Nothing to match on ← had just been pressed to move the session to the background
Nothing to match on /feedback returning to the drafts list after Ctrl+O or Ctrl+Z while a report was sending, leaving the send impossible to cancel
Probably feedback-transcripts-redact-account-memory-compact-summaries claude purge stopping silently (exit 0, or a hang in a terminal) when a file or folder could not be deleted; it now deletes the rest, lists what it could not delete, and exits 1
No entry names this >> and << on a line of only spaces leaving the cursor past the end of the line, where a following x deleted nothing
Nothing to match on V then d) the cursor lands on the first non-blank, and . after it acts on the cursor's line
Nothing to match on /loop wakeup or scheduled task; Claude is no longer told, and the session stays asleep
Probably org-managed-config-schema-gains-sharing-endpoint-scheduled claude_code.at_mention logging to emit at most 100 agent and 100 MCP-resource events each time a prompt is read
No entry names this A model matched these bullets to the GitHub issues they fix, so a link can be wrong.
1 added and 1 removed, of 218 lines, about 9 words, in the prompt 14 of 27 arms receive. 3 other prompts also changed. 1 new prompt appeared. The appended system-reminder blocks moved: 1 line added.
Claude Code, interactive mode
No prompt capture for v2.1.293, so this release's prompt surface is unknown.
718 documentation changes were recorded within 24 hours either side of this release, nearest first. The closest 12 are below. They're here because they happened near this release in time. That's not a claim that this release caused the edit, or that the page documents anything in it.
The 37 literal strings found in the bundle, with the number of entries that name each one. Picking one searches for it. A name is here because this build's code mentions it, which is not the same as it working or being finished.
What's wrong with this entry?