Changes on 2026-05-06

1. **Analyze the Request:** * **Role:** World-class programmer analyzing documentation changes. * **Input:** Diff for `settings.md` (1 page, +1/-1 lines). * **Task:** Concise, insightful analysis in markdown format. Focus on developer relevance. * **Language:** Chinese (as requested: "请用中文回复"). * **Output Structure:** 1. Overall Summary. 2. Key Themes. 3. Impact Level. 4. Action Items. 2. **Analyze the Diff:** * **File:** `settings.md`. * **Change:** Update to the description of the `autoUpdatesChannel` setting. * **Original Description:** "Use `"stable"`... or `"latest"` (default) for the most recent release." * **New Description:** "...most recent release. To disable auto-updates entirely, set [`DISABLE_AUTOUPDATER`](/en/setup#disable-auto-updates) in `env`." * **Context:** The setting `autoUpdatesChannel` allows choosing between stable and latest. The change clarifies that *this specific setting* is for channel selection, and to *completely disable* updates, one should use an environment variable `DISABLE_AUTOUPDATER`. It doesn't change the default value example (`"stable"`), just adds a helpful note on how to disable updates entirely (which isn't an option via the channel setting itself). 3. **Drafting the Analysis (Internal Monologue/Drafting in English -> Chinese):** * *Overall Summary:* The documentation for `autoUpdatesChannel` in settings.md was updated to clarify how to completely disable auto-updates. It now explicitly points users to the `DISABLE_AUTOUPDATER` environment variable. * *Chinese:* 对 `settings.md` 中 `autoUpdatesChannel` 配置项的描述进行了更新，阐明了如何完全禁用自动更新。文档现在明确指引开发者使用 `DISABLE_AUTOUPDATER` 环境变量来实现此目的。 * *Key Themes:* * Clarification on update control mechanisms. * Separation of concerns (channel vs. enable/disable). * Reference to environment variables. * *Chinese:* * 配置选项与环境变量的协同工作。 * 明确区分“更新渠道选择”与“完全禁用更新”的机制。 * 文档指引的清晰度提升。 * *Impact Level:* * Is it breaking? No. Code didn't change. Default didn't change. * Is it High? No, it's a doc update. * Is it Medium? It resolves potential confusion for developers who want to turn updates off completely and might be looking for a specific value in `autoUpdatesChannel` that doesn't exist. * *Decision:* Low. It's purely documentation clarification. * *Reasoning:* No functional change to the software, purely improves discoverability of existing features. * *Chinese:* Low（低）。这仅是文档说明的优化，未涉及任何代码逻辑或默认行为的变更。 * *Action Items:* * None strictly required. * Good to know: How to disable updates if you have strict version control. * *Chinese:* * 无需更改现有代码或配置。 * 如果之前在寻找如何通过设置文件禁用更新，请转而使用 `DISABLE_AUTOUPDATER` 环境变量。 * 审查更新策略（如需严格锁定版本）。 4. **Refining the Output (formatting and tone):** * *Structure Check:* 1. Summary: Short and punchy. 2. Themes: Bullet points. 3. Impact: Level + Reasoning. 4. Action items: Practical steps. 5. **Final Polish (Chinese):** * *Summary:* 更新了 `settings.md` 中关于 `autoUpdatesChannel` 的文档，新增了如何完全禁用自动更新的指引。 * *Themes:* * 文档易读性 * 环境变量配置 * *Impact:* Low。仅改进了文档描述，未改变软件行为。 * *Action Items:* 检查 `DISABLE_AUTOUPDATER` 设置。 Let's make it sound like a "world-class programmer". Professional, precise. * *Revised Summary:* 对 `autoUpdatesChannel` 的文档描述进行了微调，补充了关于如何完全禁用自动更新的关键指引。 * *Revised Themes:* * 配置项与环境的解耦。 * 针对特定需求（如禁用更新）的操作指引明确化。 * *Revised Impact:* **Low**。纯粹是文档层面的改进，帮助开发者快速找到禁用更新功能的正确方法，不影响现有系统行为。 * *Revised Action Items:* * 如果您希望完全禁用自动更新，请在环境变量中设置 `DISABLE_AUTOUPDATER`，而不是在 `autoUpdatesChannel` 中寻找选项。 * 无需修改现有的 settings 配置文件。 6. **Final Output Generation** (matches the structure requested).

