Anthropic Release Notes

• Improved Agent tool subagent_type matching to accept case- and separator-insensitive values (e.g. "Code Reviewer" resolves to code-reviewer)

• Updated agent color palette

• Fixed /goal silently hanging when disableAllHooks or allowManagedHooksOnly is set 6 now shows a clear message instead of an indicator that never resolves

• Fixed a regression in settings hot-reload where symlinked settings files caused misattributed change events and spurious ConfigChange hooks

• Fixed claude --bg failing with "connection dropped mid-request" when the background service was about to idle-exit

• Fixed background service startup failing on machines with enterprise endpoint security by allowing more time

• Fixed remote managed settings not retrying on 401 6 now retries once with a force-refreshed token

• Fixed managed extraKnownMarketplaces auto-update policy not being persisted to known_marketplaces.json

• Fixed /loop scheduling redundant wakeups to poll for background tasks that already notify on completion

• Fixed a recurring event-loop stall on Windows when a missing executable (e.g. gh) triggered synchronous where.exe re-spawns on every check

• Fixed Read tool calls failing validation when offset is passed as a whitespace-padded or +-prefixed string

• Fixed native terminal cursor not staying at the input caret when the terminal loses focus

• Plugins now warn when a default component folder (e.g. commands/) is silently ignored because plugin.json sets the matching key. Shown in /doctor, claude plugin list, and /plugin.

Original source

We’re releasing 20+ new MCP connectors that link Claude to the software that the legal industry runs on and 12 new plugins tailored to specific legal work and practice areas.

Earlier this year we released our first legal plugin, and in the months since, legal professionals have become the most engaged Claude Cowork users of any knowledge-work function. We’re now building on that with a much larger set of tools.

Legal work runs on a specific technology stack: contract lifecycle systems, research platforms, document management, e-discovery, data rooms, firm-specific precedents, and much more. Claude now connects to all of it through several key building blocks. First, MCP connectors bring your legal work (the documents, communications, and records tied to specific matters) into Claude. Secondly, practice-area plugins package the tasks that lawyers run most often. And finally, because both are built on open protocols, firms and in-house teams can customize Claude to match the way they actually practice.

Today we’re introducing 20+ new MCP connectors that link Claude to the software the legal industry already relies on, and 12 new plugins tailored to specific legal work and practice areas. And finally, we're partnering with the Free Law Project, the Justice Technology Association, and others working to put legal help within reach of people who can’t currently access it.

Claude works where legal teams work

Claude meets legal teams where they are, working directly inside Microsoft Word, Outlook, Excel, and PowerPoint while carrying context across all four apps. A redline finished in Word doesn’t need to be re-explained when it becomes a cover note in Outlook, a closing checklist in Excel, or a board summary in PowerPoint.

In Word, Claude skills—reusable instructions that encode a team's playbooks and standards—handle drafting, redlining, and clause-by-clause comparisons against those playbooks, tracking every change and explaining the reasoning behind it. They also take on the rote work in between every turn: scrubbing internal comments before a draft goes to the counterparty, running a final formatting check on an execution copy, and pulling fallback language from approved playbooks.

In Outlook, Claude triages incoming matter work: flagging contract requests, drafting responses and cover notes, and scheduling follow-ups so nothing pile ups.

In Claude Cowork, the same connectors and plugins are available for work that spans many documents: triaging a batch of contracts, clearing a product feature for launch, and drafting a note on regulatory developments for the board. Scheduled tasks can automate recurring work such as weekly regulatory update sweeps or intake triage.

And with Projects, matter teams get a persistent workspace where precedents and prior drafts are retained across every conversation.

New connectors across the legal stack

New MCP connectors let Claude interact with the systems that legal teams already rely on.

Contract lifecycle and drafting:

• Definely, which gives live, deterministic access to contract structure for review: resolve definitions, validate cross-references, map dependencies, and run structural diffs to see how edits propagate across an agreement;
• Docusign, which connects Claude to your agreement data so you can quickly surface key terms like renewal dates and obligations, and orchestrate agreement workflows across the contract lifecycle, from drafting through signature and post signature management;
• Ironclad, which lets Claude access your contract repository and workflows and ask questions about contracts in plain language, with results automatically scoped to each user's permissions.

Deal rooms and transaction documents:

• Box, which connects Claude to content stored in Box to search and access files, query documents, create or update content, and extract metadata fields, while enforcing existing Box security and access policies;
• Datasite, which connects Claude to your Datasite virtual data room—the secure workspace where thousands of M&A deals are facilitated annually—to set up folder structures, invite users, search documents, track buyer Q&A, and audit data room readiness.

Document management:

• iManage, a knowledge work platform, gives Claude permission-bound, auditable access to governed iManage content, including matter history, documents, and institutional knowledge, eliminating the need for bulk exports or custom integrations;
• NetDocuments, which lets Claude search and retrieve documents from your NetDocuments repository and draft new documents based on your precedents, with full respect for your organization's permissions and governance policies.

Expert networks and skills:

