Changes on 2026-09-21

1. **Analyze the Request:** * **Role:** World-class programmer analyzing documentation changes. * **Format:** Markdown, concise, insightful, Chinese response. * **Input:** Diffs from 17 pages. * **Output Structure:** Overall Summary, Key Themes, Impact Level, Action Items. 2. **Analyze the Diffs (Page by Page):** * **`desktop.md` & `network-config.md`**: Added `unpkg.com` to the list of allowed external hosts for loading JavaScript libraries in Artifacts. * *Impact:* Minor feature expansion for Artifacts. * **`discover-plugins.md`**: Updated instructions for installing plugins when `/plugin` isn't available. Added VS Code extension as an option (previously only mentioned desktop app and cloud sessions). * *Impact:* Improved UX/Docs clarity for plugin installation across different environments. * **`interactive-mode.md`**: * Added `Ctrl+Enter` or `Ctrl+X Ctrl+S` to send queued messages immediately. * Clarified memory pressure logic for background tasks (macOS/Linux): "terminates" -> "stops", added debug log mention. * *Impact:* New keyboard shortcut, better observability for background task management. * **`monitoring-usage.md`**: * Added `OTEL_LOG_MANAGED_SETTINGS` environment variable. * Added `effort` attribute to traces. * *Impact:* Enhanced observability/telemetry capabilities. * **`vs-code.md`**: * Effort levels: Clarified that non-`max` levels are saved to user settings as defaults. * Added "Sign out" option in Settings (v2.1.277). * Added "Copy a response" feature (hover + button or `/copy` command) (v2.1.277). * Agent map: Now lists background tasks (shell/monitors) alongside subagents. * *Impact:* Significant UX improvements for VS Code extension users (copying, signing out, task monitoring). * **`build-with-claude/overview.md` & `text-generation.md`**: Updated "Compaction" link to "Compaction at a token threshold". * *Impact:* Doc navigation update. * **`build-with-claude/*.md` (pdf-support, citations, structured-outputs, effort, files, computer-use-tool, code-execution-tool, programmatic-tool-calling, mcp-connector)**: * *Common Pattern:* Replaced the text-based "Compatibility" section with a structured `featureMetadata` frontmatter block. * *Content:* Standardized info on status (GA/Beta), ZDR eligibility, supported models (lists), and supported platforms. * *Specifics:* No actual logic changes, just structural metadata migration for better documentation generation/management. 3. **Synthesize Key Themes:** * **Standardization/Metadata Migration:** A bulk update to move compatibility info into `featureMetadata` frontmatter across multiple API pages. * **Artifact/Environment Enhancements:** Added `unpkg.com` support and new keyboard shortcuts. * **Observability:** New OTEL flags and trace attributes. * **VS Code UX Improvements:** Better agent map, copy command, effort level persistence, sign out. * **Plugin Installation:** Clarified paths for different environments (specifically VS Code). 4. **Determine Impact Level:** * *Most changes are doc structure (metadata)*: Low impact on code, but good to know. * *API changes*: None in logic, just links and metadata. * *Tooling changes (VS Code/Desktop/CLI)*: New shortcuts (`Ctrl+Enter`), new endpoints allowed (`unpkg.com`), new telemetry fields. These are "nice to have" or "need to know for monitoring" but not "breaking". * *Verdict*: **Low to Medium**. It's mostly documentation structure updates (metadata migration) and minor feature additions/clarifications for the tools. 5. **Draft Action Items:** * Update firewall/proxy rules to include `unpkg.com` for Artifacts. * Check VS Code extension updates for new "Copy response" and "Agent map" features. * Update telemetry parsing if using OTEL to handle new `effort` and `managed_settings` fields. * Review `featureMetadata` in API docs if you rely on scraping/programmatic doc reading. 6. **Refine the Output (Chinese):** * *Summary*: Mainly structural updates to API documentation (metadata migration) and minor feature enhancements for Claude tools (VS Code, Desktop, CLI). * *Themes*: Metadata migration, Artifact support expansion, Observability improvements, VS Code UX. * *Impact*: Low. * *Action Items*: Whitelist unpkg.com, parse new OTEL fields, check VS Code updates. 7. **Final Polish (Reviewing against the generated diffs):** * Did I miss anything? The "Compaction at a token threshold" link change is minor but part of the API updates. * The `interactive-mode` change about "memory pressure" is a refinement of existing behavior description, not a behavioral change per se, but good for debugging. * The `vs-code` change about "Effort" saving to settings is a behavior change to note for users. 8. **Construct Final Response:** (Proceeding to generate markdown).