1. **Analyze the Request:** * **Role:** World-class programmer/analyst. * **Task:** Analyze documentation changes (Changelog) as a single batch. * **Input:** A diff for `CHANGELOG.md.md` (specifically version 2.1.132). * **Output Format:** Markdown. * **Language:** Chinese (requested at the end of the prompt). * **Structure:** 1. Overall Summary, 2. Key Themes, 3. Impact Level, 4. Action Items. 2. **Analyze the Input Data (Version 2.1.132):** * *Added Features:* * `CLAUDE_CODE_SESSION_ID` env var for Bash tool. * `CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1` to opt out of fullscreen renderer. * "Pasting…" hint for Ctrl+V images. * *Fixes (Significant quantity & variety):* * **Reliability/Stability:** Fixed SIGINT handling (graceful shutdown), fixed uncaught exception on terminal close/SSH disconnect. * **Resume/Session Handling:** Fixed `--resume` failing with emoji truncation errors (Unicode/surrogates), fixed `--permission-mode` ignored on resume. * **Terminal/Render/UX:** Fixed fullscreen blanking after sleep/ctrl+Z, fixed cursor placement with complex Unicode (Indic/ZWJ), fixed vim operators with NFD accents, fixed scrolling in various IDEs (Cursor, VS Code, JetBrains), fixed mouse wheel speed. * **Clipboard/Paste:** Fixed pasting text starting with `/`, fixed stray escape sequences during paste. * **Commands:** Fixed `/usage` Ctrl+S hang on Linux, `/terminal-setup` error on Windows, `/effort` picker not reflecting env var, `/status` showing wrong model, autocomplete popup height, statusline token counts, Alt+T on macOS. * **Platform Specific:** Fixed dead input on Windows after re-opening background session, fixed unbounded memory growth from MCP servers. * **MCP (Model Context Protocol):** Fixed servers failing `tools/list` (retry logic), fixed auth status display, fixed retry logic for headless mode. * **Cloud/Provider:** Fixed Bedrock/Vertex 400 errors with prompt caching. * *Improvements:* Visual consistency in dialogs, updated TUI banner text. 3. **Synthesize the Analysis (Drafting in English first, then translating/refining to Chinese):** * *Overall Summary:* This release is a massive "bugfix and polish" update. It focuses heavily on stability, terminal/UI edge cases (especially Unicode and IDE integration), and fixing session management/resume logic. * *Key Themes:* * **Terminal UX & IDE Integration:** Lots of fixes for how the tool behaves inside VS Code, JetBrains, Cursor, and Windows Terminal. Scrolling, pasting, and rendering. * **Unicode/Text Handling:** Specific fixes for emojis, Indic conjuncts, NFD accents, and cursor positioning. This suggests complex text handling was a pain point. * **Stability & Reliability:** Handling SIGINT, SSH disconnects, memory leaks (MCP), and crash recovery (graceful shutdown). * **MCP & Environment Variables:** Better MCP error handling/auth display and new env vars for session ID and rendering control. * *Impact Level:* **High**. It's not a breaking change (API break), but it fixes critical usability issues (dead input, crashes, memory leaks) and annoying UX bugs (scrolling, pasting). It significantly improves the day-to-day developer experience. * *Action Items:* * Update the CLI. * Check if the `CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN` is needed if users dislike fullscreen mode. * Verify MCP server error reporting for better debugging. 4. **Refining and Translating to Chinese (Target Language):** * *Overall Summary:* 2.1.132 版本是一次重大的稳定性与用户体验更新。主要修复了大量终端交互、IDE 兼容性、会话恢复及 Unicode 处理方面的边缘情况 Bug，并新增了环境变量控制功能。 * *Key Themes:* * **终端与 IDE 交互体验:** 修复了在 Cursor, VS Code, JetBrains 等 IDE 中的滚动、粘贴、渲染及全屏模式问题。 * **文本与 Unicode 处理:** 解决了包含表情符号、Indic 复合字符或重音符号时的光标定位、Vim 操作及字符串截断问题。 * **稳定性与资源管理:** 修复了强制中断时的异常退出、SSH 断开时的崩溃、以及 MCP 服务器的内存泄漏问题。 * **MCP 与配置:** 增强了 MCP 连接的错误提示与重试逻辑，修复了环境变量覆盖及权限模式在会话恢复时的逻辑。 * *Impact Level:* **High** (高). 虽然没有破坏性变更，但修复了导致死锁（死输入）、内存溢出及强制退出崩溃的关键 Bug，显著提升了工具的鲁棒性和日常使用体验。 * *Action Items:* * **立即更新:** 推荐所有开发者更新以解决潜在的内存泄漏和崩溃问题。 * **检查渲染偏好:** 如果不喜欢全屏模式，可尝试设置 `CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1`。 * **验证 MCP 连接:** 关注更新后 MCP 服务器的连接状态提示，排查之前的静默失败问题。 5. **Final Review against Constraints:** * Single batch analysis? Yes. * Markdown format? Yes. * Concise? Yes. * Chinese language? Yes. * Focus on developers? Yes. 6. **Final Output Generation.** (Proceeding to generate the response).