• Lawve AI, which offers a curated library of legal AI skills written by practicing lawyers, in-house counsel, and legal technologists, searchable from inside Claude;
• The L Suite, which offers two MCP connectors from their leading in-house counsel community: (1) Lloyd, which allows The L Suite members to connect Claude with the Braintrust member platform; and (2) TopCounsel, which helps any in-house counsel find the right outside counsel for a specific matter based on The L Suite's proprietary dataset and ranking algorithm.

E-discovery and review:

• Consilio, which puts a client’s own live matters and Consilio’s Aurora Legal AI at Claude's fingertips, with every response scoped to what the user is already entitled to see;
• Everlaw, which provides a litigation platform, lets Claude search, organize, and retrieve documents from Everlaw projects using metadata, keywords, and document types, with direct review links;
• Relativity, which lets Claude stand up matters, shape workspace schema, govern access, and analyze usage in its AI platform for legal data intelligence, RelativityOne.

Fiduciary-grade workflows:

• Thomson Reuters, which connects Claude to CoCounsel Legal, a fiduciary-grade system for end-to-end drafting, research, review, and validation across all major practice areas, serving as an AI assistant for high-stakes legal work, grounded in Westlaw primary law, Practical Law guidance, KeyCite, and your own documents, with transparent and verifiable outputs.

Legal research and case law:

• Legal Data Hunter, which gives Claude access to the world's fastest growing legal corpus: 31M+ documents from 160+ jurisdictions, including EU consolidated law, case law from supreme and constitutional courts, and official doctrine;
• Midpage, which connects Claude to a database of case law for complex legal research, opinion review, and work product, with everything hyperlinked to real sources for easy verification;
• Trellis, which gives Claude direct access to the largest state trial-court dataset in the US, including dockets, rulings, verdicts, and filings, for judge and opposing-counsel analytics and motion drafting.

Legal AI assistants:

• Harvey, which brings Harvey's legal intelligence into Claude, supporting general legal inquiries, analysis over Vault projects, and research questions for select knowledge sources;
• Solve Intelligence, which connects Claude to patent and non-patent literature, legal texts, SEP technical standards, and the open web for prior-art search, claim mapping, and patent drafting.

Public service

• BoardWise, which guides licensed professionals facing state board matters: helping them understand deadlines, navigate their situation, and draft structured response letters tailored to their jurisdiction;
• Courtroom5, which provides legal guidance to the roughly 80% of civil litigants who appear in court without an attorney, with jurisdiction-aware case intake, deadline calculation, and next-step guidance across all 50 states;
• Descrybe, which gives Claude legal-research tools for working with primary law: search cases by concept or citation, check treatment status, find citing authorities, and verify quoted language;
• Free Law Project, which connects Claude to CourtListener's millions of US court opinions, PACER dockets, judge profiles, oral arguments, and citation data.

Practice-area plugins

Legal work looks different depending on the seat you're in. We're releasing 12 practice-area plugins (download them from the Legal Marketplace, here), each built around a specific legal role. Every plugin starts with a short setup interview that learns your practice: your playbook, your escalation chain, your risk calibration, your house style, so Claude’s answers are not generic but rather tailored for your team. These include:

• Commercial Legal reviews vendor agreements and NDAs against your playbooks and routes escalations with a plain-language summary for business stakeholders.
• Corporate Legal handles M&A: diligence across the data room, disclosure schedules, board consents, and the closing checklist. It can be configured for board work, public-company governance, or entity compliance.
• Employment Legal covers hires, terminations, worker classification, leave deadlines, and investigations, and drafts policies with state-specific rules built in.
• Privacy Legal reviews DPAs against your playbook, triages PIAs and DPIAs, prepares DSAR responses within statutory timelines, and flags gaps between written policy and actual practice.
• Product Legal runs launch reviews against your internal framework, checks marketing claims for substantiation, and answers risk questions from teams across the business.
• Regulatory Legal monitors regulatory developments, filters them to your materiality threshold, compares new rules against your policy library, and tracks gaps and comment deadlines.
• AI Governance Legal triages AI use cases against your governance tiers, runs impact assessments, reviews vendor AI terms, and can draft a starting AI policy.
• IP Legal conducts trademark clearance and freedom-to-operate triage, drafts and responds to cease-and-desist letters, handles DMCA takedowns and open-source compliance, and screens invention disclosures.
• Litigation Legal manages matter intake and portfolio tracking, legal holds, demand letters, subpoena triage, chronologies, deposition preparation, privilege logs, and brief drafting.
• Law Student provides Socratic drilling, case briefs, IRAC grading, and bar preparation with jurisdiction-specific distinctions.
• Legal Clinic manages client intake, deadline tracking, case memos, and the supervisor review queue.
• Legal Builder Hub finds and installs community-built legal skills from public registries, running a security review, license check, and freshness check on every install and update.

Each agent template can be installed in Cowork or Claude Code with a click, and produces outputs that match institutional drafting standards. A subset of these (Commercial Legal, Corporate Legal, Litigation Legal, Product Legal, Litigation Legal) are also available as cookbooks that can be deployed as Managed Agents in the Claude Platform for programmatic use. Teams can layer on their own precedents and playbooks to customize the skills.

Every legal organization works differently, and no single set of plugins can cover every practice. The plugin and skill ecosystem are open protocols, and early contributors including Box, Legal Quants, Lawve AI, and Thomson Reuters have already shipped skills, plugins, and style conventions of their own. Any partner can submit connectors and skills through the Directory.

