Changes on 2026-03-30

用户想要一份关于 Claude 文档更改的简洁而有见地的分析。我需要查看这 7 个页面的差异并总结： 1. 整体摘要 2. 跨页面的关键主题 3. 影响级别（低/中/高/破坏性）并附上理由 4. 开发者行动项目（最多 5 点） 让我们逐一分析这些更改： **1. desktop.md (+15/-5)** - 更新了在桌面应用中启用“computer use”的说明 - 重构为步骤格式（<Steps>） - 将“Settings > Desktop app > General”更新为“Settings > General (under Desktop app)” - 添加了关于更新应用和确认计划/操作系统的详细信息 - 调整了应用权限的设置路径 **2. hooks.md (+3/-5)** - 更新了“TaskCreated”钩子描述：从“防止任务创建”改为“回滚任务创建” - 更新了调试说明：移除了 `Ctrl+O` 详细模式切换 - 添加了新的环境变量 `CLAUDE_CODE_DEBUG_LOG_LEVEL=verbose` 用于更精细的调试 **3. terminal-config.md (+2/-0)** - 添加了关于减少闪烁和内存使用的说明 - 介绍了 `CLAUDE_CODE_NO_FLICKER=1` 用于全屏渲染 **4. about-claude/models/overview.md (+3/-0)** - 添加了说明，指出了批次 API 上新的“extended output”功能 - Opus 4.6 和 Sonnet 4.6 现在支持 `output-300k-2026-03-24` beta 标头，最高可达 300k 输出 token **5. build-with-claude/extended-thinking.md (+1/-1)** - 更新了说明以匹配批次 API 上的新 300k 输出支持 - 添加了指向批次 API 文档的链接 **6. build-with-claude/batch-processing.md (+70/-0)** - 大幅新增了“扩展输出（beta）”部分 - 解释了批次 API 上新的 300k token 输出限制 - 提供了多个代码示例 **7. CHANGELOG.md.md (+42/-0)** - 版本 2.1.88 的广泛错误修复和新功能 - 包含 `CLAUDE_CODE_NO_FLICKER=1`、`PermissionDenied` 钩子、各种 bug 修复（内存泄漏、Windows CRLF 问题、缓存 bug） **整体摘要：** 本次更新引入了桌面应用工作流程的改进、批次 API 上高达 300k 输出 token 的新增扩展输出功能，以及终端渲染和钩子的多个错误修复和增强。 **关键主题：** 1. **扩展输出能力**：批次 API 上新的 300k token 输出限制 2. **桌面应用 UX 改进**：“computer use”和权限的更好说明 3. **终端稳定性**：新的防闪烁渲染、内存泄漏修复 4. **钩子和调试增强**：改进的钩子行为、新的调试选项 5. **Bug 修复**：Windows CRLF 问题、缓存 bug、各种崩溃修复 **影响级别：** 中高。新增的 300k 输出支持对长文档生成意义重大。桌面应用的说明是用户体验改进而非破坏性变更。修复提高了稳定性。 **开发者行动项目：** 1. 如需生成长文档，请在批次 API 上利用新的 300k 输出限制 2. 如果终端闪烁，测试 `CLAUDE_CODE_NO_FLICKER=1` 3. 检查钩子实现，特别是针对 `TaskCreated`，行为已从“防止创建”变为“回滚创建” 4. 更新任何依赖特定输出 token 限制的代码 5. 试用新的 `CLAUDE_CODE_DEBUG_LOG_LEVEL=verbose` 进行钩子调试 让我用中文进行总结。