1. **Analyze the Request:** * **Role:** World-class programmer analyzing documentation changes. * **Output:** Concise, insightful analysis in markdown format. * **Language:** Chinese. * **Input:** 12 pages of documentation diffs for a tool (Claude Code). * **Structure:** Overall Summary, Key Themes, Impact Level, Action Items. 2. **Analyze the Diffs (Page by Page):** * **`cli-reference.md`**: * Added `--plugin-url`: Fetch plugin zip from URL for this session. * Updated `--settings`: Clarified that it accepts an inline JSON string and overrides behavior (merge logic). * **`headless.md`**: * Updated table row: Added `--plugin-url` alongside `--plugin-dir`. * **`interactive-mode.md`**: * Updated Ctrl+R (reverse search): Changed default scope to "all projects". Press Ctrl+S to cycle scopes (session/project/all). * **`llm-gateway.md`**: * Updated Gateway Model Discovery: Now requires an environment variable `CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY=1` to enable. Previously seemed automatic or the text implied it queries automatically. Now explicitly "off by default" for security/privacy reasons (shared keys). Requires v2.1.129. * **`model-config.md`**: * Updated `ANTHROPIC_CUSTOM_MODEL_OPTION` text: Added note about the discovery flag `CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY=1`. * **`monitoring-usage.md`**: * Updated "Pull request counter": Now increments for merge requests created via shell command or MCP tool, not just direct creation. * **`plugins.md`**: * Added section on `--plugin-url`: Allows testing hosted plugins (e.g., CI artifacts) without downloading locally. * **`plugins-reference.md`**: * **Breaking/Structural Change**: `monitors` moved to root -> `experimental.monitors`. * **Breaking/Structural Change**: `themes` moved to root -> `experimental.themes`. * Updated table to reflect these structural changes. * Clarified `experimental` namespace. * **`settings.md`**: * Added `skillOverrides`: New setting to control skill visibility via settings files (`on`, `name-only`, `user-invocable-only`, `off`). * Updated `--settings` description: Clarified merge logic with file-based settings (overrides keys, keeps others). * Note: Requires v2.1.129. * **`setup.md`**: * Updated auto-update section: Homebrew and WinGet can now opt into auto-updates via `CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE=1`. Linux (apt/dnf/apk) still manual. * WinGet update might fail due to file locking if Claude is running. * **`skills.md`** & **`slash-commands.md`** (Identical changes in both): * Added section "Override skill visibility from settings": Using `skillOverrides`. * Updated "Context budget" section: Mentioned using `skillOverrides` to save token budget by setting skills to `"name-only"`. 3. **Synthesize and Group Changes:** * **Plugin Enhancements:** `--plugin-url` support. * **Plugin Structure Changes:** `themes` and `monitors` moved to `experimental.*` namespace in `plugin.json`. *This is likely a breaking change for plugin developers.* * **Settings & Config:** Clarification on `--settings` merge behavior. New `skillOverrides` feature. * **Gateway/Model Discovery:** Discovery is now opt-in via Env Var (`CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY=1`). * **UX Improvements:** Ctrl+R search defaults to all projects. Homebrew/WinGet auto-updates opt-in. * **Monitoring:** Broader definition of PR counting. 4. **Drafting the Analysis (Iterative refinement):** * *Summary:* This update focuses on plugin capabilities (remote loading, structural updates), refined configuration management (settings merging, skill overrides), and gateway model discovery security (opt-in only). * *Themes:* 1. **Plugin Architecture Evolution**: Remote loading (`--plugin-url`) and structural refactoring (`experimental` namespace). 2. **Configuration Precision**: Better control over settings merging and skill visibility without editing source files. 3. **Security & Privacy**: Gateway model discovery is now disabled by default to prevent info leakage in shared-key environments. 4. **Developer Experience (DX)**: Improved search defaults and package manager auto-update options. * *Impact:* * *Breaking/Medium*: The `plugin.json` changes (`themes` -> `experimental.themes`, `monitors` -> `experimental.monitors`) will break existing plugins using these features until updated. * *Medium*: Gateway discovery change affects LLM gateway users. * *Low*: Others are additive/enhancements. * *Action Items:* 1. Update `plugin.json` if you use themes or monitors. 2. Set Env Var if you rely on automatic gateway model discovery. 3. Review `skillOverrides` for better context management. 4. Consider `CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE` for smoother updates. 5. **Translating to Chinese (World-class programmer tone):** * *Summary:* 本次更新主要集中在插件能力的扩展（远程加载与结构调整）、配置管理的精细化（合并逻辑与技能覆盖），以及网关模型发现的安全加固（默认关闭）。 * *Themes:* 插件架构升级, 配置控制增强, 安全与隐私, 开发者体验优化. * *Impact:* **中/高** (Medium/High). 主要原因在于 `plugin.json` 的结构性破坏性变更。 * *Action Items:* 修复 `plugin.json`, 启用网关发现, 使用 `skillOverrides`, 设置包管理器自动更新. 6. **Final Polish (Markdown formatting):** Ensure it looks professional and "world-class". * *Refining the impact:* The plugin change is breaking. The gateway change is a behavior change (off by default). The rest is additive. So overall "Medium to High" or "High for plugin authors, Medium for users". Let's go with "Medium" but highlight the breaking change in reasoning. * *Refining Action Items:* Make them actionable verbs. 7. **Final Output Generation** (matching the drafted sections).

