Anthropic Release Notes

• Added directory path suggestions to /cd, matching /add-dir behavior
• Added a /doctor check that proposes trimming checked-in CLAUDE.md files by cutting content Claude could derive from the codebase
• /commit-push-pr now auto-allows git push to the repo's configured push remote (remote.pushDefault, or the sole remote when only one is configured) in addition to origin
• Gateway: /login now supports Anthropic-operated public gateway endpoints
• EnterWorktree now asks for confirmation before entering a git worktree outside the project's .claude/worktrees/ directory
• Background agents now upgrade to a new version in the background right after a Claude Code update, instead of paying a slow stale-session upgrade when you attach
• Fixed an expired login failing every model with a misleading "There's an issue with the selected model" error instead of prompting to run /login
• Fixed claude --resume and --continue not responding to keyboard input on startup
• Fixed MCP servers configured via --mcp-config or .mcp.json ignoring a per-server request_timeout_ms, which caused long-running MCP tool calls to time out at the 60s default in fresh sessions
• Fixed CLAUDE_CODE_EXTRA_BODY being silently ignored by claude agents / --bg background workers; the shell-exported override now follows the dispatching session
• Fixed OAuth MCP servers requiring manual re-authentication after a single failed token refresh …

• Dreams (research preview) now supports Claude Fable 5 and Claude Sonnet 5. See Supported models.
• We've expanded the Access Transparency documentation of cmek_preserve events with a filter example, an example event payload, and two preservation reason codes (policy_violation_investigation, csae_report). The documentation now also clarifies that a preservation event is written whether the preservation was initiated by a human reviewer or an automated safety pipeline. See CMEK content preservation.

A new way to reflect with Claude

Your monthly recap is a new feature at Settings > Reflect that shows you the topics you spent time on, your most active day and peak hour, and observations about how you work with Claude. It's in beta on Free, Pro, and Max plans on the web and Claude Desktop, and requires memory to be on. Alongside it, Settings > Time and focus lets you set optional break reminders and quiet hours. For more information, refer to See your monthly recap and Set break reminders and quiet hours.

• Added an auto mode rule that blocks tampering with session transcript files
• Fixed --json-schema silently producing unstructured output when the schema was invalid, and schemas using the format keyword being rejected
• Fixed a message sent while Claude was working being silently lost when the turn ended at the --max-turns limit
• Fixed Windows worktree removal deleting files outside the worktree when an NTFS junction or directory symlink existed inside it
• Fixed background agents staying shown as "failed" or "completed" in the agent list after being resumed with SendMessage
• Fixed background jobs flipping from "needs input" back to "working" in the agent list when the agent's turn contained no readable text
• Fixed claude attach erroring when a background agent was mid-upgrade restart instead of waiting for it to come back
• Fixed session-to-PR linking missing a PR created in a Bash call whose output exceeded the 30K inline limit
• Fixed claude mcp add-from-claude-desktop getting stuck when a server name contains unsupported characters; invalid names are now reported and remaining servers still import
• Fixed a plugin LSP server that fails to initialize preventing a valid LSP server from another plugin handling the same file extension
• Fixed a Windows crash when the directory Claude was launched from is deleted, locked, or unmounted while a command is running
• Fixed a crash when a file watcher was closed while a directory scan was still in flight …

• You can now set an expiration when you create an API key or an Admin API key in the Claude Console. Choose a preset, a custom duration, or Never. For keys with a lifetime of at least 7 days, Anthropic emails the creator before expiration. Existing keys are unaffected. The Admin API reports each key's expiration in the expires_at field. See Authentication.

