Admins running the bundled gateway can now set one shared monthly spending limit for a whole access group. The new blockReadsExemptPaths setting lists folders Claude Code may still read when reads outside your working directories are blocked. Claude Code can now publish an artifact as a Claude doc. It also reports whether a lasting subscription to that doc's updates was set up. In Cowork, the loops Claude Code starts no longer receive your memory. A hidden --gateway-json option on claude auth login lets the VS Code extension handle Cloud gateway sign-in.
Several features are in the build but not switched on yet. Remote sessions can track and resend conversation lines they still owe after a restart, but only when this is switched on remotely. Files uploaded to a project can be attached as text context, behind a flag that defaults to off. Claude Code can list MCP server requests that are waiting for your input, also behind an off-by-default flag. Long Bash output previews can keep both the start and the end, with the full text saved to a file. Numbered menus can be set to wait for Enter instead of picking after a short pause.
File searches no longer hang when ripgrep fails to exit after a timeout. Stray connections can no longer knock you off a background session. Sending a message immediately no longer cuts off an automatic compaction that is in progress. Resuming a copied session no longer shows a stray cut-off tool call. When Claude Code runs as a tool server, a settings file that fails to load no longer drops its permission rules. Shell snapshots now save your aliases in a case where they used to save nothing.
Written by our agent from the shipped bundle, not by Anthropic.
A new held-message recognition feature can be turned off with CLAUDE_CODE_DISABLE_HELD_MESSAGE_RECOGNITION, which is also passed to remote sessions
CLAUDE_CODE_SORTED_OTTER can now override the remote tengu_sorted_otter switch, and one function moves from that switch to tengu_quiet_pike
claude auth login gains a hidden --gateway-json option that runs Cloud gateway sign-in as JSON lines for another program, such as the VS Code extension
Managed settings gain policy_mode: layered, which merges several matching policies instead of applying only the first one, with limits to protect deny rules
A background session's socket can now hold new connections until they send something, so a silent stray connection cannot kick off the attached viewer
Sessions & agentsWant the reasoning? Read walks the 37 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.
Managed settings gain policy_mode: layered, which merges several matching policies instead of applying only the first one, with limits to protect deny rules
Restricted mode now blocks reads outside the working directories, searches and Chrome uploads are fenced too, and blockReadsExemptPaths lets chosen paths through
Unclear Under some conditions the exempt list is treated as empty, and it is not clear what those conditions are.
The bundled gateway can now cap monthly spend for a whole group, rejects requests when the shared pool runs out, and documents the group_pool limit header
Claude Code adds groundwork for server-side auto mode checks when a host such as Claude Desktop manages the provider gateway, plus gateway login reporting
Unclear It is not clear whether meeting these three conditions turns on server review for host-managed providers.
Remote session code gains renewSessionTokens and isThawing hooks, but isThawing always returns false and the function receiving them does nothing
Unverifiable self-named and looped cross-signed CA certificates are now dropped, two env vars keep them, and certificate errors explain missing issuers
Unclear Which certificates are dropped, and whether dropping happens by default, is not settled.
After sign-in, Claude Code can now load a dynamic MCP setup and add a server, unless strict or managed MCP settings apply
Unclear It is not clear which server gets added or what decides whether one is added.
The bundled gateway supports input_tagging for Bedrock guardrails, requires it to match across upstreams, and checks every model named in a request
Unclear Which values input_tagging accepts is not stated.
Claude Code now has a sign-in flow for a Cloud gateway that asks for a URL, asks you to trust it and confirms the account
Unclear How a user starts this sign-in flow, and whether it is available yet, is not stated.
What would fix it?
Smaller changes and internals, grouped as the pipeline found them. Nothing is dropped, it is only further down.
5 more of these are in What probably matters to you, above.
After failed or killed commands the Bash tool can now show Claude the output's end and memory-kill notes, and analytics record programs and test results
Unclear It is not stated what decides whether the end-of-output and out-of-memory notes are switched on.
With a gateway set, auto mode now shows a notice when gateway checks are not working and it is using its built-in check, which sends extra billed requests
The gateway can now wrap message content in Bedrock guardrail tags, and refuses requests with too many or too deeply nested model fields
Unclear How the guardrail tagging mode is chosen is not stated.
A subagent with no valid effort level of its own now gets one worked out from its permission settings instead of none
Unclear Which effort level the permission settings produce is not known.
Auto mode allow rules are now gathered per settings source, and command-line allow rules are merged with managed policy
Unclear It is not stated how command-line allow rules and policy allow rules are merged.
When an administrator's settings refuse a stored login, Claude Code can now report the reason instead of a fixed error
Unclear It is not clear what message a refused user now sees, or when the refusal reason appears.
Claude Code can now hold back a saved login and explain why: an admin setting, missing organization settings, or a needed restart
Setting any of four OpenTelemetry attribute limit variables now switches how Claude Code records the events it logs about its own use
Claude Code now resolves ANTHROPIC_ORGANIZATION_ID whenever no federation source location is set, dropping an earlier extra condition
Unclear The condition that was removed is not described, so it is unclear which federation setups behave differently now.
Gateway configs now require the same guardrail.input_tagging on every Bedrock upstream, and remote-session messages wait for admission
Claude Code now names three specific reasons a sign-in token fails or is revoked: account not a member, no organization, no account
Unclear It is not stated whether the message you see when login renewal fails changes.
mcp_authenticate now checks organization policy again just before sign-in starts, and stops if your Claude account changed meanwhile
Claude Code now recognises more Bedrock and Vertex errors as a refusal to give you access to a model
With client or custom CA certificates, Claude Code now closes a reused connection when certain connection settings have changed since it opened
4 more of these are in What probably matters to you, above.
The two browser messages on the Cloud gateway sign-in screen are now kept as shared text instead of being written into the screen
Claude Code's usage data now records finer timings for preparing attachments and for streaming text in remote sessions
Claude Code now merges the catch-all base policy into each managed policy in one step instead of merging its parts separately
When Claude Code refuses its stored copy of remote settings, it now records which helper tier that copy came from
Claude Code now records which account a policy limit decision belongs to and checks it again when the account changes
Policy limit lookups now return an extra field, and an extra step can run when a permission hook's allow is ignored
Anthropic has not published official notes for v2.1.315 yet. This section updates automatically when the entry appears in the upstream changelog. Everything else on this page came out of the bundle instead, which is why the two lists don't match.
4 prompts changed.
Claude Code, interactive mode
12 prompt changes in this release could not be quoted from the build, so no entry on this page describes them.
629 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 44 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?
