Changes on 2026-05-12

Let me analyze the two documentation changes: 1. **claude-code-on-the-web.md**: Added a clarification that Auto-fix is a per-PR toggle, and explained how to stop monitoring (via CI status bar toggle or telling Claude to stop watching). This is a UX clarification. 2. **model-config.md**: Added an important clarification that Sonnet with 1M context is NOT automatically upgraded like Opus — it requires "extra usage" on every subscription plan including Max. This is a significant cost/configuration clarification.

1. **Analyze the Request:** * **Role:** World-class programmer, expert in developer tools/docs. * **Task:** Analyze 4 specific documentation changes as a single batch. * **Output Format:** Markdown, concise, insightful, Chinese. * **Structure:** 1. Overall Summary, 2. Key Themes, 3. Impact Level, 4. Action Items. 2. **Analyze the Changes (Page by Page):** * **Page 1: `claude-code-on-the-web.md` (+6 / -5)** * *Topic:* Cloud sessions and GitHub authentication/access. * *Key Change 1:* The table row for "GitHub App" changed "Install... on specific repositories" to "Authorize... during web onboarding". It added a specific use case: "teams that want Auto-fix". * *Key Change 2:* A significant `<Note>` block was added. It clarifies that a cloud session can access *any* repo the GitHub account can see, not just those with the App installed. The App installation is *only* for PR webhooks (Auto-fix). To restrict access, you must restrict the GitHub account/team itself. * *Key Change 3:* Troubleshooting section updated to reflect that installing the App on a specific repo is *not required* for access if the account has access via other means (like permissions). * *Interpretation:* This is a major clarification on permissions. Developers might have thought the GitHub App limited access scope, but it actually doesn't for session access; it only enables Auto-fix. Access is determined by the GitHub account's overall permissions. * **Page 2: `settings.md` (+1 / -1)** * *Topic:* `worktree.sparsePaths` setting. * *Key Change:* Added clarification: "plus root-level files". * *Interpretation:* Minor clarification. Sparse checkout isn't *just* those directories; it also grabs root files (like package.json, configs). Good to know for monorepo setups. * **Page 3: `skills.md` (+2 / -2)** * *Topic:* Skill discovery mechanism. * *Key Change:* Changed section title from "Automatic discovery from nested directories" to "Automatic discovery from **parent and nested** directories". * *Content Change:* Added explanation that project skills load from the start dir *and every parent directory up to the repo root*. * *Interpretation:* Previously, docs implied only nested (child) dirs were discovered. Now it clarifies upward traversal too. If you start in a subfolder of a repo, it still finds skills in the root. * **Page 4: `slash-commands.md` (+2 / -2)** * *Topic:* Skill discovery mechanism (duplicate content of `skills.md`). * *Key Change:* Identical to Page 3. * *Interpretation:* Consistency update across docs. 3. **Synthesize Analysis:** * **Overall Summary:** The update primarily clarifies permission scopes for cloud sessions (GitHub App vs. Account access) and refines documentation on workspace utilities (sparse checkout and skill discovery paths). * **Key Themes:** * *Cloud Access Control:* Correcting the misconception about GitHub App installation limiting repository access for cloud sessions. * *Workspace/Tooling Behavior:* Clarifying how `sparse-checkout` handles root files and how skills are discovered (upward traversal to repo root). * **Impact Level:** Medium. The GitHub access clarification is significant for security and permissions (High for teams using Cloud), while the others are Low/Medium (UX improvements). * **Action Items:** * Re-evaluate cloud session access permissions (don't rely solely on App installation for access control). * Leverage the new skill discovery behavior (start sessions anywhere in the repo). * Adjust expectations for sparse-checkout root files. 4. **Drafting the Response (in Chinese):** * *Summary:* 本次更新主要澄清了云端会话的 GitHub 权限机制，明确了 GitHub App 仅用于 Auto-fix 而非限制访问范围；同时优化了 Worktree 稀疏检出和 Skills 自动发现路径的文档说明。 * *Themes:* * **权限澄清**：修正了对 GitHub App 权限范围的误解，强调云端会话基于 GitHub 账号的整体权限，而非仅限已安装 App 的仓库。 * **工具行为细化**：明确了 Worktree sparse-checkout 会包含根目录文件，以及 Skills 发现机制支持向上遍历至仓库根目录。 * *Impact:* Medium. Reasoning: GitHub 权限的解释变化对团队安全配置至关重要，属于认知修正；其余为行为细节的文档完善。 * *Action Items:* * 审查团队在 GitHub 上的账号/组织权限配置，而非仅依赖 Claude App 安装来控制云端访问。 * 在 monorepo 中利用 Skills 的父目录遍历机制，在子目录启动会话时也能加载根目录技能。 * 使用 `worktree.sparsePaths` 时，预期会自动包含项目根目录的配置文件（如 `package.json`）。 5. **Refining for "World-class programmer" tone:** * Make it crisp. * Highlight the security implication of the GitHub access change (it's a "gotcha" fix). * Ensure the "Action items" are actionable. 6. **Final Polish (Chinese):** * Page 1 (Web/Auth): "Cloud sessions need access to your GitHub repositories..." -> Change: Clarified that App installation doesn't limit session scope. * Page 2 (Settings): "plus root-level files" -> Clarification. * Page 3 & 4 (Skills): "parent and nested directories" -> Feature clarification. *Drafting final output structure.* * **Overall Summary**: 本次文档核心更新在于澄清了云端会话的访问控制机制，指出了 GitHub App 并不限制会话访问范围；同时细化了 Worktree 稀疏检出和 Skills 发现路径的行为描述。 * **Key Themes**: * **安全性/权限修正**：强调云端会话的访问权限取决于连接的 GitHub 账号本身能看到的仓库，而 GitHub App 的安装仅用于启用 Auto-fix 功能，并非访问边界。 * **Monorepo 体验优化**：Skills 发现机制现在明确支持向上遍历至仓库根目录，提升了在子目录工作的灵活性。 * **配置细节明确**：明确了 sparse-checkout 行为（包含根文件）。 * **Impact**: Medium. Reasoning: 对云端权限模型的澄清可能影响安全策略（Medium/High），其他属于功能性描述完善（Low）。综合评定为 Medium。 * **Action Items**: * **安全审计**：若需严格限制云端会话的仓库访问，请直接在 GitHub 上限制账号/团队的权限，而非仅控制 GitHub App 的安装范围。 * **技能管理**：在 Monorepo 子目录中启动会话时，无需担心遗漏根目录定义的 `.claude/skills`。 * **配置预期**：在使用 `worktree.sparsePaths` 时，预期根目录配置文件（如 `tsconfig.json`, `package.json`）会被自动检出。 7. **Final Check against constraints:** * Single batch analysis? Yes. * Markdown format? Yes. * Chinese? Yes. * Concise and insightful? Yes. (Self-correction on impact: The GitHub change is actually quite significant if teams thought they were safe by not installing the app on certain repos. It's a security boundary misconception fix. I will emphasize this.) *Final Output Generation.*

1. **Analyze the Request:** * **Role:** World-class programmer. * **Task:** Analyze documentation changes (3 pages) as a single batch. * **Output Format:** Markdown, concise, insightful. * **Language:** Chinese. * **Structure:** 1. Overall Summary (1-2 sentences). 2. Key Themes (bullets). 3. Impact Level (Low/Medium/High/Breaking) with reasoning. 4. Action Items (max 5 bullets). 2. **Analyze the Changes (Page by Page):** * **Page 1: `discover-plugins.md`** * *Change:* Added info about `autoUpdate` in managed settings (`extraKnownMarketplaces`). * *Context:* Previously, auto-update was on for official, off for others. Now admins can force it on via managed settings entries. * **Page 2: `plugins-reference.md`** * *Change 1:* Added note about version 2.1.140 behavior regarding ignored default folders when manifest keys exist. It mentions the `/doctor` command flagging ignored folders. * *Change 2:* Updated `uninstall` command flag `-y/--yes`. Old description: "Required when stdin is not a TTY". New description: "Required when stdin or stdout is not a TTY". * *Change 3:* Updated `prune` command flag `-y/--yes`. Same change as above ("stdin or stdout is not a TTY"). * **Page 3: `settings.md`** * *Change 1:* Added info about "Embedding hosts" (like Claude Desktop) supplying policy via SDK `managedSettings`. Mentions `parentSettingsBehavior` set to `"merge"` to combine managed tiers. * *Change 2:* Added info about `autoUpdate` boolean in `extraKnownMarketplaces` entries (linking back to the change in `discover-plugins.md`). 3. **Synthesize Key Themes:** * **Theme 1: Enhanced Admin Control over Plugins/Auto-Updates.** The ability to set `autoUpdate` in managed marketplaces allows organizations to enforce plugin updates for security or consistency. * **Theme 2: Enterprise/Embedding Integration.** The `settings.md` change about embedding hosts merging settings implies better support for enterprise deployment (e.g., Claude Desktop embedding the Claude Code engine). * **Theme 3: CLI/UX Refinement.** The `-y` flag description change suggests an improvement in non-interactive environments (pipelines, scripts) where `stdout` might be redirected, not just `stdin`. The warning about ignored folders helps developers debug plugin configurations. 4. **Determine Impact Level:** * *Reasoning:* * The auto-update setting is additive (new option), not breaking. * The embedding host policy setting is additive/config behavior change. * The `-y` flag description update is a documentation clarification (or implies a bug fix) for edge cases in automation, but the flag itself existed. * The ignored folder warning is helpful for developers but not a breaking change. * *Conclusion:* **Low to Medium**. It's mostly configurability improvements and documentation clarifications. I'll lean towards **Low** for existing users, but **Medium** for enterprise admins/integrators because of the new `parentSettingsBehavior` and managed settings capabilities. 5. **Draft Action Items:** * Check if your organization needs to enforce auto-updates via managed settings. * Review `/doctor` or plugin details if you suspect a manifest key is overriding a default folder. * Verify scripts/pipelines: if you use `-y` with redirected output, it now officially covers stdout redirection. * (For embedders) Evaluate if `parentSettingsBehavior: "merge"` is needed to combine host and managed settings. 6. **Translate to Chinese & Refine (Drafting the Response):** * *Summary:* 此次更新主要增强了企业级配置能力，特别是针对插件自动更新的强制控制及嵌入宿主（如 Claude Desktop）的设置合并策略，同时优化了 CLI 命令在非交互式环境下的行为描述。 * *Themes:* * **企业级管理增强**: 新增了在托管设置中强制启用 `autoUpdate` 的能力，并允许嵌入宿主通过 SDK 合并策略设置。 * **配置与诊断改进**: 针对插件 manifest 覆盖默认目录的情况，提供了更清晰的诊断警告。 * **CLI 自动化支持**: 修正了 `-y/--yes` 标志的描述，明确其在 stdout 或 stdin 非 TTY 终端时的必要性。 * *Impact:* **Low** (主要针对管理员和集成商，现有功能无破坏性变更)。 * *Action Items:* * 企业管理员检查是否需要通过 `extraKnownMarketplaces` 强制开启插件自动更新。 * 开发者利用新增的诊断信息排查插件 manifest 配置路径问题。 * 脚本编写者确认在输出被重定向时使用 `-y` 标志的兼容性（虽然逻辑可能已支持，但文档现已明确）。 7. **Final Polish (Self-Correction during drafting):** * Make sure the `-y` flag explanation is clear: it's a documentation change to reflect that the requirement is now `stdin OR stdout`, not just `stdin`. * Ensure the "Embedding hosts" point is clear—it's about `managedSettings` merging. 8. **Final Output Generation** (matches the provided good response).

1. **Analyze the Request**: * **Role**: World-class programmer analyzing documentation changes. * **Input**: 11 pages of documentation diffs (Markdown). * **Output Format**: Markdown. * **Language**: Chinese (requested: "请用中文回复"). * **Structure**: 1. Overall Summary (1-2 sentences). 2. Key Themes (bullets). 3. Impact Level (Low/Medium/High/Breaking) with reasoning. 4. Action Items (max 5 bullets). 2. **Analyze the Diffs (Page by Page)**: * **`cli-reference.md`**: * Change 1: `--exclude-dynamic-system-prompt-sections` description updated from "git status" to "git-repo flag". *Significance*: Minor clarification on dynamic prompts. * Change 2: Expanded guidance on `--system-prompt` vs append flags. It now recommends using "Output Styles" for personas and "CLAUDE.md" for project conventions, instead of just replacing system prompts blindly. *Significance*: Better DX (Developer Experience), guides best practices. * **`data-usage.md`**: * Change 1: Added `CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC` to the list of conditions preventing survey popups. * Change 2: Added `DO_NOT_TRACK` to the list of env vars disabling surveys. * Change 3: Added a new env var `CLAUDE_CODE_ENABLE_FEEDBACK_SURVEY_FOR_OTEL=1` to re-enable surveys *only* for internal OpenTelemetry collectors when non-essential traffic is blocked. *Significance*: Improved telemetry control for enterprise/privacy-focused environments. * **`mcp.md`**: * Change: Removed a large chunk of code (React component `MCPServersTable` fetching from an API). The text "Claude Code can connect to..." remains. *Significance*: Likely moved to a dynamic component or handled differently in the build system. Documentation text is mostly unchanged, just implementation details removed from the source markdown. * **`monitoring-usage.md`**: * Change: Added a new telemetry event `claude_code.feedback_survey` with attributes like `event_type`, `appearance_id`, `enabled_via_override`. *Significance*: Aligns with the changes in `data-usage.md`. Allows monitoring survey participation via OTEL. * **`output-styles.md`**: * Change: Rewrote the comparison section "Output Styles vs. CLAUDE.md vs. --append-system-prompt". It clarifies *when* to use which (e.g., use Output Styles for identity changes, Append for extra rules). Also updated the comparison with Agents. *Significance*: Conceptual clarity for configuration management. * **`sandboxing.md`**: * Change: Added instructions for Ubuntu 24.04+ to configure AppArmor profile for `bwrap` (bubblewrap) because the default policy prevents user namespaces. *Significance*: Fixes a critical setup issue for newer Ubuntu users using sandboxing. * **`security.md`**: * Change: Updated the statement about MCP servers. Instead of "does not manage or audit", it says Anthropic "reviews connectors against listing criteria" but "does not security-audit". *Significance*: Legal/clarification on security responsibility. * **`settings.md`**: * Change: Added a new setting `teammateDefaultModel` for agent teams. *Significance*: New feature support for default model selection in agent teams. * **`about-claude/pricing.md`**: * Change: Added "Claude Opus 4.7" to the list of models supporting Fast Mode. *Significance*: Model availability update. * **`api/rate-limits.md`**: * Change: Added "Opus 4.7" to Fast Mode rate limits. *Significance*: Consistency with pricing update. * **`CHANGELOG.md.md`**: * Change: Added entry for version 2.1.140. Includes fixes for settings hot-reload (symlinks), background service startup, `/goal` hanging, and improvements to agent tool matching. *Significance*: Stability and performance improvements. 3. **Synthesize and Categorize**: * **Themes**: * **Configuration & Best Practices**: `cli-reference.md` and `output-styles.md` clarify when to use system prompts, output styles, and CLAUDE.md. * **Telemetry & Privacy Control**: `data-usage.md` and `monitoring-usage.md` introduce granular control over feedback surveys (OTEL override, `DO_NOT_TRACK`). * **Platform Support & Fixes**: `sandboxing.md` adds AppArmor fix for Ubuntu 24.04. `settings.md` adds agent team settings. `CHANGELOG` lists bug fixes. * **Model Updates**: Pricing and Rate limits added Opus 4.7 support for Fast Mode. * **Impact Level**: Medium. There are no breaking changes for existing workflows. The Ubuntu fix is important for new setups, and the telemetry changes are relevant for enterprise. The clarifications help avoid configuration errors. * **Action Items**: * Update Ubuntu 24.04 AppArmor config if using sandboxing. * Review telemetry settings if `DO_NOT_TRACK` or OTEL is used. * Check agent team settings for the new default model option. 4. **Draft the Response (in Chinese)**: * *Summary*: 此次更新主要优化了配置指南（系统提示词 vs 输出样式），增强了企业级遥测控制（特别是针对反馈调查），修复了 Ubuntu 24.04 上的沙箱问题，并增加了对 Opus 4.7 快速模式的支持。 * *Themes*: * 配置最佳实践澄清。 * 企业隐私与遥测控制增强。 * 操作系统兼容性修复。 * 模型与 Agent 功能扩展。 * *Impact*: Medium. 多为优化和修复，无破坏性变更，但 Ubuntu 沙箱问题对新用户影响较大。 * *Actions*: * 如果在 Ubuntu 24.04+ 使用沙箱，需配置 AppArmor。 * 企业用户检查新的遥测环境变量设置。 * Agent Team 用户可配置新的默认模型。 5. **Refine Content**: * Make sure the tone is professional ("World-class programmer"). * Ensure the distinction between `--append-system-prompt` and Output Styles is captured in the themes, as that was a big documentation rewrite. * Highlight the specific Ubuntu fix as it prevents runtime errors. 6. **Final Polish (Self-Correction during drafting)**: * *Correction*: The `mcp.md` diff removed a lot of code. I should mention it briefly as a docs implementation detail removal, but focus more on the functional changes. * *Correction*: Ensure `teammateDefaultModel` is mentioned in the settings section. 7. **Final Output Generation**: (Proceed to generate markdown based on the drafted points).

1. **Analyze the Request:** * **Role:** World-class programmer with deep expertise in developer tools and documentation. * **Task:** Analyze a specific documentation change (Diff provided) as a single batch. * **Output Format:** Concise analysis in Markdown. * **Language:** Chinese (as requested: "请用中文回复"). * **Input:** One change in `plugins.md` regarding the `--plugin-dir` flag. 2. **Analyze the Diff:** * **File:** `plugins.md` * **Change:** Added 2 lines (+2, -0). * **Content:** * Added text: "The flag also accepts a `.zip` archive of the plugin directory, which requires Claude Code v2.1.128 or later." * Added code block: `claude --plugin-dir ./my-plugin.zip` * **Context:** Previously, `--plugin-dir` only accepted a directory path. Now it accepts a zip file of that directory. 3. **Synthesize the Analysis (Drafting in English first for structure, then translating):** * **1. Overall Summary:** * *Draft:* The `--plugin-dir` flag now supports passing a `.zip` archive of a plugin, in addition to a standard directory path. * *Chinese:* `--plugin-dir` 标志现在支持直接传入插件目录的 `.zip` 压缩包，而不再局限于标准目录路径。 * **2. Key Themes:** * *Draft:* * Plugin distribution ease. * CLI flexibility. * *Chinese:* * 便捷的插件分发：允许开发者将插件打包为 zip 文件直接运行，无需解压。 * CLI 增强功能：扩展了命令行参数的文件格式支持。 * **3. Impact Level:** * *Draft:* Low (New feature, backward compatible). * *Chinese:* Low（低影响） * *Reasoning:* This is a purely additive enhancement. Existing workflows using directory paths remain untouched. It provides a new, more convenient way to distribute or share plugins (e.g., sharing a single zip file instead of a folder). * *Chinese Reasoning:* 这是一个纯粹的新增功能，向后兼容。现有的目录路径工作流不受影响，仅为开发者提供了更便捷的插件分发或共享方式（例如分享单个 zip 文件而非文件夹）。 * **4. Action items for developers:** * *Draft:* * Ensure Claude Code version >= v2.1.128. * Try passing `.zip` files to `--plugin-dir` for easier testing/sharing. * *Chinese:* * 确保使用 Claude Code v2.1.128 或更高版本以使用此功能。 * 尝试直接使用 `--plugin-dir ./my-plugin.zip` 来测试或分发打包好的插件，而无需先解压。 4. **Review and Refine:** * The analysis is concise and hits the key points: what changed, the benefit, the version requirement, and the action to take. * The tone is professional ("World-class programmer"). 5. **Final Output Generation (Markdown):** 1. **Overall Summary**: `--plugin-dir` 标志现在支持直接传入插件目录的 `.zip` 压缩包文件，不再局限于物理目录路径。 2. **Key Themes**: * **分发灵活性**：开发者可以将插件打包为 zip 文件直接运行，便于分享或分发。 * **版本依赖**：新功能引入了特定版本要求。 3. **Impact Level**: **Low**（低影响） * **Reasoning**：这是一个纯功能增强，向后兼容。现有代码无需修改，且为插件分发提供了一种更整洁的替代方案（无需解压文件夹）。 4. **Action items**: * 确保本地环境运行 Claude Code v2.1.128 或更高版本。 * 尝试将插件目录打包为 `.zip` 并通过 `--plugin-dir` 参数直接加载以简化测试流程。 6. **Final Polish (Self-Correction during drafting):** * Make sure the version number is accurate based on the diff text. Yes, "v2.1.128 or later". * Ensure the language is natural Chinese. 7. **Final Result Production.**