• Added a warning when your login is about to expire, so you can re-authenticate before background sessions are interrupted
• Added a grey ⏸ badge to the footer when in manual permission mode, making the active mode always visible
• Added the session's additional working directories to MCP roots/list, with notifications/roots/list_changed sent when the set changes
• Fixed opening or switching background agent sessions on macOS stalling for 15–20 seconds due to a false low-memory detection (regression in 2.1.196)
• Fixed background sessions becoming permanently unresponsive to attach, replies, and stop when the daemon's session token went stale — the session now recovers automatically
• Fixed returning to claude agents silently stopping running subagents and re-running the prompt from scratch — their work now carries over
• Fixed a memory and per-turn CPU regression in interactive sessions: the context-usage indicator no longer re-analyzes the entire transcript after every turn
• Fixed background agents inheriting a stale PATH from the daemon instead of the dispatching shell, causing missing tools on Windows
• Fixed background and agent-view sessions dropping a shell-exported ANTHROPIC_BASE_URL, which sent API keys to the default endpoint and failed with 401
• Fixed Bash failing with "argument list too long" in repos with many git worktrees
• Fixed worktree-isolated subagents sometimes running shell commands in the parent checkout instead of their own worktree …

Claude Cowork on web and mobile

Claude Cowork is now available on web and mobile in addition to desktop. We are rolling this capability out over the next several weeks starting with the Max plan, with more plans to follow. Cowork runs your sessions remotely (in beta), so your sessions and files are saved to your Claude account and go where you go, on any device. Work continues when you close your laptop, and scheduled tasks run with no device online. Chat and Cowork also share one home now, with one place for your projects and artifacts across both. For more information, see Use Claude Cowork on web, desktop, and mobile.

Write tools for the Microsoft 365 connector

The Microsoft 365 connector now goes beyond search. With write tools enabled, Claude can draft, send, and organize email, manage calendar events, update mailbox settings, and create and update files in OneDrive and SharePoint. Read and search tools work as before, and Teams remains read-only. Before members can use write tools, a Microsoft Entra administrator needs to consent to the updated permission set and an admin needs to enable them for the organization. For more information, see Set up the Microsoft 365 connector and Connect to Microsoft 365.

• Added a "Dynamic workflow size" setting in /config for controlling how large Claude generally makes dynamic workflows (small/medium/large agent counts) — an advisory guideline, not an enforced cap
• Added workflow.run_id and workflow.name OpenTelemetry attributes to telemetry emitted by workflow-spawned agents, so a workflow run's activity can be reconstructed from OTel data
• Fixed a crash in the inline Ctrl+R history search when accepting or cancelling while the search was still scanning the history file
• Fixed /rename on background sessions being reverted when the job restarts, which broke addressing the session by its new name
• Fixed transient mTLS handshake failures when settings were re-applied during an in-place client certificate rotation
• Fixed commands sent from Remote Control (mobile/web) into an interactive session failing with "Unknown command"
• Fixed images and files sent from the Remote Control mobile or web app without a caption being silently dropped
• Fixed the sign-in URL printed by claude auth login and claude mcp login --no-browser not being reliably clickable when it wraps over SSH — it is now emitted as a single hyperlink
• Fixed opening a chat from claude agents sometimes failing with "currently running as a background agent" followed by a worker crash/respawn loop …

• Changed AskUserQuestion dialogs to no longer auto-continue by default; opt into an idle timeout via /config
• Changed the "default" permission mode to "Manual" across the CLI, --help, VS Code, and JetBrains; --permission-mode manual and "defaultMode": "manual" are accepted alongside default
• Fixed a crash at startup when disabledMcpServers or enabledMcpServers in .claude.json is set to a non-array value
• Fixed background sessions silently stopping mid-turn after sleep/wake or when reopening a stalled session
• Fixed background sessions re-running a turn cancelled with Esc after a stall respawn
• Fixed background agents never starting again after a crash left a stale daemon.lock whose PID the OS reused
• Fixed background-agent daemon handover so a reinstalled older build can no longer take over the daemon; build recency is now judged by the version's embedded build timestamp
• Fixed background-agent roster issues: transient corruption permanently disabling orphan cleanup, older binaries not preserving fields written by newer versions, and socket auth tokens being stripped during daemon restarts
• Fixed subagents cut off by a rate limit before producing any text output returning an empty result instead of failing cleanly
• Fixed control bytes from background-agent output reaching the terminal in the agent view
• Fixed claude agents --plugin-dir <dir> not showing the plugin's agents and skills in the agent view when the flag is placed after agents …

