Changes on 2026-06-01

用户希望对提供的文档变更进行分析。 总共有 4 个页面： 1. `mcp.md`：增加了一个指向快速入门指南的链接，并稍微澄清了上下文窗口的使用情况。 2. `overview.md`：增加了一个指向 MCP 快速入门指南的链接。 3. `plugins-reference.md`：从 LSP 配置的可选字段表中移除了 `shutdownTimeout` 和 `restartOnCrash`。 4. `CHANGELOG.md.md`：增加了版本 `2.1.160`，其中包含安全提示、Bug 修复（Windows、后台会话、性能）、功能移除和重命名（"workflow" -> "ultracode"）。 我的任务是总结变更，识别关键主题，评估影响，并列出给开发者的可执行项目，全部以 Markdown 格式并用中文回复。 **1. Overall Summary (1-2 sentences):** 本次更新主要集中在增强安全性（防止写入敏感配置文件）、修复 Windows 和后台会话的 Bug、优化性能，以及调整 MCP 和相关功能的文档说明。此外，关键词 "workflow" 被重命名为 "ultracode"。 **2. Key Themes:** * **安全性增强**：增加写入 shell 启动文件和构建工具配置文件的提示。 * **MCP 文档引导**：在多处增加了指向 "MCP quickstart" 的链接，帮助新手入门。 * **稳定性与修复**：大量修复了 Windows 平台、后台会话、剪贴板操作以及 UI 交互的问题。 * **配置变更**：废弃了 `shutdownTimeout` 和 `restartOnCrash` 插件配置项，移除了特定的环境变量支持，并将动态工作流触发关键词从 `workflow` 改为 `ultracode`。 **3. Impact Level:** **Medium (中等)** * **Reasoning:** 大量 Bug 修复显著提升了用户体验，特别是 Windows 用户和重度用户。安全提示防止了潜在的意外执行。关键词变更 `workflow` -> `ultracode` 是破坏性变更（虽然提示说用自然语言请求也可以，但关键词不再有效），可能影响用户习惯。移除环境变量和插件配置选项也属于小幅破坏性变更。 **4. Action items for developers:** * **更新触发词**：如果您习惯使用关键词 `workflow` 来触发动态工作流，请改用 `ultracode`。 * **清理配置**：检查是否使用了已废弃的环境变量 `CLAUDE_CODE_OPUS_4_6_FAST_MODE_OVERRIDE`，移除它（已无作用）。 * **移除无效字段**：检查 LSP 插件配置，移除不再支持的 `shutdownTimeout` 和 `restartOnCrash` 字段。 * **关注安全性**：注意在安装或配置时，系统将增加对写入 `.zshenv`、`~/.config/git/` 等敏感位置的确认提示。 * **阅读新指南**：如果是初次使用 MCP，请查阅新增的 [MCP quickstart](/en/mcp-quickstart) 指南。