1. **Analyze the Request:** * **Role:** World-class programmer analyzing documentation changes. * **Input:** A diff of a single documentation page (`claude-code-on-the-web.md`). * **Output Language:** Chinese. * **Format:** Markdown. * **Sections:** Overall Summary, Key Themes, Impact Level (with reasoning), Action Items for Developers (max 5). 2. **Analyze the Input Diff:** * **File:** `claude-code-on-the-web.md`. * **Content Change:** Added a new section "From the terminal" under "Getting started". * **Specifics:** * Introduces the `/web-setup` command. * Allows setting up Claude Code on the web directly from the terminal using existing local `gh` (GitHub CLI) credentials. * Syncs `gh auth token` to the cloud environment. * Fallback mechanism: If `gh` isn't installed, it falls back to browser-based setup. * Clarification on permissions: `gh` credentials allow cloning/pushing; the GitHub App is only needed for specific features like "Auto-fix". * Admin note: This feature can be disabled via admin settings. 3. **Synthesize the Analysis (Internal Monologue):** * *Summary:* The documentation update introduces a terminal-based workflow (`/web-setup`) for initializing Claude Code on the web, leveraging existing GitHub CLI credentials to streamline the setup process. * *Key Themes:* * Streamlining onboarding (developer experience). * CLI-to-Cloud integration. * Credential management/reuse (using `gh` CLI). * Permission granularity (native CLI vs. GitHub App). * *Impact Level:* Medium. It's a new workflow feature that significantly improves convenience for existing CLI users, but it's not a breaking change and doesn't drastically alter core functionality logic. * *Action Items:* * Try the `/web-setup` command if already using `gh` CLI. * Understand the difference between just using the token vs. installing the GitHub App (for Auto-fix). * Check admin settings if in an enterprise environment to see if this is allowed. 4. **Drafting the Response (in Chinese):** * *Summary:* 文档新增了通过终端（CLI）初始化 Claude Code Web 端的功能。引入了 `/web-setup` 命令，允许用户复用本地的 `gh` (GitHub CLI) 凭证来快速配置云端环境，从而简化了设置流程。 * *Key Themes:* * **CLI 驱动的云端配置**：新增终端命令直接启动并配置 Web IDE，无需手动在浏览器中授权。 * **凭证复用**：利用本地已认证的 GitHub CLI (`gh`) 凭证同步至云端，实现无缝衔接。 * **权限颗粒度**：明确了使用 CLI 凭证与安装 GitHub App 的区别（后者仅用于 Auto-fix 功能）。 * **降级处理**：提供了完善的回退机制，若无 `gh` CLI 则自动跳转至网页授权。 * *Impact:* **Medium**。这是一个提升开发者体验（DX）的便利性功能，虽然不破坏现有功能，但为重度 GitHub CLI 用户提供了更快捷的入口。 * *Action Items:* * 尝试在 Claude Code 中运行 `/web-setup` 命令以快速连接 GitHub。 * 确保本地已安装并登录 `gh` CLI 以获得最佳体验。 * 若需要 PR 自动修复（Auto-fix）功能，仍需安装 Claude Code GitHub App。 * 团队管理员可通过后台设置禁用此快速启动功能。 5. **Review and Refine:** * Does it meet the "world-class programmer" persona? Yes, concise and technical. * Is it in Chinese? Yes. * Is it in Markdown? Yes. * Are the sections correct? Yes. 6. **Final Output Generation:** (Proceed to generate output based on the drafted points).