Democratizing access to legal services with AI

Legal services are out of reach for many people and small businesses, and the gap is widening. We’re working with the Free Law Project, Justice Technology Association, and other legal aid and Public Service organizations to help make legal services more affordable and available.

Qualifying legal aid clinics, public defenders, and nonprofit legal services organizations can gain access to significantly discounted pricing through the Claude for Nonprofits program. Free and low-cost tools from BoardWise, Courtroom5, Descrybe, and Free Law Project are available to Claude users via MCP connectors as well.

"Most people don't know they have legal rights until it's too late to use them. Claude can now meet them where they are — in the moment they're scared and searching for answers."

• Sonja Ebron, CEO & Co-Founder, Courtroom5

Trusted across the legal industry

Firms and in-house teams have moved from testing Claude to running their practice on it — and the legal tools they rely on are increasingly built on Claude too. At our Briefing: Enterprise Agents in February, Thomson Reuters showcased CoCounsel rebuilt on the Claude Agent SDK; with today's release, that integration runs both ways. Harvey, Solve Intelligence, and others below are doing the same.

These updates build on Claude Opus 4.7, our most capable publicly available model for legal reasoning and long-document work.

Here’s what legal teams and ecosystem partners have told us about working with Claude:

[Multiple testimonials from legal industry leaders praising Claude's integration, capabilities, and impact on legal workflows and AI transformation.]

Getting started

The new connectors and practice-area plugins are open source and available in Claude Cowork. Enterprise admins can enable them in your workspace settings. Learn more here or contact our sales team.

Register for our launch webinar to see the new features in action – we'll share live product walkthroughs, and cover how law firms and in-house teams can get the most out of Claude and the connected ecosystem. Builders can also explore community-maintained skills via Legal Quants and Lawvable.

For legal aid and access-to-justice organizations who are interested in partnering, get in touch via our Nonprofits program.

Original source

• Added agent view (Research Preview): a single list of every Claude Code session — running, blocked on you, or done. Run claude agents to get started. See https://code.claude.com/docs/en/agent-view
• Added /goal command: set a completion condition and Claude keeps working across turns until it's met. Works in interactive, -p, and Remote Control. Shows live elapsed/turns/tokens as an overlay panel
• Added /scroll-speed command to tune mouse wheel scroll speed with a live preview
• Added claude plugin details <name> to show a plugin's component inventory and projected per-session token cost
• Added transcript view navigation: ? for keyboard shortcuts, {/} to jump between user prompts, v to toggle shortcut panel
• Added hook args: string[] field (exec form) that spawns the command directly without a shell, so path placeholders never need quoting
• Added hook continueOnBlock config option for PostToolUse — set to true to feed the hook's rejection reason back to Claude and continue the turn
• MCP stdio servers now receive CLAUDE_PROJECT_DIR in their environment, matching hooks. Plugin configs can reference ${CLAUDE_PROJECT_DIR} in commands
• Compaction prompt now asks the model to preserve sensitive user instructions
• /mcp Reconnect now picks up .mcp.json edits without a restart, and shows the HTTP status and URL when reconnecting fails
• /context all per-skill token estimates now account for the model's tokenizer and show rounded values
• claude plugin install <name>@<marketplace> now auto-refreshes the marketplace and retries before reporting a plugin as not found
• /plugin installed-plugin details now show hook event names and MCP server names cleanly
• /context now shows the providing plugin's name for plugin-sourced skills
• Remote MCP server reconnect retry on transient failures is now enabled for all users
• API requests from subagents now carry x-claude-code-agent-id / x-claude-code-parent-agent-id headers, and claude_code.llm_request OTEL spans include agent_id / parent_agent_id attributes
• Remote Control, /schedule, claude.ai MCP connectors, and notification preferences are now disabled when ANTHROPIC_API_KEY / apiKeyHelper / ANTHROPIC_AUTH_TOKEN is set, even if a Claude.ai login also exists. Unset the API key to use these features
• Fixed a deadlock where expired credentials and the forceRemoteSettingsRefresh policy setting blocked claude auth login/logout/status with no way to recover
• Fixed autoAllowBashIfSandboxed not auto-approving commands with shell expansions like $VAR and $(cmd)
• Fixed a bug where a hook writing to the terminal could corrupt an on-screen interactive prompt; hooks now run without terminal access
• Fixed unbounded memory growth when an HTTP/SSE MCP server streams non-protocol data — response bodies now capped at 16 MB per SSE frame
• Fixed Skill(name *) permission rules — the wildcard form now works as a prefix match, matching Bash(ls *) behavior
• Fixed settings hot-reload not detecting edits to symlinked ~/.claude/settings.json
• Fixed plugin details failing to load when the marketplace key differs from the manifest name
• Fixed /model picker "Default" row not reflecting ANTHROPIC_DEFAULT_OPUS_MODEL/ANTHROPIC_DEFAULT_SONNET_MODEL overrides
• Fixed spurious "stream idle timeout" 5 minutes after a response completed, caused by the watchdog timer not being cleared on stream cancellation
• Fixed silent exit 1 when 10+ MCP servers are configured and the cache directory is unwritable — the error message now includes the underlying cause
• Fixed a typing cursor blinking on tab names, list pointers, and select rows in dialogs
• Fixed transcript view letter shortcuts not working after mouse click
• Fixed Bash-mode up-arrow history repeating the first entry and clobbering the in-progress draft
• Fixed pasting or dropping multiple images only inserting the last one
• Fixed hyperlinks using unreadable dark navy on dark themes — they now adapt to the active theme
• Fixed model picker showing a redundant "Current model" row for third-party users whose model is set to the opus alias
• Fixed legacy Opus picker entry on PAYG 3P providers resolving to the same model as the default entry
• Fixed mouse wheel scrolling speed in Cursor and VS Code 1.92–1.104; the trackpad now scrolls at a steady rate and the mouse wheel keeps ~3 lines per notch
• Fixed scroll behavior in Windows Terminal and VS Code when attached to background sessions
• Fixed MCP resources from disconnected servers lingering in @server: autocomplete
• Fixed two-file diff snippets over-reporting the number of truncated lines by one
• Fixed Grep results not relativizing Windows drive-letter paths and count mode reporting wrong totals for single-file paths
• Fixed border-embedded text overflowing on CJK/emoji due to visual cell width miscalculation
• Fixed fuzzy-match highlighting splitting emoji and astral-plane characters mid-pair
• Fixed skill argument names containing regex metacharacters breaking argument substitution
• Fixed ProgressBar rendering a full block for an almost-full fractional cell
• Fixed task polling and fs.watch being resurrected when the last subscriber leaves while a fetch is in flight
• Fixed plugin dependency resolution leaving a stale count when the manifest name differs from the source identifier
• Fixed Insights Time-of-Day chart skewing when a session has an unparseable timestamp
• Fixed keybindings using only the cmd/super/win modifier being flagged as unparseable
• Fixed claude_code.active_time.total OpenTelemetry metric not being emitted in --print mode
• Fixed claude plugin update not preserving cross-plugin symlinks inside a marketplace
• [VSCode] Press Cmd/Ctrl+Shift+T to reopen the most recently closed session tab, configurable via claudeCode.enableReopenClosedSessionShortcut

Original source

How it works

Today we're introducing agent view in Claude Code: one place to manage all your Claude Code sessions.

When running agents in parallel before, you've probably had to manage multiple terminal tabs, a tmux grid, and an overloaded mental ledger of what you need to tackle next.

With agent view in Claude Code, you can kick off new agents, send them to the background, and jump in only when Claude needs you. See at a glance which agents are waiting on you, which are still working, and which are done, so you can easily steer many all at once.

Agent view improves visualizing and interacting with your Claude Code sessions in the CLI.

See everything at once

Press the left arrow from any session or run claude agents from the terminal to open agent view. Each row shows the session, whether it needs your input, the contents of its last response, and when you last interacted with it.

Peek and reply without leaving

Select a session to peek at the last turn. If a session is waiting on a decision, answer inline and the session picks back up. Press enter to attach directly to sessions where you want to explore the full transcript.

Background anything

Lastly, users can take any existing session and add it to agent view using /bg or skip the foreground entirely using claude --bg [task] to launch a fresh session.

How developers are using agent view

A few patterns we have seen from early users:

• Scaling the number of concurrent sessions: Dispatch several ideas at once, each optionally paired with a skill, and return to a list of pull requests ready for review.
• Manage long running agents: PR babysitters, dashboard updaters, and other looping jobs show their next run time right in the list.
• Navigate between separate sessions: When you’re in the middle of a session, press the left arrow, start a related task or quick codebase question, then arrow right back into what you were doing. Peek shows the answer when it lands.
• See what shipped: Status indicators on each row plus the title in peek make it easy to scan which sessions produced a PR.

Getting started

Agent view is available today as a Research Preview on Pro, Max, Team, Enterprise, and Claude API plans. Opt-in by running claude agents. Usual rate limits apply. See the docs for more information.

Original source

The Claude Platform on AWS is now generally available, offering a new way for AWS customers to access the full set of Claude Platform features with AWS authentication, billing, and commitment retirement. Claude also remains available on Amazon Bedrock, where AWS is the data processor.

Starting today, Claude Platform on AWS customers can deploy agents at scale with Claude Managed Agents and build with tools like code execution, skills, the advisor strategy, and more.

Access the complete Claude Platform via AWS

The Claude Platform on AWS brings the full set of Claude API features to AWS customers for the first time, with all new features and betas shipping the same day they go live on the native Claude API.

Authentication runs through AWS IAM, audit logging through CloudTrail, and billing through a single AWS invoice that fully retires against existing commitments. Customers use their existing AWS credentials and IAM policies, so teams stay within the tools and permissions they already manage.

Claude Platform on AWS will be available in most AWS commercial regions and support global and U.S. inference geographies.

What's included

The Claude Platform on AWS includes native platform features, like:

• Claude Managed Agents (beta) to build and deploy agents at scale
• Advisor strategy (beta) to give agents an intelligence boost by consulting an advisor model
• Web search and web fetch to augment Claude’s knowledge with current, real-world data from across the web
• Code execution to run Python code, create visualizations, and analyze data directly within API calls
• Files API (beta) for uploading and referencing documents across conversations
• Skills (beta) to teach Claude best practices so it delivers consistent results
• MCP connector (beta) to connect Claude to any remote MCP server without writing client code
• Prompt caching for reducing costs and latency on repeated context
• Citations for grounding responses in source documents
• Batch processing for high-volume, asynchronous workloads

Claude Platform on AWS customers also get access to the Claude Console, Anthropic's development environment for building and testing with Claude. The Console includes a prompt improver, prompt generator, and evaluation tools.

Claude Opus 4.7, Sonnet 4.6, and Haiku 4.5 are available, with new models shipping on the Claude Platform on AWS as they launch.

Choosing the right path for developers

Both the Claude Platform on AWS and Claude on Amazon Bedrock enable AWS customers to build on Claude models. The difference is in who operates the service and which features are available.

The Claude Platform on AWS is a first of its kind offering for Anthropic, giving you all native Claude API features from day one. Anthropic operates the service and data is processed outside the AWS boundary. This is a good option for companies that want the full Claude Platform experience.

Claude on Amazon Bedrock keeps AWS as the data processor and operates within the AWS boundary. This is a good fit for companies that have strict regional data residency requirements or need their data processed exclusively within AWS's infrastructure.

Getting started

The Claude Platform on AWS is available today. To get started, visit the Claude Platform on AWS or explore the documentation.

If you have an existing Bedrock private offer, please contact your Anthropic or AWS account executive before getting started with Claude Platform on AWS to ensure your discounts are applied correctly. Discounts cannot be applied retroactively to usage incurred before a Claude Platform private offer is accepted.

Original source

Changes

• Added CLAUDE_CODE_ENABLE_FEEDBACK_SURVEY_FOR_OTEL to re-enable the session quality survey for enterprises capturing responses through OpenTelemetry
• Added settings.autoMode.hard_deny for auto mode classifier rules that block unconditionally regardless of user intent or allow exceptions
• Fixed MCP servers configured in .mcp.json, plugins, and claude.ai connectors silently disappearing after /clear in the VS Code extension, JetBrains plugin, and Agent SDK
• Fixed a rare login loop where a concurrent credential write could overwrite a freshly-rotated OAuth token and force re-login
• Fixed MCP OAuth refresh tokens being lost when multiple servers refresh concurrently — users with several remote MCP servers should no longer need daily re-authentication
• Fixed an API error (400) when extended thinking emitted a redacted thinking block after a tool call
• Fixed --resume / --continue not finding sessions when the project path contains underscores
• Fixed plan mode not blocking file writes when a matching Edit(...) allow rule exists
• WSL2: image paste from Windows clipboard now works via a PowerShell fallback when xclip/wl-paste cannot read image data
• Fixed plugin Stop/UserPromptSubmit hooks failing when cache cleanup deletes a version still in use by a running session
• Improved visual consistency across slash command dialogs: standardized footer hints, dialog spacing, and arrow-key styling, and the dialog frame now appears immediately during loading instead of popping in after
• Fixed colors appearing at wrong positions in bash command output and markdown code blocks
• Fixed ReasonML diffs rendering corrupted "undefined" text artifacts at word-diff boundaries
• Fixed worktree exit dialog warning about uncommitted files in the wrong directory after worktree removal
• Fixed @ file picker not matching files created mid-session in small non-git directories
• Fixed @-mention file picker not finding files in directories with more than 100 entries
• Fixed failed tool calls not being click-to-expand in fullscreen mode when their output was truncated
• Fixed Backspace and Ctrl+Backspace getting swapped after using Ctrl+G to open an external editor on terminals with persistent extended-key modes
• Fixed /usage weekly reset showing time of day instead of the calendar date
• Fixed welcome banner ellipsis causing column overflow on CJK terminals
• Fixed /insights crash when session history contains tool calls with malformed input fields
• Fixed a renderer crash when a tool's collapsibility classification changes mid-session
• Fixed a skills entry in plugin.json hiding the plugin's default skills/ directory, and listing a file path now shows an error instead of failing silently
• Fixed IDE shell-integration lock files not respecting CLAUDE_CONFIG_DIR
• Fixed trailing whitespace in copied terminal output during streaming
• Fixed plugin uninstall and enable/disable not matching slugs case-insensitively
• Fixed tool error truncation marker showing a negative count for surrogate-pair strings
• Fixed env vars from CLAUDE_ENV_FILE SessionStart hooks going stale after /resume or /clear
• Fixed /branch saving a multi-line session title when given a pasted multi-line name
• Fixed a stray leading space on the second line of wrapped text at the column boundary
• Fixed Esc not dismissing dialogs in /install-github-app, /desktop, /resume, and /web-setup
• Fixed /doctor MCP schema errors not naming the missing field or showing the source file path
• Fixed Bash permission prompts showing an internal parser diagnostic instead of a user-readable explanation
• Fixed plugin slash commands with spaces (e.g. /myplugin review) not resolving to their namespaced form
• Fixed AskUserQuestion discarding multi-select answers when supplied as an array
• Fixed /clear <name> not labeling the cleared session for /resume
• Fixed CronList output missing qualifiers and the scheduled prompt
• Fixed "Jump to bottom" overlay leaving color artifacts on CJK characters in fullscreen mode
• Fixed wide markdown tables leaving a stale bordered render in terminal scrollback while streaming
• Fixed pasted text being silently dropped when a long prompt with a pasted-text placeholder was auto-truncated
• Fixed /release-notes getting stuck on an old version after a failed changelog refresh
• Fixed /mcp server list not scrolling when there are more servers than fit in the terminal
• Fixed mid-input slash command autocomplete not working after an initial slash command
• Fixed scrolling to bottom re-engaging auto-follow with autoScrollEnabled: false
• Fixed prompt suggestions being auto-submitted by Enter on an empty input instead of requiring Tab or arrow to accept
• Fixed keyboard shortcut hints not reflecting rebound keys from keybindings.json
• Fixed /settings language change being reverted on Escape after confirming
• Fixed /terminal-setup only appearing in autocomplete on exact name match instead of partial prefixes
• Fixed "Chat about this" on an AskUserQuestion dialog erasing the question text
• Fixed MCP tool results being invisible when the server returns content blocks
• Improved error message when --worktree collides with an existing or stale worktree
• Changed plugin marketplace removal key to d (matching delete elsewhere) instead of r which collided with retry

Original source

• Added worktree.baseRef setting (fresh | head) to choose whether --worktree, EnterWorktree, and agent-isolation worktrees branch from origin/<default> or local HEAD. Note: the default fresh changes EnterWorktree's base back to origin/<default> (it has been local HEAD since 2.1.128) — set worktree.baseRef: "head" to keep unpushed commits in new worktrees
• Added sandbox.bwrapPath and sandbox.socatPath managed settings (Linux/WSL) to specify custom bubblewrap and socat binary locations
• Added parentSettingsBehavior admin-tier key ('first-wins' | 'merge') to let admins opt SDK managedSettings (parent tier) into the policy merge
• Hooks now receive the active effort level via the effort.level JSON input field and the $CLAUDE_EFFORT environment variable, and Bash tool commands can read $CLAUDE_EFFORT
• Improved focus mode behavior
• Improved memory usage by releasing warm-spare background workers under memory pressure
• Fixed parallel sessions all dead-ending at 401 after a refresh-token race wiped shared credentials
• Fixed Edit/Write allow rules scoped to a drive root (C:\) or POSIX / matching incorrectly and always prompting
• Fixed an unhandled rejection (ECOMPROMISED) when a history or session-log file lock is compromised by clock skew or slow disk
• Fixed pressing Esc during conversation compaction showing a spurious "Error compacting conversation" notification
• Fixed HTTP(S)_PROXY / NO_PROXY / mTLS not being respected for the full MCP OAuth flow including discovery, dynamic client registration, token exchange, and token refresh
• Fixed Read/Write/Edit being denied on mapped network drives passed via --add-dir / SDK additionalDirectories
• Fixed Remote Control stop/interrupt from claude.ai not fully canceling the CLI session the same way local Esc does, causing queued messages to never advance after interrupting a stuck tool or prompt
• Fixed /effort in one session unexpectedly changing the effort level of other concurrent sessions, and a related issue where an IDE effort change could be silently dropped
• Fixed subagents not discovering project, user, or plugin skills via the Skill tool
• claude --help now lists --remote-control alongside --remote-control-session-name-prefix
• [VSCode] Fixed claudeCode.claudeProcessWrapper failing with "Unsupported platform" when the extension build doesn't bundle a Claude binary

Original source

• Added CLAUDE_CODE_SESSION_ID environment variable to the Bash tool subprocess environment, matching the session_id passed to hooks
• Added CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1 env var to opt out of the fullscreen alternate-screen renderer and keep the conversation in the terminal's native scrollback
• Added a "Pasting…" footer hint while a Ctrl+V image paste is being read from the clipboard
• Fixed external SIGINT (e.g. IDE stop button, kill -INT) not running graceful shutdown — terminal modes are now restored and the --resume hint is printed instead of an abrupt exit
• Fixed an uncaught exception when the terminal is closed or SSH disconnects mid-session under the native build
• Fixed --resume failing with no low surrogate in string when a tool error truncation split an emoji; pre-corrupted sessions are sanitized on load
• Fixed --permission-mode flag being ignored when resuming a plan-mode session with -p --continue/--resume, and plan mode not being re-applied after ExitPlanMode within the same session
• Fixed fullscreen mode showing a blank screen after laptop sleep/wake or Ctrl+Z/fg until the next keystroke or stream output
• Fixed cursor landing mid-grapheme on Ctrl+E/A/K/U/arrow keys when an Indic conjunct or ZWJ emoji wraps across lines
• Fixed vim operators corrupting text containing decomposed (NFD) accented characters
• Fixed pasting text starting with / silently swallowing the input or triggering an unknown-command reply
• Fixed pasting dumping stray escape sequences into the prompt when focus events or mouse-tracking reports interleave with the bracketed paste
• Fixed mouse wheel scrolling being too fast in Cursor and VS Code 1.92–1.104 due to an upstream xterm.js bug
• Fixed scroll-wheel handling in JetBrains IDE 2025.2 terminals (spurious arrow keys, wrong-direction events, runaway acceleration)
• Fixed /usage Ctrl+S hanging when copying the stats screenshot to the clipboard on Linux/X11
• Fixed /terminal-setup showing a contradictory error in Windows Terminal — Shift+Enter is natively supported there
• Fixed /effort picker not reflecting the CLAUDE_CODE_EFFORT_LEVEL env var override
• Fixed /status showing the wrong default model for some users
• Fixed slash command autocomplete popup being capped at ~3–5 visible commands instead of scaling with terminal height
• Fixed statusline context_window token counts reflecting cumulative session totals instead of current context usage
• Fixed Alt+T (thinking toggle) not working on macOS terminals without "Option as Meta" enabled (iTerm2, Terminal.app defaults)
• Fixed dead keyboard input on Windows after re-opening a background session from claude agents
• Fixed unbounded memory growth (10GB+ RSS) when a stdio MCP server writes non-protocol data to stdout
• Fixed MCP servers that connect but fail tools/list silently showing 0 tools — they now retry once and show "connected · tools fetch failed" in /mcp
• Fixed unauthorized claude.ai MCP connectors showing as "failed" instead of "needs auth", and headless -p mode retrying non-transient 4xx connection failures
• Improved visual consistency in slash command dialogs and /login, /upgrade, /extra-usage dialog spacing
• Updated the /tui fullscreen startup banner to describe additional renderer benefits (lower memory usage, mouse support, auto-copy on select)
• Fixed Bedrock and Vertex 400 errors when ENABLE_PROMPT_CACHING_1H is set

Original source

Starting today, Claude for Excel, PowerPoint, and Word are generally available, and Claude for Outlook is now in public beta for all paid plans. As Claude moves between tasks in your Microsoft apps, it keeps the full context of your conversation.

One conversation across four apps

Most work doesn't live in one application, so Claude moves between them as you do. Triage an email in Outlook, open the attachment in Word to draft a memo in your team's template, build the supporting analysis in Excel, and turn it into a deck in PowerPoint — all without re-explaining what you're working on. Adjust an assumption in Excel and the chart in PowerPoint and the number in your Word memo automatically update, too.

Claude works across open files, so keep the spreadsheet, deck, and memo open side by side and changes will flow between them.

Conversations persist with each file, so you can close the sidebar, reopen it the next day, and pick up where you left off using your keyboard or your voice.

Claude for Outlook

Claude for Outlook brings Claude into your inbox. Ask Claude to triage your inbox and it sorts messages by what needs your response, what it can draft for you, and what's noise. Replies land as drafts in Outlook's compose pane with recipients, subject, and body filled in. Calendar invites check attendee availability and open in Outlook's native event form.

Open an attachment in Word or Excel and Claude already knows what the sender asked for. You review every reply and calendar invite before it goes out, and nothing goes out until you click send.

Deploying Claude for Microsoft 365 across your organization

Claude for Excel, PowerPoint, and Word are now generally available, with the controls IT admins and organizations need. One AppSource listing covers Excel, PowerPoint, and Word, and a separate listing adds Outlook in beta. Admins can deploy both from the Microsoft admin center.

Enterprise admins can configure OpenTelemetry to stream prompts, tool calls, and document references to their own collector, so security teams see exactly what Claude does across every app. The Analytics API breaks out activity per user, per app, per day.

Organizations can access all four add-ins with a Claude account, or route traffic through an existing LLM gateway to Claude models running on Amazon Bedrock, Google Cloud’s Vertex AI, or Microsoft Foundry.

Microsoft 365 Copilot customers can also work with Claude AI models directly within Excel and PowerPoint.

How organizations use Claude for Microsoft 365

“We can instruct Claude to build a style guide from an executive's prior written communications so our EAs can draft their emails in their voice. That's high-leverage work the team would never have time to set up by hand.”
Ben Letalik, Sr. Director, Digital Transformation & Innovation

“We can instruct Claude to build a style guide from an executive's prior written communications so our EAs can draft their emails in their voice. That's high-leverage work the team would never have time to set up by hand.”
Rajeev Sethi, GVP Enterprise Technologies

“Our investment professionals live in data and analytical models, and Claude for Excel meets them there. Analysts are using it to build and update coverage models, separate signal from noise, and pressure-test their work — all with a step-change in efficiency.”
Atte Lahtiranta, Head of Core Engineering

“Claude in Excel allows my teams to build an initial version of complex models faster, enabling them to focus on refining the model, pressure testing inputs and assumption, and exploring more scenarios and trade-offs. This helps us have richer and deeper discussions with our clients earlier.”
Gene Rapoport, Head of Private Equity AI Practice

“Claude enables a seamless transition from rough ideas to polished, branded deliverables across presentation, document and spreadsheet applications without disrupting the workflow. That end-to-end consistency has been a significant time-saver, especially when quality, formatting, and speed all matter.”
Vivek Kulkarni, US AI Transformation Leader

Getting started

All Mac and Windows users on paid plans can access Claude for Microsoft 365. Claude for Outlook is available in beta on all paid plans. Admins can deploy these add-ins from Microsoft AppSource through the Microsoft admin center.

Original source

• Added --plugin-url <url> flag to fetch a plugin .zip archive from a URL for the current session
• Added CLAUDE_CODE_FORCE_SYNC_OUTPUT=1 env var to force-enable synchronized output on terminals that auto-detection misses (e.g. Emacs eat)
• Added CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE: when set on Homebrew or WinGet installations, Claude Code runs the upgrade command in the background and prompts to restart
• Plugin manifests: themes and monitors should now be declared under "experimental": { ... }. Top-level declarations still work but claude plugin validate will warn
• Gateway /v1/models discovery for the /model picker is now opt-in via CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY=1 (was automatic in 2.1.126–2.1.128)
• Ctrl+R history picker now defaults to searching all prompts across all projects, matching pre-2.1.124 behavior. Press Ctrl+S to narrow to the current project or session
• Third-party deployments (Bedrock, Vertex, Foundry, or ANTHROPIC_BASE_URL gateway) no longer see spinner tips pointing at first-party Anthropic surfaces
• skillOverrides setting now works: off hides from model and /, user-invocable-only hides from model only, name-only collapses description
• The claude_code.pull_request.count OTel metric now counts PRs/MRs created via MCP tools, not just shell commands
• Policy refusal error messages now include the API Request ID for easier support debugging
• Fixed API errors with unrecognized 400 status codes showing raw JSON instead of the underlying error message
• Fixed /clear not resetting the terminal tab title after a conversation
• Fixed session title chip from /rename disappearing while a permission or other dialog is active
• Fixed agent panel below the prompt being hidden when subagents are running (regression in 2.1.122)
• Fixed external-editor handoff (Ctrl+G) blanking the conversation history above the prompt
• Fixed /context dumping its rendered ASCII visualization grid into the conversation, wasting ~1.6k tokens per call
• Fixed /agents Library list arrow-key navigation: the highlighted agent now stays visible when the list exceeds the viewport
• Fixed /branch success message not including the new branch's session id for /resume
• Fixed bold headers with keycap/ZWJ/skin-tone emoji losing trailing characters in fullscreen mode
• Fixed server-managed settings policy not applying for enterprise/team users whose stored OAuth credentials lacked the user:inference scope
• Fixed OAuth refresh race after wake-from-sleep that could log out all running sessions
• Fixed 1-hour prompt cache TTL being silently downgraded to 5 minutes
• Fixed cache-miss warning appearing spuriously after /clear or compaction when changing /effort or /model
• Fixed Bash(mkdir *), Bash(touch *) and similar allow rules not being honored for in-project paths
• Fixed deniedMcpServers patterns with a *:// scheme wildcard not matching mixed-case hostnames
• Fixed harmless WebSocket warning being logged as an error in --debug during voice mode
• [VSCode] Fixed /clear not clearing the conversation context and displayed transcript

Original source

We’ve agreed to a partnership with SpaceX that will substantially increase our compute capacity. This, along with our other recent compute deals, means that we’ve been able to increase our usage limits for Claude Code and the Claude API.

Below, we describe these changes and the progress we’re making on compute.

Higher usage limits

The following three changes—all effective today—are aimed at improving the experience of using Claude for our most dedicated customers.

First, we’re
doubling Claude Code’s five-hour rate limits
for Pro, Max, Team, and seat-based Enterprise plans.

Second, we’re
removing the peak hours limit reduction on Claude Code
for Pro and Max accounts.

Third, we’re
raising our
API rate limits
considerably for Claude Opus models
, as shown in the table below:

Our updated API rate limits for Claude Opus models.

New compute partnership with SpaceX

We’ve signed an agreement with SpaceX to use all of the compute capacity at their Colossus 1 data center. This gives us access to more than 300 megawatts of new capacity (over 220,000 NVIDIA GPUs) within the month. This additional capacity will directly improve capacity for Claude Pro and Claude Max subscribers.

This joins our other significant compute announcements:

• An up to 5 gigawatt (GW) agreement with Amazon
  , which includes nearly 1 GW of new capacity by the end of 2026;
• A 5 GW agreement with Google
  and Broadcom, which will begin coming online in 2027;
• A
  strategic partnership
  with Microsoft and NVIDIA that includes $30 billion of Azure capacity;
• Our
  $50 billion investment
  in American AI infrastructure with Fluidstack.

We train and run Claude on a range of AI hardware—AWS Trainium, Google TPUs, and NVIDIA GPUs—and continue to explore opportunities to bring additional capacity online.

As part of this agreement, we have also expressed interest in partnering with SpaceX to develop multiple gigawatts of orbital AI compute capacity.

Expanding internationally

Our enterprise customers—particularly those in regulated industries like financial services, healthcare, and government—increasingly need in-region infrastructure to meet compliance and data residency requirements. Accordingly, some of our capacity expansion will be international: our recently announced
collaboration with Amazon
includes additional inference in Asia and Europe.

We’re very intentional about where we’ll add capacity—partnering with democratic countries whose legal and regulatory frameworks support investments of this scale, and where the supply chain on which our compute depends—hardware, networking, and facilities—will be secure.

Finally, we recently made a
commitment
to cover any consumer electricity price increases caused by our data centers in the US. As part of our international expansion, we’re exploring ways to extend that commitment to new jurisdictions, as well as partnering with local leaders to invest back into the communities that host our facilities.

Original source