• Stacked slash-skill invocations like /skill-a /skill-b do XYZ now load all leading skills (up to 5), not just the first
• Fixed SSL certificate errors (TLS-inspecting proxies, missing NODE_EXTRA_CA_CERTS, expired certs) burning retries before showing actionable guidance — they now fail immediately with the fix hint
• Fixed streaming responses being discarded when the API emits a mid-stream overloaded/server error after partial output — the partial is now kept with an incomplete-response notice
• Fixed subagents cut off by a rate limit or server error silently failing instead of returning their partial work to the parent
• Fixed subagents reporting API errors (e.g. usage limit reached) as successful results — the error is now reported to the parent agent
• Fixed the background-agent daemon on Linux killing itself and every running agent every ~50 seconds after an unclean shutdown left a corrupted worker record
• Fixed background agents failing to cold-start over SSH on macOS with "Could not switch to audit session" (regression in 2.1.196)
• Fixed claude stop being silently undone when it raced a background-agent respawn — the respawn now honors the stop
• Fixed background job progress indicators stalling for minutes while the job ran long commands
• Fixed background sessions on memory-starved machines showing a generic error — they now indicate low memory and suggest freeing resources …

• We've added the agent-memory-2026-07-22 beta header, which changes how listing memories (GET /v1/memory_stores/{memory_store_id}/memories) behaves: results are returned in a stable, server-defined order and the order_by and order parameters are ignored; depth accepts only 0, 1, or being omitted (other values return a 400 error); and path_prefix must end with / and matches whole path segments instead of a substring. Page cursors issued without the header aren't valid with it, so restart from the first page when you adopt it. On memory store endpoints, agent-memory-2026-07-22 replaces managed-agents-2026-04-01; sending both returns a 400 error. On July 22, 2026, the managed-agents-2026-04-01 header adopts the same list behavior. See Beta headers.
• The Python (0.116.0), TypeScript (0.110.0), Go (1.56.0), Java (2.48.0), Ruby (1.55.0), PHP (0.36.0), C# (12.35.0), and CLI (1.16.0) SDKs now send agent-memory-2026-07-22 on all memory store calls instead of managed-agents-2026-04-01. If your code passes betas explicitly on memory store calls, replace managed-agents-2026-04-01 with agent-memory-2026-07-22 there rather than adding a second value.

• Subagents now run in the background by default, so Claude keeps working while they run and is notified when they finish (previously a gradual rollout)
• Claude in Chrome is now generally available
• Added background agent notifications in claude agents — sessions that need input or finish now fire the Notification hook (agent_needs_input / agent_completed)
• Added /dataviz skill for chart and dashboard design guidance with a runnable color-palette validator
• Gateway: added Claude Platform on AWS (anthropicAws) as an upstream provider; model-not-found responses now advance the failover chain
• Background agents launched from claude agents now commit, push, and open a draft PR when they finish code work in a worktree, instead of stopping to ask
• The built-in Explore agent now inherits the main session's model (capped at opus) instead of running on haiku
• Subagents and context compaction now inherit the session's extended thinking configuration, improving output quality on delegated tasks
• Fixed brief network drops mid-response aborting the turn — transient errors like ECONNRESET now retry with backoff instead of failing
• Fixed excessive background classifier requests when sandboxed processes repeatedly accessed the same network host
• Fixed background tasks in web, desktop, and VS Code task panels getting stuck on "Running" after they finish or after resuming a session …

• We've launched Claude Sonnet 5 (claude-sonnet-5), the next generation of our Sonnet model family, at introductory pricing of $2 / $10 per MTok (made the standard price on August 10, 2026). Claude Sonnet 5 supports a 1M token context window, 128k max output tokens, and the same set of tools and platform features as Claude Sonnet 4.6, except Priority Tier, which is not available on Claude Sonnet 5. Three behavior changes apply when migrating: adaptive thinking is now on by default; manual extended thinking (thinking: {type: "enabled", budget_tokens: N}) is removed and returns a 400 error (it was deprecated on Sonnet 4.6); and setting sampling parameters (temperature, top_p, top_k) to non-default values returns a 400 error. Claude Sonnet 5 also uses a new tokenizer that produces approximately 30% more tokens for the same text. The exact increase depends on the content and workload shape. See What's new in Claude Sonnet 5 for details and migration guidance. For behavioral differences and model-specific prompting patterns, see Prompting Claude Sonnet 5. …