Auto mode classifier supports custom models, extra-long conversations no longer rejected outright
When you enable auto mode (a mode that lets Claude execute tools autonomously without asking each time) to handle heavy and complex tasks, you can now customize the model used by the local safety classifier. Through the environment variable CLAUDE_CODE_AUTO_MODE_MODEL, you can specify the model for the client-side classifier while the server-side model remains unchanged. When a conversation is too long and exceeds the scope of server-side safety checks, it is now compacted first instead of rejecting tool calls outright.
An issue where most auto mode classifier block events failed to record classifier_category has been fixed. Another issue where newly added attributes crowded out tool_use_id, tool_source, and tool_parameters when OTEL_LOGRECORD_ATTRIBUTE_COUNT_LIMIT was set low has also been resolved.
When you leave a conversation window idle for too long, you might notice that Claude automatically reorganizes earlier message history. The /config settings menu now includes an "Idle compaction" option so you can freely enable or disable automatic idle compaction, and the notice displayed after reorganization finishes now explains how to turn it off. Previously, if you stopped generation midway while a conversation was being compacted, the screen would throw a "Prompt is too long" error; this issue has now been resolved.
If your gateway uses prefixed Opus 4 or 4.1 names (such as anthropic/claude-opus-4-1), running /autocompact and /effort has also been corrected to save to the proper model.
When you start a new conversation, operating instructions for Claude in Chrome can now be read from a shared prompt cache. Claude adjusted the placement of these instructions within the system prompt so that new conversations can share the existing cache.
Tools added dynamically midway through a session will no longer suffer cache misses, even after being reloaded via ToolSearch or undergoing conversation compaction.
FEATURE
Claude Design shows sunset date notices, cloud failures route to dedicated settings
If you regularly use UI design commands in your terminal, you will now see more accurate timelines and guidance notices during related operations. When you enter /design-sync or /design-login, the screen adds a notice explaining that the standalone web version of Claude Design is scheduled to shut down on December 14, 2026.
When executing /design consent and /design revoke fails in a cloud session, the error message now points you to claude.ai/design/settings instead of recommending unusable login commands.
When you have many plugins installed for a project, launching Claude Code now comes with noticeably shorter wait times. The system has reduced filesystem calls when reading plugin commands and agent files, an improvement that is especially noticeable on Windows. Previously, when executing subcommands like claude plugin, the process would occasionally exit before configuration file writes finished, causing lost changes or leaving behind .tmp temporary files; it now ensures writes complete before exiting. When Git defaults to the reftable reference format, the marketplace no longer repeatedly re-downloads entire repositories on every refresh, nor do newly installed plugins display an unknown version. PowerShell tools can now smoothly invoke commands under a plugin's bin/ directory, piping into formatting commands when search results are empty no longer throws errors, and failures when querying builtin plugins correctly point to /plugin.
BUGFIX
MCP protocol compatibility upgraded, desktop re-authentication guidance made more accurate
When using external tools in the desktop app, you will now receive guidance that perfectly matches your current interface if re-authentication or reconnection is required. Previously, when desktop Claude needed to reconnect to an MCP (Model Context Protocol, a protocol that connects AI to external tools) server, it misdirected you to check web settings or run the /mcp command, even though neither option existed in that environment; this guidance has now been corrected.
Meanwhile, when an external server negotiates protocol version 2026-07-28 without providing optional fields such as resultType, ttlMs, or cacheScope, the tool list no longer goes blank, and tool calls no longer fail completely.
FEATURE
Forked subagents enabled by default, background execution rules aligned across interfaces
When using Claude in the desktop app, VS Code, or programmatically, rules for handling multiple tasks in parallel are now unified with the terminal. Forked subagents (subagent_type: "fork") are now enabled by default in claude -p, the Agent SDK, desktop, and VS Code; to disable them, set CLAUDE_CODE_FORK_SUBAGENT=0, while claude mcp serve does not offer them. Subagents in main conversations on desktop and VS Code now always run in the background rather than being decided by the model, whereas agent calls initiated by subagents run in the foreground by default. An issue in the viewer where scrolling long lists or collapsing groups resulted in highlighted blank lines has been fixed, and the bottom ← for agents hint text now automatically hides 10 seconds after a session opens, leaving only a count of pending agents.
FEATURE
Third-party cloud headless mode permissions default to default, switching providers no longer errors
When calling Claude on enterprise cloud platforms via the CLI or SDKs, switching provider channels midway through a session will no longer stall. Previously, switching to Vertex AI or Bedrock in the middle of a session frequently failed due to mismatched input parameters (diagnostics: Extra inputs are not permitted); this compatibility issue is now resolved. On third-party providers, if no permission mode is specified and telemetry is disabled or the setup is a fresh install, claude -p and Agent SDK sessions will start with default, requiring an explicit --permission-mode auto to maintain automatic approvals. When reopening background sessions from other folders that lack a model gateway, the system now specifically explains why the connection failed instead of vaguely reporting that you are not logged in.
FEATURE
Concurrency limits added for prompt and agent hooks, executing at most 12 per event
When your automation workflow sets up many custom interception commands for the same event, you can keep track of which are currently executing and which are still waiting. Prompt and agent hooks (small programs triggered by specific events) now have a concurrency limit: at most 12 can run concurrently for the same event, with remaining hooks waiting their turn. This limit is calculated on a per-event basis.
BUGFIX
Windows external drive writes no longer rejected, Git orphaned files and fetch fixed
When working on projects across different operating systems or specialized disk formats, file modifications and version control will now run much more smoothly. On Windows, if a project is located on an exFAT or FAT32 partition—including sessions started with the --plugin-dir flag—file writes that were previously rejected by the system or triggered frequent confirmation prompts have had their permission misjudgments fixed. In Git 2.56 or newer, if a directory retains an orphaned .git file pointing to a nonexistent path, the worktree (a Git feature for maintaining multiple copies of the same project in parallel) isolation mechanism no longer refuses to create or restore worktrees. For self-hosted runners that reuse checkout directories formatted with reftable, running git fetch to retrieve data will no longer fail due to object errors.
BUGFIX
Wrapped terminal hyperlinks are fully clickable, and emojis no longer break table layouts
When you browse long URLs or text containing icons output by Claude in the terminal, visual presentation and click experiences are now much cleaner. Previously, when an extra-long URL wrapped in backticks wrapped across lines, only the first line was clickable in terminals that support hyperlinks. Now, the entire URL is consolidated into a single clickable link. When a link started inside an emoji, the wrap width counted an extra character cell, causing that emoji to be hidden in question previews and turning tables into lists. These issues are now fixed.
BUGFIX
Cloud session costs no longer reset during accumulation, and credit plans skip extra suggestions
When you monitor account quota consumption or continue projects in the cloud, usage and cost tracking are now more precise. If your subscription plan charges for specific models solely via extra credits, Claude automatically skips follow-up prompt suggestions after answering the query and deducting credits, preventing silent credit consumption in the background. Meanwhile, when a cloud session resumes in a new process, previously accumulated costs and usage no longer reset to zero.
When you ask Claude to read local images, the source size determines whether it loads. Previously, the Read tool (a utility for inspecting file contents) loaded image files of any size, or pipes and devices named like images, entirely into memory. Now, image sources exceeding 128 MB are rejected from loading.
BUGFIX
Artifact publishing supports empty modifications, and version conflict retry logic is fixed
When you have Claude dynamically generate or modify display artifacts in conversation, the publishing flow is no longer interrupted by minor glitches. When publishing an artifact (a standalone display panel or code file), the system no longer fails if Claude transmits an empty list of modifications. Meanwhile, if a newer version of an artifact was already created elsewhere while an update was being submitted, Claude no longer blindly retries in an erroneous manner upon rejection, but follows the proper retry mechanism to update content.
FEATURE
Prompt message redirects to GitHub when organizations disable the feedback command
When using the terminal in a corporate or enterprise-managed team environment and looking to share suggestions about tool features, notice the prompt shown by the feedback command. When your organization's administrative policy disables the /feedback command, the on-screen message now directs you to GitHub issues (a page used to submit bug reports), instead of asking you to contact an internal organization admin.
BUGFIX
Remote Control clearly marks offline status, and help remains accessible while logged out
When managing sessions across devices through Remote Control, connection status is now clear at a glance. If your computer goes offline during a remote connection, the subagent panel in the interface no longer spins indefinitely, but clearly shows that the Remote Control connection has dropped.
Meanwhile, if you run claude remote-control --help without being logged in to an account, the system now prints complete command usage and exits cleanly, instead of hanging unresponsive.
BUGFIX
[VSCode] Browser connection status calibrated, and unclosed code block streaming fixed
When viewing Claude's responses while connecting peripheral tools inside the VS Code editor, visual display and connection status are now more accurate. Previously, even when unable to connect to any browser with the Claude extension installed, the @browser banner at the top mistakenly reported "Browser connected". Now, connection status is calibrated to reflect actual conditions. When an MCP server URL contains a query string, completing login authorization from the panel no longer opens a broken authentication webpage. If a list item contained an unclosed code block, a rendering glitch where subsequent text briefly displayed as plain text before abruptly snapping into code during streamed generation has now been completely fixed.
BUGFIX
[Cloud sessions] Unstarted routine reasons now visible, with status determination and duplicate executions fixed
When configuring automated routines in the cloud to run reports or analyses, task execution histories are now more dependable. On the routine management page, if the previous run failed to start properly, a prominent banner at the top now details the specific reason, such as the organization reaching its concurrent cloud session limit. Previously, unexpected interruptions in a cloud session caused the task status to be misrecorded as completed. If a task was archived before starting, it was erroneously displayed as canceled. Now, these edge cases are properly marked as failed. Meanwhile, when a scheduled task fails midway, the system no longer takes it upon itself to restart from scratch an hour or more later, preventing duplicate reports or repeated billing charges.
BUGFIX
[Cloud sessions] History rewind and cross-device sync fixed, with precise launch failure messages
When collaborating with teams in cloud sessions through a browser, multiple operations and interface sync mechanisms are now smoother. When clicking "Rewind to here" inside a session, previously only the latest message worked while all others failed, but now every historical checkpoint rewinds smoothly. Self-hosted runners require Claude Code v2.1.246 or later. When a pull request encounters merge conflicts, the status line no longer briefly flashes back to a ready state during GitHub re-reviews. When a GitHub repository is renamed or moved, issues where the diff view missed modifications or failed to load have been resolved. Meanwhile, messages sent from another device now appear instantly on open pages without requiring a manual refresh. If a session fails to launch, error messages now explicitly indicate "Connection lost" or a server error instead of staying vague.
BUGFIX
[Claude Tag] Slack message formatting and image attachments fixed, preventing premature direct message drops
When tagging Claude for assistance in Slack channels or direct messages, conversation formatting and file-sharing experiences are now much more reliable. Images uploaded to Slack in formats such as HEIC, SVG, TIFF, and BMP now pass properly to Claude as working files instead of getting lost. When Claude answers a question by editing an earlier message, the "is thinking…" indicator below the tag clears properly rather than lingering permanently. URLs inside code blocks attached under list steps are no longer wrapped in superfluous angle brackets, allowing copied commands to be pasted directly. Hyperlinks in responses no longer absorb trailing bold markers, italics, or full-width punctuation into the URL and break formatting. When a direct message encounters a delay in a single Slack lookup, the system now proactively retries first, rather than immediately replying that direct messages are unavailable and discarding the request. In Slack Enterprise Grid, direct messages run in whichever connected workspace where you most recently opened Claude.
FEATURE
[Claude Tag] Admin Interface Reorganized into Four Tabs, Accelerating Repository and Channel Search
When administrators adjust Claude authorization scopes and connection channels in the admin console, permissions are now neatly organized. The Claude Tag admin interface has been reorganized into four tabs: Bundles, Connectors, Skills and plugins, and Channels, making permission categories clear at a glance. Repository search performance has noticeably improved, now covering up to 100 connected GitHub accounts and searching private repositories beyond the first 5,000 indexed by GitHub App installations. In the add location feature, manually entering or pasting a channel name immediately displays that channel without waiting for the organization's full channel list to load. The "Add > Domain" option on workspace or channel pages is ready as soon as the current page finishes loading, without waiting for all channels to load.
When enterprises strictly control Claude usage permissions across different team roles, configuration rules for administrator roles and external tools are now thoroughly clarified. In organizations with restricted role permissions, newly appointed channel managers previously could lose access to Claude in Slack. The manager role now automatically includes access authorization for Claude Tag. The roles page in organization settings has also been tidied up, consolidating roles created for channel managers into a collapsible section beneath existing organization roles for a much cleaner layout. If multiple MCP servers share the same host address, the admin console no longer mistakenly merges them into a single connector, displaying each server independently instead. When a channel reaches its monthly spend cap, the system notice no longer mistakenly claims that channel managers can increase quotas, instead clearly identifying organization owners with a link to the usage page.
FEATURE
[Code Review] Setup Automatically Restores After Connecting GitHub, Reopening Directly to Repository Selection
When configuring Code Review workflows in the admin console, redirecting mid-process for authorization no longer loses your initial progress. Previously, leaving the setup workflow to connect a GitHub account prevented the admin console from automatically restoring progress upon return, often requiring a fresh start. This redirection interruption is now resolved, reopening directly to the repository selection screen upon return so you can smoothly resume setup.
Original changelog
Original changelogAuto mode classifier supports custom models, extra-long conversations no longer rejected outright
Added `CLAUDE_CODE_AUTO_MODE_MODEL` to choose the model the client-side auto mode classifier uses; it does not change the model for server-side auto mode
Fixed `classifier_category` missing from OpenTelemetry `tool_decision` events for most auto mode classifier blocks, and new `tool_decision` attributes pushing out `tool_use_id`, `tool_source` and `tool_parameters` when `OTEL_LOGRECORD_ATTRIBUTE_COUNT_LIMIT` is low
Improved auto mode with the server-side classifier: a conversation too long for the safety check is now compacted, instead of every checked tool call being denied
Original changelog/config adds idle compaction toggle, stopping midway no longer reports length error
Added an `Idle compaction` row to `/config` for turning idle compaction off or back on; the notices shown after an idle compaction now say how to turn it off
Fixed a "Prompt is too long" error when stopping a turn while the conversation was being compacted
Fixed `/autocompact` and `/effort` saving to the wrong model when a gateway names Opus 4 or 4.1 with a prefix, such as `anthropic/claude-opus-4-1`
Original changelogChrome extension instructions share cache, dynamic tool loading no longer misses
Fixed a prompt cache miss when a tool added mid-session was loaded again through ToolSearch or after compaction
Changed where the Claude in Chrome instructions sit in the system prompt so that new conversations can read them from the shared prompt cache
Original changelogClaude Design shows sunset date notices, cloud failures route to dedicated settings
Added a notice to `/design-sync` and `/design-login` that standalone Claude Design (claude.ai/design) closes by December 14, 2026
Fixed `/design consent` and `/design revoke` suggesting `/design-login` when they fail in a cloud session, where it isn't available; the message now points to claude.ai/design/settings
Original changelogPlugin loading speed noticeably improved, config writing and command compatibility fixed
Fixed `claude plugin` and other subcommands sometimes exiting before a queued settings or config write finished, which could lose the change or leave a `.tmp` file behind
Fixed plugin marketplaces re-cloning on every refresh, and newly installed git plugins showing version "unknown", when git defaults to the reftable ref format
Fixed the PowerShell tool not finding commands in a plugin's `bin/` folder, and reporting an error when a search that finds nothing (rg, grep, findstr, git grep) is piped into `Select-Object` or another formatting cmdlet
Fixed `claude plugin details <name>@builtin` suggesting `claude plugin list`, which never shows built-in plugins, when the plugin isn't found; it now points to `/plugin`
Improved startup time with many plugins enabled: plugin command and agent files now take far fewer file system calls to load, most of all on Windows
Original changelogMCP protocol compatibility upgraded, desktop re-authentication guidance made more accurate
Fixed Claude in the desktop app pointing you to claude.ai settings or `/mcp` to authorize or reconnect an MCP server where that option isn't available
Fixed MCP servers showing no tools, or every tool call failing, when the server negotiates protocol version 2026-07-28 but omits `resultType`, `ttlMs` or `cacheScope`
Original changelogForked subagents enabled by default, background execution rules aligned across interfaces
Fixed rows in the agents view staying blank after moving down a long list or folding a section
Changed fork subagents (`subagent_type: "fork"`) to be on by default in `claude -p`, the Agent SDK, the desktop app and VS Code, as they already are in the terminal; `CLAUDE_CODE_FORK_SUBAGENT=0` turns them off, and `claude mcp serve` never offers them
Changed the desktop app and VS Code to always run the main conversation's subagents in the background, as the terminal does, rather than let Claude choose; a subagent's own Agent calls in `claude -p`, the Agent SDK, the desktop app and VS Code now run in the foreground by default
Changed the `← for agents` footer hint to hide 10 seconds after a session opens; the count of agents waiting on you still shows
Original changelogThird-party cloud headless mode permissions default to default, switching providers no longer errors
Fixed requests failing with "diagnostics: Extra inputs are not permitted" after switching to Vertex or Bedrock mid-session
Improved the message when a background session reopened from another folder has no LLM gateway: it now says why, instead of "Not logged in"
Changed `claude -p` and Agent SDK sessions with no permission mode to start in `default` mode on third-party providers, with telemetry off or on a fresh install; `--permission-mode auto` keeps auto
Original changelogConcurrency limits added for prompt and agent hooks, executing at most 12 per event
Changed prompt and agent hooks so that at most 12 of one event run at a time; the rest wait their turn
Original changelogWindows external drive writes no longer rejected, Git orphaned files and fetch fixed
Fixed worktree isolation refusing to create or resume worktrees under git 2.56 or later when a stray `.git` file points at a directory that doesn't exist
Self-hosted runner: Fixed git fetches failing with "bad object refs/heads" in sessions that reuse a checkout stored in git's reftable format
Windows: Fixed every file write being refused or asked about for projects on exFAT or FAT32 drives, including in sessions started with `--plugin-dir`
Original changelogWrapped terminal hyperlinks are fully clickable, and emojis no longer break table layouts
Fixed URLs written in backticks being clickable only on their first row when they wrap; the whole URL is now one link in terminals that support hyperlinks
Fixed an emoji that a link starts inside wrapping one column too wide, which hid it in question previews and turned tables into lists
Original changelogCloud session costs no longer reset during accumulation, and credit plans skip extra suggestions
Fixed prompt suggestions spending usage credits on models your plan pays for only with credits: they are now skipped after a reply billed to credits
Fixed a cloud session's cost and usage restarting from zero after the session resumed in a new process
Original changelogRead tool sets image size limit, directly rejecting sources over 128 MB
Fixed the Read tool loading an image file of any size, or a pipe or device named like an image, entirely into memory; image sources over 128 MB are now refused
Original changelogArtifact publishing supports empty modifications, and version conflict retry logic is fixed
Fixed artifact publishes sometimes failing when Claude sent an empty list of edits, and Claude retrying an artifact update the wrong way after a newer version of the artifact turned it away
Original changelogPrompt message redirects to GitHub when organizations disable the feedback command
Changed the message shown when your organization's policy turns off `/feedback`: it now points to GitHub issues instead of an organization admin
Original changelogRemote Control clearly marks offline status, and help remains accessible while logged out
Fixed `claude remote-control --help` not printing its usage and exiting when not signed in
[Remote Control] Fixed a subagent's pane spinning forever in a Remote Control session after your computer goes offline; it now says Remote Control is disconnected
Original changelog[VSCode] Browser connection status calibrated, and unclosed code block streaming fixed
[VSCode] Fixed text after an unclosed code block in a list showing as plain text while a reply streams, then turning into code
[VSCode] Fixed MCP server sign-in from the panel opening a broken authorization page when the server URL contains a query string
[VSCode] Fixed the `@browser` banner saying "Browser connected" when no browser with the Claude extension can be reached
Original changelog[Cloud sessions] Unstarted routine reasons now visible, with status determination and duplicate executions fixed
[Cloud sessions] Added a banner on a routine's page that says why its last run didn't start, such as your organization reaching its limit on concurrent cloud sessions
[Cloud sessions] Fixed routine runs showing as Completed after their cloud session stopped unexpectedly, and as Cancelled when archived before they started, instead of failed
[Cloud sessions] Fixed a scheduled routine run that failed partway being run again from the start an hour or more later, which could repeat work such as posting the same report twice
Original changelog[Cloud sessions] History rewind and cross-device sync fixed, with precise launch failure messages
[Cloud sessions] Fixed "Rewind to here" failing on every message except the newest in cloud sessions; self-hosted runners need Claude Code v2.1.246 or later
[Cloud sessions] Fixed the pull request status bar in cloud sessions flipping a pull request with merge conflicts back to ready while GitHub rechecked it
[Cloud sessions] Fixed the diff view in cloud sessions missing changes or failing to load after the session's GitHub repository was renamed or moved
[Cloud sessions] Fixed an open cloud session sometimes not showing messages sent from another device until you reloaded the page or clicked away and back
[Cloud sessions] Improved the error shown when a cloud session fails to start: it now says "Connection lost" or "Server error" instead of "Something went wrong"
Original changelog[Claude Tag] Slack message formatting and image attachments fixed, preventing premature direct message drops
[Claude Tag] Fixed "is thinking…" staying up under a mention in a Slack channel or DM after Claude answered it by editing one of its earlier messages
[Claude Tag] Fixed URLs in code blocks under a numbered or bulleted step of Claude's Slack replies being wrapped in angle brackets, which broke copied commands
[Claude Tag] Fixed HEIC, SVG, TIFF and BMP images attached in Slack never reaching Claude; they now arrive as files in its working files, like other file types
[Claude Tag] Fixed Claude in Slack sometimes answering a direct message with "DMs are temporarily unavailable" and dropping it when a single Slack lookup stalled; it now retries first
[Claude Tag] Fixed direct messages with Claude on a Slack Enterprise Grid ignoring Slack's workspace dropdown; they now run under the connected workspace you last opened Claude in
[Claude Tag] Fixed links in Claude's Slack replies absorbing the closing bold or italic marks, or full-width punctuation, right after them, which broke the link and the formatting
Original changelog[Claude Tag] Admin Interface Reorganized into Four Tabs, Accelerating Repository and Channel Search
[Claude Tag] Improved repository search in Claude Tag admin settings to cover up to 100 connected GitHub accounts and find private repositories past the first 5,000 of a GitHub App install
[Claude Tag] Improved Add place in Claude Tag admin settings to list a channel you type or paste right away, instead of only after your organization's full channel list has loaded
[Claude Tag] Improved Add > Domain on a workspace's or channel's page in Claude Tag admin settings to be available once that page loads, not only after every channel has loaded
[Claude Tag] Changed Claude Tag admin settings to organize Claude's access into four tabs: Bundles, Connectors, Skills and plugins, and Channels
Original changelog[Claude Tag] Channel Manager Role Granted Automatic Permissions, Shared-Host Connectors Displayed Independently
[Claude Tag] Fixed new channel managers losing access to Claude in Slack in organizations that restrict Claude Tag by role; the manager role now also grants Claude Tag in Slack
[Claude Tag] Fixed custom connectors whose MCP servers share one host showing as a single connector in Claude Tag admin settings; each server is now its own connector
[Claude Tag] Fixed Claude in Slack's notice for a channel's monthly spend limit saying a channel manager can raise it; it now names an organization owner and links the usage page
[Claude Tag] Changed the Roles page in organization settings to group the roles created for Claude Tag channel managers in a collapsed section below your organization's own roles
Original changelog[Code Review] Setup Automatically Restores After Connecting GitHub, Reopening Directly to Repository Selection
[Code Review] Fixed Code Review setup not resuming after you leave to connect GitHub; back in admin settings, it now reopens at the repository picker