1. **Analyze the Request:** * **Role:** World-class programmer analyzing documentation changes. * **Output Format:** Markdown, concise, insightful, Chinese language. * **Input:** 11 pages of diffs. * **Task:** Batch analysis summarizing changes, themes, impact, and action items. 2. **Analyze the Diffs (Page by Page):** * **Page 1: `claude-code-on-the-web.md`** * *Change:* Added support for self-hosted GitHub Enterprise Server (GHES) in "Platform restrictions" section. (Teams and Enterprise plans). * *Significance:* Expands platform compatibility for Claude Code on the Web. * **Page 2: `network-config.md`** * *Change:* Added instruction to allowlist Anthropic API IP addresses for self-hosted GitHub Enterprise Server instances behind firewalls. * *Significance:* Network configuration guidance for GHES users. * **Page 3: `plugin-marketplaces.md`** * *Change:* Added a recommendation to use regex pattern matching for internal git servers, specifically mentioning GitHub Enterprise Server (GHES). * *Significance:* Best practice guidance for plugin marketplace configuration. * **Page 4: `about-claude/models/overview.md`** * *Change:* Updated the "Context window" column in the models table. Previously, Sonnet 4.5 and 4 had 1M (or 200k) options. Now, only Opus 4.6 and Sonnet 4.6 have 200k listed (Wait, looking closer at the diff). * *Deep Dive:* The diff shows the table row changing from mentioning 1M for Opus/Sonnet to just "200k tokens" for all listed rows (Opus 4.6, Sonnet 4.6, Sonnet 4.5, Sonnet 4, Haiku 4.5). Wait, looking at the table structure: * Opus 4.6: "200k tokens" (previously 1M or 200k). * Sonnet 4.6: "200k tokens". * Sonnet 4.5: "200k tokens". * Sonnet 4: "200k tokens". * Haiku 4.5: "200k tokens". * *Correction:* Looking at the context of other pages, Opus 4.6 and Sonnet 4.6 retain 1M. The table row in this specific diff looks simplified. Let's look at the footer notes. Note 1 was removed (explaining the 1M beta header and long context pricing). Note 2 became Note 1 (explanation of cutoffs). Note 3 became Note 2. * *Interpretation:* The table itself seems to have been simplified to show the default/base context window (200k), or perhaps the 1M option for Opus 4.6/Sonnet 4.6 isn't explicitly shown in the *tooltip* of the table cell anymore, relying on the text description elsewhere. Or, looking at `context-windows.md` (Page 8), Opus 4.6 and Sonnet 4.6 *do* have 1M. * *Crucial Observation:* The removal of Note 1 (the one explaining 1M context for Sonnet 4.5/4) indicates Sonnet 4.5 and 4 **lost** their 1M context capability (beta removed/cancelled). * **Page 5: `about-claude/pricing.md`** * *Change:* Removed the entire section "Long context pricing" specific to Sonnet 4.5 and Sonnet 4. * *Change:* Updated "stacking" sentence to remove "long context pricing". * *Significance:* Confirms that the premium long context pricing for Sonnet 4.5/4 is gone because the feature (1M context) is gone for them. Only Opus 4.6 and Sonnet 4.6 keep 1M at standard pricing (as seen in the remaining text). * **Page 6: `api/service-tiers.md`** * *Change:* Removed lines regarding burndown rates for long-context requests (>200k) on Sonnet 4.5 and Sonnet 4. * *Significance:* Consistent removal of the beta feature logic. * **Page 7: `build-with-claude/prompt-caching.md`** * *Change:* Removed "long context pricing" from the list of modifiers that stack with prompt caching. * *Significance:* Documentation clean-up following the pricing change. * **Page 8: `build-with-claude/context-windows.md`** * *Change:* Rewrote the paragraph about context windows. * *Old:* "Claude Opus 4.6 and Sonnet 4.6 have a 1M-token context window. [Note about Sonnet 4.5/4 beta header]." * *New:* "Claude Opus 4.6 and Sonnet 4.6 have a 1M-token context window. Other Claude models, including Claude Sonnet 4.5 and Sonnet 4, have a 200k-token context window." * *Significance:* **MAJOR**. Explicitly states Sonnet 4.5 and 4 are capped at 200k now. The beta 1M context is gone. * **Page 9, 10, 11 (Cloud Providers: Bedrock, Vertex, Foundry)** * *Change:* All three pages show similar updates. * *Pattern:* Changed text from "Opus 4.6, Sonnet 4.6, Sonnet 4.5, and Sonnet 4 have a 1M-token context window..." to "Claude Opus 4.6 and Sonnet 4.6 have a 1M-token context window... Other Claude models... have a 200k-token context window." * *Significance:* Consistency across cloud platforms. The beta removal is universal. 3. **Synthesize Themes:** * **Theme 1: GitHub Enterprise Server (GHES) Support.** * `claude-code-on-the-web.md`: Now supported for Teams/Enterprise. * `network-config.md`: Firewall allowlisting instructions added. * `plugin-marketplaces.md`: Recommended regex approach for GHES. * **Theme 2: Model Context Window Changes (Breaking/Significant).** * **Retraction:** The beta 1M-token context window for Claude Sonnet 4.5 and Sonnet 4 has been removed/cancelled. * **Current State:** Only Claude Opus 4.6 and Sonnet 4.6 support 1M tokens. * **Pricing:** Removed premium long-context pricing for Sonnet 4.5/4 since they no longer support >200k context. 4. **Determine Impact:** * **GHES Support:** **Low to Medium** impact. Only affects organizations using self-hosted GitHub and Claude Code on the Web. Positive news for them. * **Context Window Changes:** **High Impact** (Breaking for beta users). Developers relying on the 1M beta header for Sonnet 4.5 or 4 will find their requests truncated or fail if they attempt >200k tokens. This removes a capability that was in beta. 5. **Formulate Action Items:** * **For Sonnet 4.5/4 users:** Stop using the `context-1m-2025-08-07` beta header. Expect requests >200k tokens to be capped at 200k. * **Migration:** If you need >200k context, switch to Opus 4.6 or Sonnet 4.6. * **GHES Admins:** Update firewall rules to allow Anthropic API IPs. * **GHES Plugin Devs:** Use regex patterns for internal server configuration. 6. **Drafting the Response (in Chinese):** * *Summary:* Added GHES support for Claude Code on the Web; removed 1M context beta for Sonnet 4.5 and 4, capping them at 200k. * *Themes:* 1. GHES Integration (Web + Network + Plugins). 2. Context Window Rollback (Sonnet 4.5/4 limited to 200k). * *Impact:* High (due to feature removal for specific models) / Medium (GHES support is additive). Let's call it "High" because removing a beta feature is technically a breaking change for those using it. * *Actions:* 1. Migrate to Opus 4.6/Sonnet 4.6 for 1M context. 2. Remove beta header. 3. Configure firewalls for GHES. 7. **Refining the Output (Self-Correction):** * Make sure to distinguish between *Claude Code* (the IDE agent) and *Claude API*. * The GHES changes are specific to `claude-code-on-the-web`, not necessarily the general API connecting to GHES (though the network config implies cloud infrastructure connecting to GHES). * The context window changes apply to API, Bedrock, Vertex, and Foundry. 8. **Final Polish (Markdown Structure):** * Use bolding for emphasis. * Keep it concise. **(Self-Correction during drafting):** Wait, looking at `models/overview.md`, the context window cell for Opus 4.6 and Sonnet 4.6 *also* shows "200k tokens" in the diff. This seems to be a simplification of the table to show the *default* or perhaps a data error in the diff representation? However, `context-windows.md` explicitly says: "Claude Opus 4.6 and Sonnet 4.6 have a 1M-token context window." This text was not deleted, only the Sonnet 4.5/4 beta note was deleted. Therefore: Opus 4.6/Sonnet 4.6 still have 1M. Sonnet 4.5/4 lost it. The table in `overview.md` just got simpler (perhaps hiding the "or 200k" nuance or just showing the row value generically). I will trust the explicit text in `context-windows.md` over the simplified table cell. Let's stick to the facts derived: 1. GHES support added for Claude Code on the Web. 2. Sonnet 4.5 and 4 are capped at 200k (1M beta removed). 3. Opus 4.6 and Sonnet 4.6 keep 1M. Action items need to be sharp. Final check on language: Chinese. Let's write the response.

