自動模式新增權限分頁,長對話安全審查放寬時限
你現在能更輕鬆查看並調整自動模式(auto mode,讓 Claude 不逐一詢問就自主執行的模式)的運作邊界了。在終端機輸入 /permissions,即可切換至新增的 Auto mode 分頁,直接檢視與編輯分類器的判定規則。同時,在處理內容極長的大型工作階段(session)時,工具呼叫不再動輒遭到拒絕。系統以前會將超長對話判定為暫時無法使用;現在安全審查的逾時時限會隨提示詞長度動態調整,確保大對話能順利通過檢查。
發布日期:2026-08-25
你現在能更輕鬆查看並調整自動模式(auto mode,讓 Claude 不逐一詢問就自主執行的模式)的運作邊界了。在終端機輸入 /permissions,即可切換至新增的 Auto mode 分頁,直接檢視與編輯分類器的判定規則。同時,在處理內容極長的大型工作階段(session)時,工具呼叫不再動輒遭到拒絕。系統以前會將超長對話判定為暫時無法使用;現在安全審查的逾時時限會隨提示詞長度動態調整,確保大對話能順利通過檢查。
撰寫 Bash 指令的自動放行規則時,安全性與防護機制有了更嚴謹的把關。若你在規則中的子指令前方加上萬用字元(例如 Bash(git * main)),啟動時會跳出警告,提醒該規則可能會意外放行插入在子指令前的其他參數。若指令語法不完整且末尾懸空帶有 && 或 || 運算子,權限檢查一律會強制要求手動確認,不再放行未完成的指令。此外,在 bash 環境下執行 Bash 工具時,重放快照函式不再為每個函式額外啟動 base64 子 shell,大幅降低指令執行的等待延遲。
背景工作階段(session)在各種極端環境下的啟動穩定度大幅提升。以往當啟動目錄被刪除、電腦進入睡眠或主機啟動程序較慢時,背景任務常在 45 秒後開啟失敗;現在已能妥善處理這些延遲。當另一個執行個體剛好在重新安裝 npm 套件時,也不會再因權限衝突拋出 EACCES 錯誤而無法啟動。在 Windows 等系統上,若你在工作行程剛開機時立刻於 claude agents 點開,任務不會再因重新生成途中被誤判停止。
在終端機同時管理多個背景任務,清單顯示與檔案清理現在更加井然有序。使用 claude agents 查看清單時,若將同一個命名對話再次轉入背景,清單不再重複列出兩筆相同名稱,而是會為新列自動加上流水號(例如 my-session (2))。背景清理機制也不會再誤刪你自己手動建立在 .claude/worktrees/ 底下的工作樹(worktree,Git 讓同一專案平行開多份副本的功能)。此外,在 Windows 與 macOS 環境下,無頭模式(headless,沒有終端機視覺介面的執行模式)會主動清理異常結束時殘留在 ~/.claude/sessions 的過期紀錄。
動態工作流與子代理的控制變得更加聰明。在工作流進行中按下向左鍵或執行 /background 時,系統不再直接重啟已完成的子代理,而是會先詢問並清楚列出有多少個子代理會被重啟。當子代理達到 maxTurns 回合上限時,回傳的結果會明確標示為部分完成,並附上透過 SendMessage 繼續執行的提示。而在 /goal 任務閒置期間,針對長程背景工作最多只會發起 3 次進度確認,待你送出下一則訊息後才會再允許 3 次。
透過 MCP(Model Context Protocol,讓 AI 連接外部工具的協定)擴充功能時,工具呼叫與授權判定更加準確。在無頭模式或遠端工作階段中,若工具呼叫被新訊息中斷,系統會回傳明確的中斷錯誤,不再誤報為「已完成但無輸出」。當工具參數的結構定義為空物件 {} 時,傳遞的引數會維持其真實型別,不再強制轉為 JSON 字串。使用 --strict-mcp-config 啟動時,不會再針對根本不會載入的 .mcp.json 伺服器跳出核准確認,避免背景任務卡在啟動階段。此外,針對標記為 requiresUserInteraction 的互動式工具,授權提示不再提供「一律放行且不再詢問」的無效選項。
終端機全螢幕模式與逐字稿檢視的體驗大幅改善。在全螢幕下調整視窗大小時,畫面不會再變成一片空白或強制跳到底部卡住。當你捲動到較早的歷史訊息時,捲動操作與跳至底部的動作更加順暢,不再停留在半途。當你點擊終端機視窗使其重獲焦點時,鍵盤焦點不會再被游標下方的控制元件搶走。此外,在全螢幕與 Ctrl+O 檢視長對話時,每個訊息列不再複製全域工具查找表,徹底解決記憶體隨工作階段(session)膨脹的問題。
長時間觀看終端機的對話進度與輸出結果,畫面呈現更清楚且不再卡頓。每回合結束的耗時提示行現在會明確標記完成的時間點(例如 ✻ Sautéed for 23s · done 6:05 PM)。當程式碼 diff 差異中包含極長的單行文字(例如 base64 編碼字串)時,系統會自動截斷並加上標記,防止畫面嚴重卡死。訊息排版也獲得修復,不再因為前 500 個字元沒有格式標記就誤把整則訊息的 Markdown 渲染關閉,並完整支援 + 與 N) 符號清單及底線標題。若指令執行到一半被中途切斷,狀態列會如實呈現中斷標示,不再顯示彷彿正常跑完的訊息。
終端機在接收提示詞與處理檔案路徑時變得更穩定。當你輸入以 /-- 開頭的文字(例如 Lean 語言的說明文件註解)時,系統會正常將內容發送給 Claude,不再誤判定為未知的斜線指令。使用 @ 挑選檔案時,若輸入的文字已經無法匹配任何現有路徑,檔案挑選器選單會自動關閉。此外,當補全字詞或當前工作目錄中包含空字元(null byte)時,路徑自動補全功能也不會再發生錯誤而失效。
想為終端機換上個人專屬色彩與快捷鍵,視覺效果與設定容錯現在更加可靠。使用 /rename 為對話命名時,提示詞外框會保留當前主題的設定色彩(包含自訂主題的 promptBorder),不再強制被覆蓋成預設的青色。自訂主題中的 diffAdded、diffRemoved 及其淡化色彩設定,現在也能如實呈現在程式碼比對與 /theme 預覽畫面中。此外,若在 keybindings.json 設定檔中綁定了未知的動作名稱,系統會主動跳過該項錯誤設定以保留鍵盤按鍵原本的預設功能,並在 --debug 模式下記錄除錯警告,不再無聲讓該按鍵失效。
終端機的統計數據與用量追蹤修復了多處顯示偏差。當你在主對話與代理檢視畫面之間切換移動時,狀態列(status line,終端機最底下那行即時資訊)記錄的累計費用與執行耗時不會再意外歸零。在台灣與日本等東半球時區使用 /stats 查看活動熱圖時,各天的使用次數不再發生向後偏移一格(將週日的次數錯放在週一底下)的時區計算錯誤,讓每日工作量真實呈現。
在同一個對話中切換工作目錄,相關設定與模式銜接更加完整。使用 /cd 切換至新目錄後,該專案的專案設定、掛鉤(hook,特定事件發生時被觸發的小程式)、需確認授權的 .mcp.json 伺服器、技能與代理等元件,現在會立刻生效,不再需要透過 --resume 重新載入。針對已經分叉或背景化的工作階段(session),輸入 /fork 派生新對話時不會再出現空無一物的空白歷史。此外,若先前是在計畫模式結束對話,在 VS Code 擴充套件或使用 claude -p --continue 接續執行且未指定權限模式時,系統能正確維持原有的計畫模式。
外掛 plugin 的安裝、更新與快取(把算過或查過的結果暫存起來直接用)管理修正了多處異常。執行 claude plugin update 時,現在可以直接傳入簡短的套件純名稱,不再強制要求完整命名空間。當外掛的 plugin.json 包含 UTF-8 BOM 檔頭時不再導致安裝失敗。若市集清單檔案 known_marketplaces.json 空白或損毀,執行安裝指令會明確回報錯誤,不再無聲退出或卡死。此外,外掛快取不會再為同一個外掛建立多個重複的 SHA 資料夾;同步自 claude.ai 的外掛在遙測中也能正確標記真實市集與管理員安裝來源。
開發或載入外掛技能與掛鉤(hook,特定事件發生時被觸發的小程式)時,名稱顯示與路徑解析更加精確。如果外掛技能在定義中已帶有 <plugin>: 前綴,斜線選單不會再出現重複的前綴字樣(例如 /plugin:plugin:skill)。針對採用 skills/*/SKILL.md 目錄結構的外掛,輸入 /reload-plugins 重新載入時能正確讀取所有技能,不再誤報為 0 個技能。此外,當掛鉤執行發生錯誤時,錯誤訊息會顯示解析後的完整本機路徑,不再印出未替換的原始文字 ${CLAUDE_PLUGIN_ROOT}。
串接第三方相容 API 閘道時,穩定度與憑證安全性獲得全面提升。當自訂端點(ANTHROPIC_BASE_URL)串流傳回沒有 id 欄位的工具呼叫區塊時,介面不會再拋出渲染錯誤而中止。接續先前的歷史對話時,若紀錄中包含第三方代理伺服器寫入的特殊工具區塊,也不會再導致每次對話都觸發 400 錯誤。更重要的是,系統向 Anthropic 發送遙測與指標請求時,不再夾帶設定給第三方閘道的 API 金鑰,各主機的金鑰只會發送至各自對應的伺服器。
企業環境透過自訂指令取得短效憑證時,驗證流程更加順暢。若透過 apiKeyHelper 取得短期的 JWT 授權令牌(token,用來驗證身分的授權令牌),在閒置過期後送出第一則訊息時,系統會在發送前自動更新快取,並在遭遇 401 或 403 驗證錯誤時於背景自動重試,不再彈出錯誤畫面。工作負載身分同盟、啟動期間以及登入過期後的用量數據,現在也能更精準歸屬至所屬組織。此外,在 Bedrock、Vertex AI、Foundry、Claude 應用程式閘道或停用非必要流量的環境下,Claude 現在也能自主發起 /code-review 進行程式碼審查。
讓雲端環境或背景工作自動修復程式碼,多任務協同與斷線復原能力更上一層樓。從同一個專案的多個工作樹同時啟動 /ultrareview 或雲端工作階段(session)時,不再混入另一次啟動的未提交變更。背景雲端任務(例如 /autofix-pr)的進度計數不會再漏算任務數量。在遠端控制(Remote Control)中,自動產生的對話標題在第一則提示詞後就會立即更新至網頁版與 App。自託管執行器若收到格式錯誤的輪詢回應(例如中繼代理回傳的 HTML 頁面),會自動重試而非直接退出。而在非互動模式下若因伺服器錯誤或網路斷線導致輸出中斷,系統會自動接續生成。
覆寫超大型既有檔案或在沙盒執行指令,底層處理與安裝管理變得更穩定。使用 Write 工具覆寫龐大檔案後,即使寫入成功,以往常會長時間卡死或誤報記憶體不足,現在已能流暢返回。沙盒在等待「沙盒外網路請求」權限確認時,會正常觸發 Notification 掛鉤(hook,特定事件發生時被觸發的小程式)。指令沙盒的檔案系統設定能確實遵循 --setting-sources 參數。此外,企業受管設定用戶透過 curl 腳本安裝時不再報出 Raw mode 錯誤,執行 claude install 與 claude update 也會將受管設定同意提示遞延至下一次互動工作階段,不再中途打斷指令。
Managing the boundaries of auto mode is now much more straightforward. Running /permissions introduces a dedicated Auto mode tab for viewing and editing classifier rules. Furthermore, tool calls during very large sessions are no longer denied with a "temporarily unavailable" error; the safety-check deadline now scales dynamically with prompt size, giving extensive sessions ample time to complete validation.
Security checks and execution latency for Bash commands are significantly improved. When defining Bash allow rules with a wildcard placed before the subcommand (such as Bash(git * main)), Claude Code now displays a startup warning because that pattern also inadvertently matches options inserted before the subcommand. Malformed commands that leave a trailing && or || operator dangling will now strictly require explicit user approval. Furthermore, executing the Bash tool in bash environments now replays snapshot functions without spawning an extra base64 subshell per function, speeding up command startup.
Launching background sessions is now significantly more dependable across edge cases. Previously, if the starting directory was removed, the computer slept, or the host was slow to spawn processes, background sessions would fail to open after 45 seconds; these delays are now handled smoothly. Background service startup no longer crashes with an EACCES error when another Claude Code instance is reinstalling npm packages at that exact moment. On Windows and other platforms, opening a freshly spawned session in claude agents while its worker boots no longer halts it prematurely with an in-flight respawn error.
Managing multiple background tasks in the terminal is cleaner and safer. When viewing claude agents, backgrounding a conversation that shares a name with an existing session no longer prints identical duplicate rows; instead, it automatically appends an incremental number (such as my-session (2)). The background retention cleanup sweep will no longer remove git worktrees (a Git feature for opening parallel working copies of a project) located under .claude/worktrees/ that you created manually, even if an older session points toward them. Additionally, on Windows and macOS, headless sessions cleanly purge stale records in ~/.claude/sessions left behind after unexpected terminations.
Subagent workflows are much more cooperative. Pressing the left arrow key or running /background during a dynamic workflow no longer silently restarts already-finished subagents; it asks for confirmation first and displays how many subagents would restart. When a subagent hits its maxTurns limit, it returns output marked as partial with a hint to resume via SendMessage, rather than masquerading as fully finished. For /goal tasks, idle sessions now start at most three check-ins on long-running background jobs, with your next message allowing three more.
Tool invocations and permission prompts over MCP (Model Context Protocol, an open standard connecting AI to external tools) are far more reliable. In headless or remote sessions, if an MCP tool call is interrupted by an incoming message, Claude now receives an explicit interrupted error instead of an empty successful output. Tool parameters with empty schemas ({}) receive arguments matching their real data types rather than raw JSON strings. Under --strict-mcp-config, Claude Code skips permission prompts for .mcp.json servers that will never load, preventing background sessions from hanging at startup. Interactive tools marked requiresUserInteraction also no longer show the non-functional "Yes, and don't ask again" choice.
Fullscreen and transcript view interactions are noticeably smoother. Resizing the terminal in fullscreen mode no longer renders a blank transcript or snaps to the bottom until the next keystroke. Scrolling through older messages and jumping to the bottom no longer stutters mid-transcript. Clicking the terminal window simply to restore window focus won't shift keyboard focus onto the UI control sitting under the cursor. Additionally, message rows in fullscreen and Ctrl+O views no longer hold copies of tool lookup tables, stopping memory growth on long sessions.
Terminal output and status formatting are much more informative. The duration line at the end of each turn now appends the exact completion timestamp (such as ✻ Sautéed for 23s · done 6:05 PM). When a code diff contains a massive single line (like a base64 string), Claude Code truncates it with a marker to prevent terminal slowdowns. Markdown parsing no longer disables rendering across an entire response simply because the first 500 characters lacked formatting, and properly formats + and N) lists alongside setext headings. If a running shell command is aborted mid-run, the interface explicitly marks it as cut rather than printing a deceptive finished message.
Input parsing and path autocompletion handle edge cases gracefully. Prompts beginning with /-- (such as Lean doc comments) are cleanly forwarded to Claude rather than being rejected as nonexistent slash commands. The @ file picker automatically dismisses itself as soon as typed characters stop matching any filesystem path. Furthermore, path autocompletion no longer breaks when completion tokens or directory paths contain null bytes.
Theme styling and keyboard customization are much more resilient. Running /rename to title a session now preserves your active theme prompt border color (including custom theme promptBorder definitions) instead of reverting to default cyan unless changed with /color. Custom theme diff highlights (diffAdded, diffRemoved, and their dimmed variants) correctly display in rendered diffs and within the /theme preview. Furthermore, binding an unrecognized action name in keybindings.json no longer deadens that key; Claude Code now skips the invalid action, keeps the default keybinding alive, and logs a descriptive warning when launched with --debug.
Status metrics and usage charts now report accurate figures. Navigating between the main conversation and the agent task view no longer clears the status line's accumulated cost and session duration back to zero. Additionally, running /stats in timezones east of UTC no longer shifts daily activity heatmap cells by one day (which previously plotted Sunday counts under Monday), ensuring daily totals match your actual calendar schedule.
Switching directories and continuing workflows is much smoother. When running /cd to navigate into another project directory, its project settings, hooks (small automated scripts triggered by events), approvable .mcp.json servers, skills, and agents take effect immediately without requiring --resume. Running /fork from an already-forked or backgrounded session now brings along the active conversation history instead of opening a blank screen. Furthermore, sessions that ended in plan mode properly remain in plan mode when resumed within the VS Code extension or via claude -p --continue without explicit permission mode flags.
Plugin management and caching are much more polished. Running claude plugin update now accepts an installed plugin's bare name without requiring fully-qualified namespace identifiers. Installing plugins whose plugin.json files contain UTF-8 byte-order marks (BOM) no longer fails. If known_marketplaces.json is corrupted or empty, claude plugin install prints a helpful error rather than hanging or silently exiting. Furthermore, plugin caching stops creating duplicate SHA-named directories for the same package, and OpenTelemetry events for plugins synced from claude.ai correctly log authentic marketplace metadata and admin-installed status.
Plugin skills and hooks (automated scripts triggered by specific events) now resolve naming and directory paths accurately. When a plugin skill includes the <plugin>: prefix in its frontmatter name, slash menus no longer render doubled prefixes like /plugin:plugin:skill. Running /reload-plugins correctly discovers skills organized under the skills/*/SKILL.md file pattern instead of mistakenly reporting zero skills. Furthermore, hook error messages print the fully-resolved local plugin path instead of displaying the unexpanded literal ${CLAUDE_PLUGIN_ROOT} template string.
Using Anthropic-compatible third-party gateways and proxies is safer and more reliable. When a custom endpoint (ANTHROPIC_BASE_URL) streams a tool_use payload without an id, Claude Code no longer halts with a UI rendering error. Resuming sessions whose histories include proxy-generated tool blocks rejected by Anthropic APIs will no longer cause continuous 400 errors on each turn. Crucially, telemetry and metrics sent to Anthropic will no longer carry the API key designated for third-party gateways; credentials are sent strictly to their matching host.
Authentication handling and enterprise telemetry attribution have been updated. When using apiKeyHelper to fetch short-lived JWT tokens (authentication strings proving identity), sending a prompt after an idle period now refreshes expired cached tokens before transmission and quietly retries on 401 or 403 status codes. Usage metrics for workload identity federation sessions, startup helper scripts, and post-idle token refreshes are also accurately attributed to your organization. Furthermore, Claude can now autonomously trigger /code-review across Bedrock, Vertex AI, Foundry, the Claude apps gateway, and setups where non-essential traffic is disabled.
Cloud workflows, Remote Control, and automated runners have received significant stability enhancements. Launching /ultrareview and cloud sessions concurrently from different worktrees in the same repository no longer incorporates uncommitted changes from another launch. Cloud background workflows like /autofix-pr reliably track task progress (e.g. 3/5) without skipping tasks. Remote Control sessions show auto-generated conversation titles across claude.ai and mobile apps right after the first prompt. Self-hosted runners retry upon receiving malformed responses (such as proxy error pages) instead of quitting. Furthermore, non-interactive sessions (-p, SDK, and cloud runs) automatically resume stream cutoffs caused by network loss or server stalls.
File operations, sandbox boundaries, and enterprise installation flows have been reinforced. Overwriting a large existing file with the Write tool no longer freezes the session or incorrectly claims out-of-memory errors after a successful write. The Notification hook (an automated script triggered by system events) now fires properly while the sandbox waits on user permission for external network requests. Command sandbox filesystem restrictions strictly honor the --setting-sources flag. Furthermore, Team and Enterprise installations via curl scripts no longer fail with "Raw mode is not supported" errors, and running claude install or claude update defers managed-settings consent prompts to your next interactive session instead of interrupting command execution.
Added an Auto mode tab to `/permissions` for viewing and editing auto mode classifier rules
Fixed auto mode tool calls being denied as "temporarily unavailable" on very large sessions by scaling the safety-check deadline with prompt sizeAdded a startup warning for Bash allow rules with a wildcard before the subcommand (e.g. `Bash(git * main)`), since they also match options inserted before the subcommand
Fixed Bash permission checks to always require approval for malformed commands with a dangling `&&` or `||` operator
Improved Bash tool latency on bash shells by replaying snapshot functions without a base64 subshell per functionFixed background sessions failing to open after 45 seconds when Claude Code's starting directory had been deleted, the machine had slept, or the host is slow to start processes
Fixed background sessions failing to open with "Couldn't start the background service … EACCES" when another Claude Code process was re-installing the npm package at that moment
Fixed opening a just-started session in `claude agents` while its worker was still booting (common on Windows) stopping it with "was stopped while the respawn was in flight"Fixed `claude agents` listing a backgrounded named session twice; backgrounding the same conversation again now numbers the new row (e.g. `my-session (2)`)
Fixed the background retention sweep removing git worktrees under `.claude/worktrees/` that you created yourself when an old background-session record pointed at them
Windows/macOS: Fixed headless sessions not cleaning up stale entries in `~/.claude/sessions` left by sessions that exited uncleanlyFixed pressing ← or running `/background` during a dynamic workflow restarting its finished subagents; it now asks first and says how many subagents would restart
Improved subagent results: a subagent that stops at its `maxTurns` limit now returns its output marked as partial, with a hint to continue it via `SendMessage`, instead of appearing finished
`/goal`: Changed idle sessions to start at most three check-ins on long-running background work per goal; your next message allows three moreFixed MCP tool calls interrupted by an incoming message in headless/remote sessions being reported to the model as "completed with no output" instead of an explicit interrupted error
Fixed MCP tool arguments being sent as JSON strings when the parameter's schema is empty (`{}`), instead of their real type
Fixed `--strict-mcp-config` sessions prompting to approve `.mcp.json` servers they would never load, which left background sessions waiting at startup
Fixed MCP tools marked `requiresUserInteraction` still offering "Yes, and don't ask again" in their permission prompt; the option wrote an allow rule the tool then ignoredFixed fullscreen mode showing a blank transcript after resizing the terminal and jumping to the bottom until the next keypress
Fixed erratic fullscreen scrolling when positioned at an earlier message, including jump-to-bottom getting stuck mid-transcript
Fixed fullscreen mode moving keyboard focus onto the control under the pointer when you clicked the terminal window only to bring it back into focus
Fixed memory growing with session length in the fullscreen and Ctrl+O transcript views: each rendered message row no longer retains a full copy of the transcript-wide tool lookupsAdded the turn's completion time to the end-of-turn duration line, e.g. `✻ Sautéed for 23s · done 6:05 PM`
Fixed a severe transcript slowdown when a diff contained a very long single line (e.g. a base64 string); such lines now render truncated with a marker
Fixed markdown rendering being disabled for a whole message when its first 500 characters contained no markdown, and for `+`/`N)` lists and setext headings
Fixed a command interrupted mid-run showing as "Ran 1 shell command" with no sign it was cutFixed prompts beginning with `/--` (e.g. Lean doc comments) being rejected as an unknown slash command instead of being sent to Claude
Fixed the `@` file picker staying open after the typed text stopped matching a real path
Fixed path completion failing when the completion token or working directory contained a null byteFixed `/rename` replacing the theme's prompt border color (including a custom theme's `promptBorder`) with the default cyan; the border now keeps your theme's color unless you pick one with `/color`
Fixed custom theme diff colors (`diffAdded`/`diffRemoved` and their dimmed variants) being ignored in diffs and the `/theme` preview
Fixed a `keybindings.json` binding with an unknown action name silently deadening that key; it is now skipped so the default binding keeps working, and a warning is logged under `--debug`Fixed `/stats` activity heatmap showing each day's activity one cell off (Sunday's count under Monday) in timezones east of UTC
Fixed the status line's cost and duration resetting to zero after navigating to the agents view and backFixed `/fork` from an already-forked or backgrounded session starting the new session with an empty conversation
Fixed sessions that ended in plan mode resuming outside plan mode in the VS Code extension, and in `claude -p --continue`/`--resume` with a permission prompt tool, when no permission mode was set
Improved `/cd`: the new directory's project settings, hooks, `.mcp.json` servers (behind the usual approval prompt), skills, and agents now take effect right after the move instead of on `--resume`Fixed the plugin cache creating duplicate SHA-named directories for the same plugin
Fixed `claude plugin update` failing for an installed plugin given its bare name (only the fully-qualified name worked)
Fixed plugin installation failing when `plugin.json` was saved with a UTF-8 byte-order mark (BOM)
Fixed `claude plugin install <name>` exiting silently (or hanging in a terminal) instead of reporting an error when `~/.claude/plugins/known_marketplaces.json` is empty or corrupted
Changed OpenTelemetry plugin events for plugins synced from claude.ai: `plugin_id_hash` now reflects the plugin's real marketplace, and `enabled_via` is `admin-install` for admin-installed pluginsFixed plugin skills whose frontmatter `name` already includes the `<plugin>:` prefix showing it doubled in the slash menu (e.g. `/plugin:plugin:skill`)
Fixed `/reload-plugins` reporting 0 skills for plugins that define skills under `skills/*/SKILL.md`
Fixed hook error messages showing a literal `${CLAUDE_PLUGIN_ROOT}` instead of the resolved plugin pathFixed the UI stopping with a render error on the first tool call when a third-party Anthropic-compatible endpoint (`ANTHROPIC_BASE_URL`) streams a `tool_use` block without an `id`
Fixed resumed sessions failing every turn with a 400 when the saved history contains tool blocks the Anthropic API does not accept (typically written by a third-party API proxy)
Fixed telemetry and metrics requests to Anthropic carrying the API key configured for a third-party gateway (`ANTHROPIC_BASE_URL`); a credential is now only sent to its own hostFixed a visible API error on the first prompt after idle when `apiKeyHelper` returns short-lived JWTs: an expired cached token is now refreshed before sending, and 401/403 auth errors retry quietly
Improved attribution of usage telemetry to your organization for workload identity federation sessions, events sent while `apiKeyHelper` runs at startup, and after a login token expired while idle
Changed `/code-review` so Claude can also start it on its own on Bedrock, Vertex AI, and Foundry, through the Claude apps gateway, and when telemetry or non-essential traffic is disabledFixed `/ultrareview` runs and cloud sessions launched at the same time from one repository (e.g. from several worktrees) sometimes starting with another launch's uncommitted changes
Fixed the task progress count (e.g. `3/5`) shown for background cloud sessions such as `/autofix-pr` occasionally missing a task
Fixed Remote Control sessions keeping their placeholder name in claude.ai and the Claude app until the second prompt; the auto-generated title now appears after the first prompt
Fixed the self-hosted runner ending its live sessions or exiting when a work-poll response is malformed (e.g. an intercepting proxy's HTML page); it now retries the poll
Improved non-interactive sessions (`-p`, SDK, cloud sessions) to automatically continue a response cut off mid-stream by a server error, connection loss, or stall instead of ending with an errorFixed the Write tool reporting "Out of memory" or freezing for a long time after overwriting a very large existing file, even though the file had been written
Fixed the `Notification` hook not firing while the sandbox "Network request outside of sandbox" permission prompt is waiting
Fixed the command sandbox's filesystem configuration not respecting `--setting-sources`
Fixed `curl -fsSL https://claude.ai/install.sh | bash` failing with "Raw mode is not supported" for some Team/Enterprise users with server-managed settings
Changed `claude install` and `claude update` to defer a pending managed-settings consent prompt to the next interactive session instead of prompting mid-command