1. **分析请求：** * **角色：** 世界级程序员，文档变更方面的专家。 * **任务：** 分析一批文档变更（变更日志更新）。 * **格式：** Markdown，简洁，富有洞察力，用中文。 * **输入：** `CHANGELOG.md.md` 中的 1 个文件变更。 * **内容：** 版本 2.1.131 增加了两个错误修复：Windows 上的 VS Code 扩展激活问题和 Mantle 端点认证问题。 2. **分析差异：** * **文件：** `CHANGELOG.md.md`（注意：文件名有点奇怪，通常只是 `CHANGELOG.md`，但我会将其视为变更日志）。 * **添加：** 版本 `2.1.131`。 * **Bug 修复 1：** VS Code 扩展无法在 Windows 上激活。原因：bundled SDK（捆绑 SDK）中的硬编码构建路径（`createRequire` polyfill bug）。 * **Bug 修复 2：** Mantle 端点认证失败。原因：缺少 `x-api-key` header。 3. **起草分析（迭代过程）：** * **整体摘要：** * *草稿：* 新版本 2.1.131 修复了 Windows 上 VS Code 扩展崩溃和 Mantle 认证失败的问题。 * *润色（中文）：* 发布了 2.1.131 版本，主要修复了 Windows 平台上 VS Code 扩展无法激活的问题以及 Mantle 端点的认证失败问题。 * **关键主题：** * 跨平台兼容性。 * 认证/安全性。 * 开发者体验（IDE 集成）。 * **影响级别：** * *推理：* 这破坏了 Windows 上的扩展激活（对 Windows 用户来说影响大），并且破坏了 Mantle 的认证（对 Mantle 用户来说影响大）。然而，这些都是 bug 修复，而非破坏性更改。 * *级别：* 中等到高（如果受影响）。对于普通受众，让我们坚持“中等”，对于受影响的用户则是“高”。提示要求给出一个级别。“中/高”很合适，因为平台破坏会阻塞工作流。我们就定为 **中等**，因为它解决了特定的阻塞问题而没有引入重大变更。实际上，如果 VS Code 扩展无法启动，那就是阻塞。我会根据语境将其评为 **高**，或者 **中等**。让我们坚持“中等”，因为对 Mac/Linux 用户没有影响，对非 Mantle 用户也没有影响。等等，Windows 在开发中很普遍。让我们定为 **中等**。*自我修正：* 实际上，如果它对你有影响，那就是高影响。但对于版本发布来说，“Bug 修复”通常意味着积极影响。让我们将其归类为 **中等**，因为它解决了特定的故障。 * **开发者的行动项：** * 更新到 2.1.131。 * 如果使用 Windows，请重启/重新安装扩展。 * 如果使用 Mantle，请验证标头是否已发送/检查配置（虽然这可能是一个客户端 SDK 修复，所以他们只需要更新）。 * 查看构建路径是否有类似的自定义实现。 4. **最终润色（中文）：** * *摘要：* 发布版本 2.1.131，主要针对 Windows 平台 VS Code 扩展激活失败和 Mantle 端点认证缺失 API Key 的问题进行了修复。 * *主题：* * **跨平台兼容性修复**：解决了 Windows 特定的路径解析问题。 * **认证机制完善**：修正了 HTTP 请求头中缺少认证信息的问题。 * *影响级别：* **中等**。虽然不是破坏性更新，但 Windows 用户的 IDE 扩展完全无法激活属于阻塞性问题，Mantle 认证失败也直接影响功能可用性。 * *行动项：* * 立即升级至 2.1.131 版本。 * Windows 用户需确认 VS Code 扩展能否正常激活。 * Mantle 使用者需验证 API 调用是否恢复正常。 5. **输出生成：** 将思路转化为所需的 Markdown 结构。 * *摘要：* 版本 2.1.131 修复了两个关键 bug：Windows 上 VS Code 扩展激活失败（由于 `createRequire` polyfill 的路径问题）和 Mantle 端点认证缺失 `x-api-key` 头的问题。 * *主题：* * 平台兼容性（Windows SDK 捆绑问题）。 * API 认证（标头注入）。 * *影响：* **中等**。这些是阻塞性问题的修复。Windows 开发者之前可能完全无法使用该扩展，Mantle 用户则面临认证失败。 * *行动：* * 更新到 2.1.131。 * Windows 用户重启 IDE 以确保扩展加载。 * Mantle 用户测试端点连接。 让我们用中文很好地组织最终回复。 * *摘要：* 发布 2.1.131 版本，重点修复了 Windows 平台 VS Code 扩展无法激活的阻塞性问题，以及 Mantle 端点认证失败的问题。 * *主题：* * 平台兼容性修复 * API 认证修复 * *影响：* **中等**。修复了特定场景下的阻断性 Bug（Windows 扩展启动、Mantle 认证），显著改善受影响用户的开发体验。 * *行动项：* * 升级至 2.1.131 版本。 * Windows 用户验证 VS Code 扩展是否恢复正常加载。 * Mantle 用户检查 API 连接是否稳定。 * 如有类似 SDK bundling 实现，检查是否存在硬编码路径风险。 这看起来很可靠。准备生成输出。