1. **Analyze the Request:** * **Role:** World-class programmer with expertise in developer tools/docs. * **Task:** Analyze documentation changes as a single batch. * **Format:** Markdown, concise, insightful, Chinese. * **Input:** 4 pages with diffs (`cli-reference.md`, `desktop.md`, `model-config.md`, `vs-code.md`). 2. **Analyze the Diffs:** * **Page 1: `cli-reference.md`** * *Change:* Modified the description of `--enable-auto-mode`. * *Old:* "Requires a Team plan (Enterprise and API support rolling out shortly)..." * *New:* "Requires a Team, Enterprise, or API plan..." * *Meaning:* Auto mode is now officially available for Enterprise and API plan users, not just "rolling out". * **Page 2: `desktop.md`** * *Change:* Modified the "Auto" row in the permission modes table. * *Old:* "Available on Team plans (Enterprise rolling out shortly)." * *New:* "Available on Team, Enterprise, and API plans." * *Meaning:* Consistent with the CLI change. The "Auto" mode is now generally available to higher-tier plans. * **Page 3: `model-config.md`** * *Change:* Significant updates to the "Control the model users run on" section. * *Old:* Brief explanation of `availableModels` and `model`. * *New:* Clarified that `model` is just initial selection, not enforcement. Added explanation of environment variables (`ANTHROPIC_DEFAULT_*`) to control what "Default" resolves to. Added a code example showing how to pin a specific version (e.g., 4.5) and prevent users from bypassing it to the "latest". * *Meaning:* Previous configuration methods might not have fully locked users to a specific version because they could select "Default". Now there's a documented way to enforce specific versions via env vars in the config. * **Page 4: `vs-code.md`** * *Change:* Modified the `allowDangerouslySkipPermissions` setting description. * *Old:* "Auto requires a Team plan and Claude Sonnet 4.6 or Opus 4.6..." * *New:* "Auto requires a Team, Enterprise, or API plan and Claude Sonnet 4.6 or Opus 4.6..." * *Meaning:* Again, consistent update regarding plan availability for the "Auto" mode. 3. **Synthesize and Structure Analysis:** * **Overall Summary:** The updates primarily focus on the broader availability of the "Auto" permission mode and clarifying how to enforce specific model versions in configurations. It removes "rolling out" status for Enterprise/API plans regarding Auto mode and adds critical details for model pinning. * **Key Themes:** * *Feature Availability:* "Auto" mode is now GA (Generally Available) for Enterprise and API plans. * *Model Management:* Clarified that `model` settings are initial defaults, not locks. Introduced use of `ANTHROPIC_DEFAULT_*` env vars for stricter version control. * **Impact Level:** * *Level:* Medium. * *Reasoning:* For most users, it's just availability changes. However, for admins managing configurations (model locking), the new `env` var info in `model-config.md` is a significant operational detail to ensure users stay on specific versions. * **Action Items:** * If you are on an Enterprise or API plan, you can now use Auto mode. * Admins: If you need to pin model versions (e.g., stick to 4.5 instead of auto-upgrading to 4.6), update your config to include the `ANTHROPIC_DEFAULT_*` environment variables. * Update internal docs if they previously listed Auto mode as "coming soon" for Enterprise. 4. **Drafting the Response (in Chinese):** * *Summary:* 本次文档更新主要涵盖了“自动模式”权限功能的全面可用性（现已面向企业版和 API 计划开放），以及模型配置控制的重要澄清（增加了通过环境变量锁定模型版本的方法）。 * *Themes:* * 功能可用性扩展：Auto 模式现已支持企业版和 API 计划，不再处于“即将推出”阶段。 * 配置控制增强：澄清了 `model` 配置仅作为初始选择，并引入了 `ANTHROPIC_DEFAULT_*` 环境变量以实现更严格的版本锁定。 * *Impact:* 中等。虽然大多数用户仅看到功能解锁，但对于需要严格控制模型版本的管理员来说，`model-config.md` 的更新提供了关键的配置缺失环节。 * *Action Items:* * 企业版/API 用户：现在可以启用并使用 Auto 模式。 * 配置管理员：若需防止用户自动升级到最新模型版本（如锁定在 4.5），请按新文档在配置文件中添加 `ANTHROPIC_DEFAULT_*` 环境变量。 * 检查内部文档：移除关于 Auto 模式仅限 Team 计划的过时描述。 5. **Review and Refine:** * The tone is professional and technical. * The formatting follows the requested Markdown structure. * The content accurately reflects the diffs (especially the nuance in `model-config.md` about the env vars). 6. **Final Output Generation** (matches the drafted content).