1. **Analyze the Request:** * **Role:** World-class programmer analyzing documentation changes. * **Input:** A batch of 9 pages with diffs (markdown format). * **Output:** Concise, insightful analysis in 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 Diff Content:** * **`api/messages.md`**: Added detailed descriptions for the `anthropic-workspace-id` header. This addition occurs multiple times (API create, batch create, retrieve batch, cancel batch, delete batch). The text says it's optional, selects a Workspace, needed for multi-workspace credentials, and must match specific workspace credentials if sent. * **`api/messages/count_tokens.md`**: Same addition of `anthropic-workspace-id` header description. * **`api/messages/batches/create.md`**: Same addition of `anthropic-workspace-id` header description. * **`api/models/list.md`**: Same addition of `anthropic-workspace-id` header description. * **`api/beta/files/upload.md`**: Same addition of `anthropic-workspace-id` header description. * **`build-with-claude/overview.md`**: Updated the table description for "Beta" features. Changed "Beta features on the Claude API... have a beta header" to "Most beta features... have a beta header". Minor clarification. * **`build-with-claude/text-generation.md`**: Same table update as `overview.md`. * **`build-with-claude/context-editing.md`**: Changed internal documentation links from `/compaction` to `/compaction-threshold`. Applied to Python, C#, Go, Java, PHP SDK tool runner notes. * **`agents-and-tools/tool-use/computer-use-tool.md`**: Clarified text regarding `computer_20251124` integrations, noting they work on specific models listed under "Earlier tool versions". 3. **Synthesize Themes:** * **Workspace Multi-tenancy:** The biggest change is the standardization of the `anthropic-workspace-id` header documentation across almost all API endpoints (messages, batches, models, files). This suggests a push towards better support for multi-workspace environments or clearer documentation of existing capabilities. * **Documentation Hygiene/Link Updates:** Updating internal links (compaction -> compaction-threshold) and clarifying Beta feature descriptions. 4. **Determine Impact:** * *Level:* Low. * *Reasoning:* The changes are primarily documentation additions and clarifications. The `anthropic-workspace-id` header likely existed (optional) but wasn't fully documented or standardized in text across all pages. No new required parameters were added, nor were existing behaviors changed. The link updates are internal doc maintenance. 5. **Formulate Action Items:** * Developers using multi-workspace credentials should review the new header descriptions to ensure correct implementation (though it's optional). * If referencing specific compaction docs in internal guides, update links. * Generally, just "be aware" is sufficient. 6. **Draft the Response (Internal Monologue/Rough Draft in Chinese):** * *Summary:* 本次更新主要完善了 API 文档中关于 `anthropic-workspace-id` 请求头的描述，并修正了部分内部链接和功能说明。 * *Themes:* 新增多工作区请求头的详细说明；文档链接标准化（compaction）；Beta 功能描述微调。 * *Impact:* Low。主要是对现有可选功能的文档补全和链接修正，未引入破坏性变更或新强制性参数。 * *Actions:* 关注 `anthropic-workspace-id` 的多工作区使用场景；注意 compaction 相关文档链接变更。 7. **Refine and Polish (Final Output Generation):** * *Summary:* 本次更新主要统一并详细说明了 API 请求中的 `anthropic-workspace-id` 请求头用法，同时修正了部分内部文档链接和功能描述。 * *Key Themes:* * **多工作区支持标准化**：在 Messages、Batches、Models 和 Files 等多个 API 端点的文档中，新增了 `anthropic-workspace-id` 请求头的详细说明，明确了其在多工作区凭证下的使用规则（可选、需匹配特定 ID）。 * **文档维护与链接修正**：将上下文编辑相关的内部文档链接从 `/compaction` 更新为 `/compaction-threshold`，涉及 Python、C#、Go、Java、PHP 等多个 SDK 的说明。 * **描述微调**：对 Beta 功能的分类描述和计算机使用工具的兼容性说明进行了细微的文字修正。 * *Impact:* **Low**。本次变更仅限于文档层面的完善和修正，未引入新的必选参数或破坏性变更，对现有代码运行逻辑无影响。 * *Action Items:* * 如果您使用跨多个工作区的凭证，请查阅更新后的 `anthropic-workspace-id` 请求头文档以确保正确配置。 * 如果您的内部文档引用了旧的 `compaction` 链接，请更新为 `compaction-threshold`。 * 无需修改现有代码逻辑，仅需关注文档说明。 8. **Final Review against Constraints:** * Markdown format? Yes. * Chinese? Yes. * Concise? Yes. * Action items max 5? Yes. (Self-correction: Ensure the workspace ID section emphasizes that it's for multi-workspace credentials, as that's the core insight added.) *Refined Action Item 1:* "如果您正在管理跨多个工作区的凭证..." sounds better. Let's output.

Let me analyze these documentation changes. 1. **model-config.md**: Two significant changes: - The `opusplan` model description was updated to clarify that the execution phase uses the same context window as `sonnet` (not just the planning phase uses opus's window). Also updated to reflect that when opus and sonnet resolve to models that run with 1M context by default (as current models do on the Anthropic API), both phases run with it automatically. - The extended context section was substantially rewritten: - Fable 5.1, Fable 5, Sonnet 5, and Opus 4.7+ now run with 1M window by default on every plan including Pro. No need for `[1m]` variant or usage credits for the 1M window on these models. - Opus 4.6 and Sonnet 4.6 are now clearly separated as older models that need the `[1m]` variant to reach 1M. - The table header changed from "Opus with 1M context" to "Opus 4.6 with 1M context" — clarifying this only applies to the older model. 2. **CHANGELOG.md.md**: Removed one line about a VSCode fix: "Fixed some claude.ai/code sessions opening in VS Code as an empty conversation with no messages". This suggests either the fix was reverted or the changelog entry was removed for another reason. Key themes: - Clarification of 1M context window behavior across different model versions and plans - Newer models (Sonnet 5, Opus 4.7+, Fable 5/5.1) get 1M by default on all plans - Older models (Opus 4.6, Sonnet 4.6) still need `[1m]` variant and plan-dependent access - `opusplan` context window behavior clarified for both phases