1. **Analyze the Request:** * **Role:** World-class programmer/developer tools expert. * **Task:** Analyze documentation changes for 4 pages as a single batch. * **Format:** Markdown, concise, insightful, Chinese language. * **Structure:** 1. Overall Summary, 2. Key Themes, 3. Impact Level, 4. Action Items. 2. **Analyze the Changes (Page by Page):** * **Page 1: `cli-reference.md`** * *Change:* Added `claude daemon stop --any` command. * *Detail:* Stops the supervisor and sessions. `--any` flag confirms stopping an on-demand supervisor (default). `--keep-workers` keeps sessions running for reconnection. * *Reasoning:* It's a new CLI tool to help developers manage stuck/unresponsive background services. It adds fine-grained control over the daemon lifecycle. * **Page 2: `hooks.md`** * *Change:* Updated Tip link text from "Automate workflows with hooks" to "Automate actions with hooks". * *Detail:* Just a title consistency update. * **Page 3: `hooks-guide.md`** * *Change:* Updated title from "Automate workflows with hooks" to "Automate actions with hooks". * *Detail:* Consistency update with Page 2. * **Page 4: `plugins.md`** * *Change 1:* Updated table row for "Plugins". Description changed to "self-contained directories with skills, agents, hooks, or a `.claude-plugin/plugin.json` manifest". * *Change 2:* Updated Step 1 text to say "optionally alongside a `.claude-plugin/plugin.json` manifest". * *Reasoning:* Clarifies that a `plugin.json` manifest is not strictly mandatory for a directory to function as a plugin context (or at least, the definition of a plugin is being broadened/clarified to include directories containing these components even without the manifest, or simply emphasizing the structure over just the manifest). This suggests a more flexible definition of what constitutes a "plugin" structure. 3. **Synthesize Analysis:** * **Overall Summary:** The update introduces a new CLI command for better daemon management and refines terminology/definitions regarding hooks and plugins to clarify flexibility. * **Key Themes:** * *Operational Control:* New command to handle unresponsive background supervisors. * *Terminology Consistency:* Renaming "workflows" to "actions" in hooks context. * *Plugin Structure Flexibility:* Clarifying that plugin directories focus on containing components (skills/agents/hooks), with manifest files being optional or secondary in description. * **Impact Level:** Low. These are refinements and additions that improve usability but don't break existing code. The `--any` flag is an addition, not a change in default behavior that breaks things (it confirms the default). * **Action Items:** * Use the new `claude daemon stop --any` if encountering unresponsive supervisors. * Be aware of the terminology shift ("actions" vs "workflows") when searching docs. * Note the updated plugin structure definition (manifest optional). 4. **Draft the Response (in Chinese):** * *Summary:* 本次更新引入了新的 CLI 命令以增强对后台服务的控制能力，并优化了关于 Hooks 和 Plugins 的术语及结构定义。 * *Themes:* * **运维与调试能力**：新增 `claude daemon stop --any` 命令，专门用于处理无响应的后台监控进程。 * **术语统一**：将 Hooks 相关文档中的 "workflows"（工作流）重命名为 "actions"（动作），以更准确地反映功能。 * **插件定义的灵活性**：更新了插件目录结构的描述，明确指出 `.claude-plugin/plugin.json` 清单文件是可选的，强调组件（Skills/Agents/Hooks）本身的重要性。 * *Impact:* **Low**。主要是功能性增强和文档澄清，不涉及破坏性变更。 * *Action Items:* * 在遇到后台服务无响应时，使用 `claude daemon stop --any` 进行恢复。 * 了解 Plugin 目录结构中 Manifest 文件的可选性。 * 注意文档中关于 "Automate actions" 的措辞更新。 5. **Refine Response:** Make it sound "world-class" and "insightful". Instead of just "Low impact", explain *why*. The terminology change implies a shift in mental model (from big workflows to discrete actions). *Revised Action Items:* * 尝试使用 `claude daemon stop --any` 来解决 "Background service did not respond" 错误。 * 更新插件开发心智模型：不再强制要求 `plugin.json`，目录结构本身即可承载能力。 6. **Final Polish (Markdown formatting):** Ensure the structure matches the prompt exactly. * *Summary:* 本次文档更新主要增强了后台进程管理能力，并澄清了 Hooks 和 Plugins 的结构与术语定义。 * *Themes:* 运维稳定性, 术语精确性, 架构灵活性. * *Impact:* Low. * *Action Items:* (As drafted above). *Self-Correction during drafting:* The change in `plugins.md` specifically says "self-contained directories with skills... or a `.claude-plugin/plugin.json` manifest" and "optionally alongside". This implies the `plugin.json` is *not* strictly required for the directory to function as a plugin container, which is a significant architectural clarification for plugin developers. 7. **Final Output Generation.** (Proceeding to generate Chinese response).