1. **Analyze the Request:** * **Role:** World-class programmer analyzing documentation changes. * **Input:** 6 markdown pages with diffs (chrome.md, cli-reference.md, desktop.md, devcontainer.md, sandboxing.md, settings.md). * **Output Format:** Markdown, concise, insightful. * **Language:** Chinese (as requested in the system prompt: "请用中文回复"). * **Structure:** 1. Overall Summary (1-2 sentences). 2. Key Themes. 3. Impact Level (Low/Medium/High/Breaking). 4. Action Items. 2. **Analyze the Diffs:** * **Page: `chrome.md`** * *Change:* Added a "See also" link to `[Computer use](/en/computer-use)`. * *Context:* Relates Chrome automation to native macOS computer use. * **Page: `cli-reference.md`** * *Change 1 (`--allow-dangerously-skip-permissions`):* Updated description. Clarifies that it adds `bypassPermissions` to the `Shift+Tab` mode cycle without starting in it. Allows starting in `plan` mode and switching later. * *Change 2 (`--dangerously-skip-permissions`):* Updated description. Clarifies it is equivalent to `--permission-mode bypassPermissions`. * *Context:* Refined documentation around permission bypassing modes. This implies a UI change where `Shift+Tab` cycles through modes. * **Page: `desktop.md`** * *Change:* Comparison table update. "Computer use" row changed for CLI column from "Not available" to "[Enable via `/mcp`](/en/computer-use) on macOS". * *Context:* New feature parity between Desktop and CLI for Computer Use on macOS, accessible via MCP (Model Context Protocol) or a specific command structure (though the link suggests a docs page). * **Page: `devcontainer.md`** * *Change 1:* Updated step 1 to explicitly name the extension: "[Dev Containers extension](https://...)". * *Change 2:* Updated step 4 command palette command from "Remote-Containers: Reopen in Container" to "Dev Containers: Reopen in Container". * *Context:* Microsoft renamed the extension. This is a maintenance update to reflect current VS Code extension names. * **Page: `sandboxing.md`** * *Change:* Updated the "Built-in file tools" / "Computer use" section. Added reference to "computer use in the CLI" (`/en/computer-use`) alongside Desktop. * *Context:* Consistency update acknowledging CLI support for Computer Use. * **Page: `settings.md`** * *Change:* Updated `defaultMode` description. Added list of valid values: `default`, `acceptEdits`, `plan`, `auto`, `dontAsk`, `bypassPermissions`. Note that CLI flag overrides this. * *Context:* Documentation of available permission modes is now explicit in the settings docs. 3. **Synthesize Insights (Mental Draft):** * *Summary:* The main focus is bringing Computer Use capabilities to the CLI (specifically macOS) and clarifying the permission mode system. There are also minor housekeeping updates for VS Code extension names. * *Themes:* 1. **Computer Use on CLI:** Previously Desktop-only (according to the table), now available on CLI via `/mcp` or similar. Links added to `/en/computer-use` in multiple places. 2. **Permission Mode Refinement:** Clarifying how `bypassPermissions` works, specifically how `Shift+Tab` cycles modes and how CLI flags interact with settings. 3. **Dependency Updates:** VS Code extension name change ("Remote-Containers" -> "Dev Containers"). 4. **Drafting the Content (in Chinese):** * *Overall Summary:* 本次更新主要聚焦于为 CLI 带来 macOS 的“Computer Use”能力，并显著改进了权限模式的文档说明，使其关于模式切换和覆盖机制更加清晰。同时更新了 VS Code Dev Containers 扩展的相关引用。 * *Key Themes:* * **Computer Use 跨平台支持：** 明确 CLI 现已支持 macOS 的“Computer Use”功能（通过 MCP），此前该功能主要限于 Desktop 版本。文档多处增加了 `/en/computer-use` 的链接。 * **权限模式细粒度控制：** 澄清了 `--allow-dangerously-skip-permissions` 的行为（将其加入 `Shift+Tab` 切换循环而非直接启动），并明确了 `settings.md` 中 `defaultMode` 的所有有效值。 * **依赖项名称更新：** 反映了 VS Code 扩展市场的变化，将 "Remote-Containers" 更新为 "Dev Containers"。 * *Impact Level:* **Medium**。 * *Reasoning:* 新增了 CLI 的 macOS 控制能力是一个重要的功能扩展。权限模式的澄清虽然不是代码破坏性变更，但对安全配置理解至关重要。 * *Action Items:* * 查看 `/en/computer-use` 文档，了解如何在 CLI 中配置和使用 macOS 应用控制。 * 检查 `defaultMode` 设置，确保配置了期望的默认权限行为。 * 如果使用 VS Code Dev Containers，更新命令面板指令引用（从 "Remote-Containers" 改为 "Dev Containers"）。 * 调整脚本文档中的权限跳过标志使用说明，以反映新的模式切换逻辑。 5. **Refining the Output:** * Make it punchy. * Ensure markdown format is clean. * Translate technical terms appropriately (keeping "Computer Use", "CLI", "MCP" where standard). *(Self-Correction during drafting)*: Wait, the desktop diff shows "Enable via `/mcp`". This is interesting. It implies the CLI version uses MCP (Model Context Protocol) to achieve computer use. I should mention that. *Action Items refinement:* 1. Explore `/en/computer-use`. 2. Update `settings.json` knowledge regarding `defaultMode`. 3. Update internal docs if they reference the old VS Code extension name. 4. Review permission bypass logic in scripts. 6. **Final Polish (Chinese):** * **Summary:** 本次文档更新标志着 CLI 版本现已支持 macOS 的“Computer Use”功能，并大幅澄清了权限模式（特别是 `bypassPermissions`）的交互与切换机制，同时修正了 VS Code 扩展的最新名称。 * **Themes:** Computer Use 功能扩展至 CLI; 权限系统文档精细化; 第三方依赖名称同步. * **Impact:** Medium. * **Actions:** Review new computer use capabilities; Check settings; Update VS Code references. 7. **Final Output Generation** (Matches the provided response structure).