[DOCS] Comprehensive Documentation Update for Claude Code v2.0.0 Release
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-codepage 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-codepage 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 inen/api/agent-sdk/python. - What's Missing: The renaming is not consistently applied across the documentation, which will confuse users.
- Suggested Improvement:
- Perform a site-wide find-and-replace for "Claude Code SDK" to "Claude Agent SDK" on all relevant pages.
- Specifically, update the code examples in
en/api/agent-sdk/pythonto useClaudeAgentOptionsinstead of the oldClaudeCodeOptions.
---
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:
/rewind: Thecheckpointingpage only mentionsEsc+Esc. The/rewindcommand is not listed on theslash-commandspage./usage: Thecostsandslash-commandspages do not mention the new/usagecommand for checking plan limits. This creates confusion with the existing/costcommand.- Sticky Thinking Mode: The
interactive-modepage does not state that theTabkey to toggle thinking mode is now "sticky across sessions." Ctrl+RHistory Search: Theinteractive-modepage is missing the newCtrl+Rshortcut for history search.--agentsFlag: Thecli-referencepage is missing the new--agentsflag for dynamically defining subagents.
- Suggested Improvement:
- Update the
checkpointingpage to include/rewindas a primary command. Add/rewindto theslash-commandslist. - Add
/usageto theslash-commandslist and update thecostspage to clarify the distinction:/costfor session API token usage,/usagefor subscription plan limits. - Update the
interactive-modepage to note that the thinking mode state is persistent. - Add the
Ctrl+Rhistory search feature to theinteractive-modepage. - Add the
--agentsflag to thecli-referencepage, with an explanation of its function and a link to thesub-agentspage.
---
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:
- 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.
- Tool Usage Policy: The v2.0.0 prompt is much stricter in directing the agent to use specialized tools (
Read,Edit,Grep) over theirBashequivalents (cat,sed,grep). This best practice is not clearly communicated to users. - Removal of Bash Sandbox: The
dangerouslyOverrideSandboxparameter for theBashtool has been removed in the v2.0.0 system prompt. This is a critical security and functionality change that is not documented.
- Suggested Improvement:
- Add a section to the
overviewor a new "Best Practices" page explaining the new, more balanced response style. - Update the
Bashtool description on thesettingspage to clarify its intended use is for terminal operations (git,npm), not file manipulation, for which specialized tools should be used. - Update the
securitypage 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.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