[DOCS] Comprehensive Documentation Update for Claude Code v2.0.0 Release

Resolved 💬 3 comments Opened Sep 29, 2025 by coygeek Closed Jan 9, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

This is a site-wide issue affecting multiple pages following the v2.0.0 release. Key pages include, but are not limited to: https://docs.claude.com/en/docs/claude-code/vs-code https://docs.claude.com/en/docs/claude-code/checkpointing https://docs.claude.com/en/docs/claude-code/costs https://docs.claude.com/en/docs/claude-code/interactive-mode https://docs.claude.com/en/docs/claude-code/common-workflows https://docs.claude.com/en/docs/claude-code/settings https://docs.claude.com/en/docs/claude-code/cli-reference https://docs.claude.com/en/docs/claude-code/sub-agents https://docs.claude.com/en/api/agent-sdk/overview https://docs.claude.com/en/api/agent-sdk/python

Section/Topic

The documentation is out of sync with the major v2.0.0 release. Updates are needed for: The new native VS Code extension. The rebranding of the "Claude Code SDK" to the "Claude Agent SDK". New and updated commands and CLI flags (/rewind, /usage, --agents). Changes in agent behavior, particularly response tone and tool usage policy. Removal of the Bash tool's sandbox feature. Updated workflows for Git and Pull Requests.

Current Documentation

---

A. New Native VS Code Extension

  • Current State: The en/docs/claude-code/vs-code page describes the extension as "Beta" and focuses on the "Legacy CLI Integration".
  • What's Missing: The changelog positions the native VS Code extension as a primary feature of v2.0.0. The documentation under-represents its status and capabilities.
  • Suggested Improvement: Rewrite the vs-code page to lead with the new native extension as the primary, recommended way to use Claude Code in VS Code. Detail its features (native UI, plan editing, etc.) and move the CLI integration content to a secondary section.

---

B. SDK Renaming to "Claude Agent SDK"

  • Current State: While a migration guide exists, the old name "Claude Code SDK" and old type ClaudeCodeOptions (in Python) still appear in various documentation pages and code examples, such as in en/api/agent-sdk/python.
  • What's Missing: The renaming is not consistently applied across the documentation, which will confuse users.
  • Suggested Improvement:
  1. Perform a site-wide find-and-replace for "Claude Code SDK" to "Claude Agent SDK" on all relevant pages.
  2. Specifically, update the code examples in en/api/agent-sdk/python to use ClaudeAgentOptions instead of the old ClaudeCodeOptions.

---

C. New and Updated Commands/Features

  • Current State: The documentation for commands and interactive features is missing several v2.0.0 updates.
  • What's Missing:
  1. /rewind: The checkpointing page only mentions Esc+Esc. The /rewind command is not listed on the slash-commands page.
  2. /usage: The costs and slash-commands pages do not mention the new /usage command for checking plan limits. This creates confusion with the existing /cost command.
  3. Sticky Thinking Mode: The interactive-mode page does not state that the Tab key to toggle thinking mode is now "sticky across sessions."
  4. Ctrl+R History Search: The interactive-mode page is missing the new Ctrl+R shortcut for history search.
  5. --agents Flag: The cli-reference page is missing the new --agents flag for dynamically defining subagents.
  • Suggested Improvement:
  1. Update the checkpointing page to include /rewind as a primary command. Add /rewind to the slash-commands list.
  2. Add /usage to the slash-commands list and update the costs page to clarify the distinction: /cost for session API token usage, /usage for subscription plan limits.
  3. Update the interactive-mode page to note that the thinking mode state is persistent.
  4. Add the Ctrl+R history search feature to the interactive-mode page.
  5. Add the --agents flag to the cli-reference page, with an explanation of its function and a link to the sub-agents page.

---

D. Changes to Agent Behavior and System Prompt

  • Current State: The documentation does not reflect the significant changes to the agent's core instructions in the v2.0.0 system prompt.
  • What's Missing:
  1. Response Tone: The v1.0.126 prompt instructed the agent to be hyper-concise ("One word answers are best"). The v2.0.0 prompt changes this to provide "complete information" matching the complexity of the query. The documentation does not reflect this important shift in user experience.
  2. Tool Usage Policy: The v2.0.0 prompt is much stricter in directing the agent to use specialized tools (Read, Edit, Grep) over their Bash equivalents (cat, sed, grep). This best practice is not clearly communicated to users.
  3. Removal of Bash Sandbox: The dangerouslyOverrideSandbox parameter for the Bash tool has been removed in the v2.0.0 system prompt. This is a critical security and functionality change that is not documented.
  • Suggested Improvement:
  1. Add a section to the overview or a new "Best Practices" page explaining the new, more balanced response style.
  2. Update the Bash tool description on the settings page to clarify its intended use is for terminal operations (git, npm), not file manipulation, for which specialized tools should be used.
  3. Update the security page to remove any mention of the old sandbox model and clarify the current security model for tool execution.

What's Wrong or Missing?

.

Suggested Improvement

.

Impact

High - Prevents users from using a feature

Additional Context

These updates are essential for aligning the documentation with the Claude Code v2.0.0 release. The changes are based on a direct comparison of the official documentation, the v2.0.0 changelog, and the system prompts for versions 1.0.126 and 2.0.0. Clear documentation on these points will prevent user confusion and ensure a smoother adoption of the new version.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