1. **Analyze the Request:** * **Role:** World-class programmer with expertise in dev tools/docs. * **Task:** Analyze 7 documentation changes (diffs provided) as a single batch. * **Output Format:** Markdown. * **Language:** Chinese. * **Content Requirements:** Overall Summary, Key Themes, Impact Level (with reasoning), Action Items (max 5). 2. **Analyze the Diffs (Page by Page):** * **Page 1: `desktop.md`** * *Change:* Updated note about MCP (Model Context Protocol) servers. * *Old:* Desktop app `claude_desktop_config.json` is separate from CLI/Code tab. To use in Code tab, configure in `.mcp.json`. * *New:* Desktop app *now loads* `claude_desktop_config.json` servers into the Code tab alongside local configs. CLI standalone *does not* read it, but has an import command (`claude mcp add-from-claude-desktop`). * *Impact:* Better integration between Desktop App and Code tab. Less manual config duplication for Desktop users. * **Page 2: `discover-plugins.md`** * *Change:* Added info about token costs when reloading plugins. * *New:* Reloading plugins invalidates prompt cache, increasing cost on the next request because new components announce themselves. If plugins provide MCP servers and tools aren't deferred, the cache is invalidated. * *Impact:* Performance/Cost warning. Developers need to be aware that hot-reloading isn't "free" in terms of tokens. * **Page 3: `hooks.md`** * *Change:* Updated `MessageDisplay` hook behavior and timeout defaults. * *New:* `MessageDisplay` default timeout is 10 seconds. Added examples for stripping markdown. Clarified that it holds rendering until the hook returns (keep it fast). Updated the general table: `UserPromptSubmit` defaults to 30s, `MessageDisplay` defaults to 10s for command/http/mcp_tool types. * *Impact:* Refinement of hook API. Crucial to know the new 10s timeout for UI display hooks to avoid failures. * **Page 4: `hooks-guide.md`** * *Change:* Updated timeout table for hooks. * *New:* Consistent with Page 3: `MessageDisplay` lowers timeouts to 10s. * *Impact:* Consistency check. * **Page 5: `model-config.md`** * *Change:* Clarified 1M context window suffix `[1m]`. * *New:* Applies to `opus` and `sonnet` aliases. *Crucially*, it does *not* extend the plan-mode Opus phase of `opusplan` (remains 200K). * *Impact:* Corrects a potential misunderstanding about context limits in planning mode. * **Page 6: `structured-outputs.md`** * *Change:* Availability updates for models on Amazon Bedrock. * *New:* Removed "Claude Opus 4.8" from the "Generally Available" list for Bedrock? Wait, let me check the diff closely. * *Diff:* Old: "generally available for Claude Opus 4.8, Claude Opus 4.6..." -> New: "generally available for Claude Opus 4.6..." (4.8 removed). Note says 4.8 is available via "Claude in Amazon Bedrock" (the Messages-API Bedrock endpoint). * *Impact:* Availability/Platform specific change. Likely minor unless you are specifically using Opus 4.8 on standard Bedrock. * **Page 7: `programmatic-tool-calling.md`** * *Change:* Performance data, behavior clarification of `allowed_callers`, and error updates. * *New:* Added specific performance benchmarks (11% improvement, 24% fewer tokens in benchmarks; 38% reduction in 75-tool benchmark). Clarified `allowed_callers` is not a hard security block (guidance only). Updated error codes (`tool_not_allowed` -> `invalid_request_error`). Added "Less ideal use cases". * *Impact:* Significant clarity on performance trade-offs and security expectations. 3. **Synthesize the Themes:** * *Performance & Cost:* Focus on token usage (plugin reloading, programmatic tool calling stats). * *Integration & Configuration:* MCP servers now auto-sync from Desktop to Code tab; Context window limits clarified. * *API Refinements:* Hook timeouts reduced for UI updates; Security guidance on `allowed_callers` softened (it's guidance, not a firewall). 4. **Drafting the Summary (in Chinese):** * *Summary:* 此次更新重点增强了桌面应用与 CLI 之间的配置集成，优化了 Hooks 和插件系统的性能细节，并提供了关于“程序化工具调用”的更详尽的性能数据与安全边界说明。 * *Themes:* * **MCP 集成增强**: 桌面端配置现自动加载至 Code tab，减少重复配置。 * **性能与成本控制**: 明确了插件重载的 Token 成本，以及程序化工具调用的实际节省数据。 * **API 行为微调**: 调整了 `MessageDisplay` hook 的超时限制，并澄清了 `allowed_callers` 的安全属性。 5. **Assessing Impact Level:** * Is it "Breaking"? No, mostly clarifications and additions. * Is it "High"? The timeout change in hooks (`MessageDisplay` defaults to 10s) could break existing hooks that took 11-20s. The MCP change is a feature addition/enhancement. The `allowed_callers` change is a security concept clarification. * Let's go with **Medium**. The hook timeout change is the most likely to affect existing runtime behavior, and the MCP integration changes workflow. The programmatic calling updates are informational but important for architecture decisions. 6. **Formulating Action Items:** * Check MCP config: You might be able to clean up duplicate configs now, or use the import command. * Check Hooks: If you use `MessageDisplay`, verify it runs under 10s or explicitly set `timeout`. * Tool Calling Security: Don't rely solely on `allowed_callers` for security; add client-side checks. * Context Windows: Note that `opusplan` doesn't get the full 1M context upgrade via suffix. 7. **Refining the Output (translating and polishing):** * *Summary:* 本次更新主要集中在提升配置管理的一致性、优化 Hooks 机制的响应速度，以及澄清关键 API（如程序化工具调用）的性能表现与安全边界。 * *Themes:* * **配置一体化**: 桌面端 MCP 服务器配置现自动同步至 Code 标签页。 * **性能与资源消耗**: 明确了插件重载的 Token 成本，并提供了程序化工具调用的具体收益数据。 * **API 行为澄清**: 缩短了显示类 Hook 的默认超时时间，并修正了模型上下文窗口的覆盖范围。 * *Impact:* **Medium**. * Reasoning: `MessageDisplay` hook 默认超时从 600s 降至 10s，可能导致现有的耗时 Hook 失败。MCP 配置逻辑的改变虽是增强，但也需要开发者了解新的同步行为。 * *Action Items:* * **审查 Hook 超时**: 检查现有 `MessageDisplay` hook 的执行时间，如超过 10 秒需显式设置 `timeout` 字段。 * **清理 MCP 配置**: 利用桌面端配置自动同步至 Code tab 的新特性，移除 `.mcp.json` 中可能存在的重复服务器定义。 * **注意安全边界**: 使用程序化工具调用时，切勿将 `allowed_callers` 视为唯一的鉴权手段，应在客户端代码中添加必要的权限校验。 * **理解插件成本**: 在开发调试中避免频繁重载提供 MCP 服务器的插件，以防 Token 计费异常升高。 * **核对模型限制**: 若使用 `[1m]` 后缀开启长上下文，请注意 `opusplan` 的规划阶段仍限制在 200K。 8. **Final Review:** Does this match the "world-class programmer" persona? Yes, concise, technical, and actionable.