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.
Claude Haiku 5.5 joins the model list and the haiku alias now resolves to it on Anthropic's API, while Bedrock, Vertex and other providers stay on Haiku 4.5
Unclear Whether Haiku 5.5 can be picked as a model yet is not known.
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.
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
Automatic moves to a larger-context model and Fable-style model handling now check how the account is billed and whether extra usage was agreed
Unclear It is not clear what this model-specific behaviour does for a user who gets it.
Hooks that ran somewhere other than the tool can no longer change its input or result: input changes become a denial, result changes are dropped
Whether creating a cloud session sends your machine's settings now depends on several consent signals, with a notice step in the terminal
Unclear Exactly which combination of these choices causes settings to be sent.
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.
Claude Code now rejects compressed responses from MCP servers in tool containers, and MCP connect and tool listing were reworked
Unclear It is not clear what the new encoding option changes for a given server.
When an account is using overage, the 1-hour prompt cache is turned off and a cache-touch step is skipped
Unclear It is not clear which other condition must also hold for this to apply.
When local settings and CLAUDE.md files are sent to a cloud session, anything that looks like a credential is now held back
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.
Synced skills now load only when Claude Code can read the host's skill catalog, and nothing loads when it cannot
In cloud sessions, a PermissionRequest hook that is a command, script, HTTP or MCP tool hook now causes the request to be denied
Claude Code does not forward hooks to a device on Windows or when CLAUDE_CODE_DISABLE_HOOK_FORWARDING is set, and records when hooks are held back
On Anthropic's own API, Claude Code may use Claude Haiku 4.5 instead of the default small model when a condition is met
Unclear It is not clear what condition decides when Claude Haiku 4.5 is used.
Hooks from your computer are only offered to a claude --cloud session when the feature is switched on for your account
The consent that decides whether your local settings are sent to a cloud or remote session is now worked out differently
Unclear Exactly which consent choices now lead to settings being sent and which do not.
Claude Code now refuses a worktree whose .git file leads to another repository than the one its trust and settings are kept under
Claude Code now treats overage consent as needed whenever your plan has a limit end date, even if that date has passed
Unclear It is not clear whether this makes the overage consent prompt appear more often in practice.
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.
Claude Code now passes bypass permissions mode on to other sessions only if your user settings actually show you agreed to it
Claude in Chrome file uploads now reject credential files like .env, .pem, .key and .ssh, plus device paths and over-long paths
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
When Claude Code packs your configuration for a cloud environment, files and rules that look like credentials are dropped and counted
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
Pressing right on the highest effort level now stays there instead of jumping back to the lowest
Switching tabs in the fleet view now resets a second piece of selection state as well as the first
Unclear It is not clear whether this changes what happens on a tab switch or only renames existing code.
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?