docs: Claude Code v2.1.210 - worktree isolation security fix, screen reader mode, auto mode everywhere

Co-Authored-By: claude-yolo[bot] <claude-yolo@lroole.com>

Author: github-actions[bot]

content/.metadata.json

@@ -1,12 +1,12 @@
 {
   "name": "@anthropic-ai/claude-code",
-  "version": "2.1.204",
+  "version": "2.1.210",
   "author": {
     "name": "Anthropic",
     "email": "support@anthropic.com"
   },
   "license": "SEE LICENSE IN README.md",
-  "_id": "@anthropic-ai/claude-code@2.1.204",
+  "_id": "@anthropic-ai/claude-code@2.1.210",
   "maintainers": [
     {
       "name": "zak-anthropic",
@@ -69,20 +69,20 @@
     "claude": "bin/claude.exe"
   },
   "dist": {
-    "shasum": "b34139bd500ec82f463568ec8933c296d568c1c5",
-    "tarball": "https://registry.npmjs.org/@anthropic-ai/claude-code/-/claude-code-2.1.204.tgz",
+    "shasum": "8b0306a7497680b242955a53db363e13b846406d",
+    "tarball": "https://registry.npmjs.org/@anthropic-ai/claude-code/-/claude-code-2.1.210.tgz",
     "fileCount": 7,
-    "integrity": "sha512-DmU1s/YJVvbdTAYiv9YTdA06qaD27otG5OJ2VVGGguQPMiyvfcoPP+//JJACbmBDcxMm121aqBssOXDp+4UXeQ==",
+    "integrity": "sha512-VlV7HSkli4UhlZXF5dWmDolXDz16GJdhgpUbVeXnylRHjr6fDDQtgZhO1X1JAxrQjufqXhOs3o1hveqZjLmjNw==",
     "signatures": [
       {
-        "sig": "MEQCIH5qfRlpeeSti6j1r4BrN8IhhcxFUdMrnIqLEiakOEzwAiAfQ1I/grIztJI6jhZcKFXJcg11DzT2WQ0NZ8UZq/u90Q==",
+        "sig": "MEUCIQCUYqIgtuONo0wZRQwBzcB0Y+a5xJLKyl3pFik/CsJ0RQIgWza3fG95n/Xala7jMGrkr+ASAZrrhFiSG+VlphcfWzg=",
         "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"
       }
     ],
-    "unpackedSize": 157204
+    "unpackedSize": 158809
   },
   "type": "module",
-  "_from": "file:staged-npm/anthropic-ai-claude-code-2.1.204.tgz",
+  "_from": "file:staged-npm/anthropic-ai-claude-code-2.1.210.tgz",
   "engines": {
     "node": ">=22.0.0"
   },
@@ -94,8 +94,8 @@
     "name": "wolffiex",
     "email": "wolffiex@anthropic.com"
   },
-  "_resolved": "/home/runner/work/claude-cli-internal/claude-cli-internal/staged-npm/anthropic-ai-claude-code-2.1.204.tgz",
-  "_integrity": "sha512-DmU1s/YJVvbdTAYiv9YTdA06qaD27otG5OJ2VVGGguQPMiyvfcoPP+//JJACbmBDcxMm121aqBssOXDp+4UXeQ==",
+  "_resolved": "/home/runner/work/claude-cli-internal/claude-cli-internal/staged-npm/anthropic-ai-claude-code-2.1.210.tgz",
+  "_integrity": "sha512-VlV7HSkli4UhlZXF5dWmDolXDz16GJdhgpUbVeXnylRHjr6fDDQtgZhO1X1JAxrQjufqXhOs3o1hveqZjLmjNw==",
   "_npmVersion": "11.16.0",
   "description": "Use Claude, Anthropic's AI assistant, right from your terminal. Claude can understand your codebase, edit files, run terminal commands, and handle entire workflows for you.",
   "directories": {},
@@ -104,17 +104,17 @@
   "_hasShrinkwrap": false,
   "readmeFilename": "README.md",
   "optionalDependencies": {
-    "@anthropic-ai/claude-code-linux-x64": "2.1.204",
-    "@anthropic-ai/claude-code-win32-x64": "2.1.204",
-    "@anthropic-ai/claude-code-darwin-x64": "2.1.204",
-    "@anthropic-ai/claude-code-linux-arm64": "2.1.204",
-    "@anthropic-ai/claude-code-win32-arm64": "2.1.204",
-    "@anthropic-ai/claude-code-darwin-arm64": "2.1.204",
-    "@anthropic-ai/claude-code-linux-x64-musl": "2.1.204",
-    "@anthropic-ai/claude-code-linux-arm64-musl": "2.1.204"
+    "@anthropic-ai/claude-code-linux-x64": "2.1.210",
+    "@anthropic-ai/claude-code-win32-x64": "2.1.210",
+    "@anthropic-ai/claude-code-darwin-x64": "2.1.210",
+    "@anthropic-ai/claude-code-linux-arm64": "2.1.210",
+    "@anthropic-ai/claude-code-win32-arm64": "2.1.210",
+    "@anthropic-ai/claude-code-darwin-arm64": "2.1.210",
+    "@anthropic-ai/claude-code-linux-x64-musl": "2.1.210",
+    "@anthropic-ai/claude-code-linux-arm64-musl": "2.1.210"
   },
   "_npmOperationalInternal": {
-    "tmp": "tmp/claude-code_2.1.204_1783469097416_0.06481989301297486",
+    "tmp": "tmp/claude-code_2.1.210_1784057961569_0.16964935035617112",
     "host": "s3://npm-registry-packages-npm-production"
   }
 }

content/CHANGELOG.md

@@ -469,7 +469,7 @@ Organize findings by theme. Include:
 Check that every claim references the correct source document. If citations are incomplete, return to Step 3.
 ````
 
-This example shows how workflows apply to analysis tasks that don't require code. The checklist pattern works for any complex, multi-step process.
+This example shows how workflows apply to analysis tasks that don't require code. The checklist pattern works for any complex, multistep process.
 
 **Example 2: PDF form filling workflow** (for Skills with code):
 
@@ -514,7 +514,7 @@ Run: `python scripts/verify_output.py output.pdf`
 If verification fails, return to Step 2.
 ````
 
-Clear steps prevent Claude from skipping critical validation. The checklist helps both Claude and you track progress through multi-step workflows.
+Clear steps prevent Claude from skipping critical validation. The checklist helps both Claude and you track progress through multistep workflows.
 
 ### Implement feedback loops
 
@@ -1036,7 +1036,7 @@ Skills run in a code execution environment with filesystem access, bash commands
 
 1. **Metadata pre-loaded:** At startup, the name and description from all Skills' YAML frontmatter are loaded into the system prompt
 2. **Files read on-demand:** Claude uses bash Read tools to access SKILL.md and other files from the filesystem when needed
-3. **Scripts executed efficiently:** Utility scripts can be executed via bash without loading their full contents into context. Only the script's output consumes tokens
+3. **Scripts executed efficiently:** Utility scripts can be executed through bash without loading their full contents into context. Only the script's output consumes tokens
 4. **No context penalty for large files:** Reference files, data, or documentation don't consume context tokens until actually read
 
 * **File paths matter:** Claude navigates your skill directory like a filesystem. Use forward slashes (`reference/guide.md`), not backslashes

content/claude-code-manifest.json

@@ -91,11 +91,11 @@ Evaluation results signal when to act:
   </Step>
 
   <Step title="Deploy">
-    Upload via the Skills API for workspace-wide access. See [Using Skills with the API](/docs/en/build-with-claude/skills-guide) for upload and version management. Document the Skill in your internal registry with purpose, owner, and version.
+    Upload through the Skills API for workspace-wide access. See [Using Skills with the API](/docs/en/build-with-claude/skills-guide) for upload and version management. Document the Skill in your internal registry with purpose, owner, and version.
   </Step>
 
   <Step title="Monitor">
-    Track usage patterns and collect feedback from users. Re-run evaluations periodically to detect drift or regressions as workflows and models evolve. Usage analytics are not currently available via the Skills API. Implement application-level logging to track which Skills are included in requests.
+    Track usage patterns and collect feedback from users. Re-run evaluations periodically to detect drift or regressions as workflows and models evolve. Usage analytics are not currently available through the Skills API. Implement application-level logging to track which Skills are included in requests.
   </Step>
 
   <Step title="Iterate or deprecate">
@@ -113,7 +113,7 @@ Note that API requests support a maximum of 8 Skills per request (see [Using Ski
 
 ### Start specific, consolidate later
 
-Encourage teams to start with narrow, workflow-specific Skills rather than broad, multi-purpose ones. As patterns emerge across your organization, consolidate related Skills into role-based bundles.
+Encourage teams to start with narrow, workflow-specific Skills rather than broad, multipurpose ones. As patterns emerge across your organization, consolidate related Skills into role-based bundles.
 
 <Tip>
   Use evaluations to decide when to consolidate. Merge narrow Skills into a broader one only when the consolidated Skill's evaluations confirm equivalent performance to the individual Skills it replaces.
@@ -150,11 +150,11 @@ Each role-based bundle should contain only the Skills relevant to that role's da
 
 ### Source control
 
-Store Skill directories in Git for history tracking, code review via pull requests, and rollback capability. Each Skill directory (containing SKILL.md and any bundled files) maps naturally to a Git-tracked folder.
+Store Skill directories in Git for history tracking, code review through pull requests, and rollback capability. Each Skill directory (containing SKILL.md and any bundled files) maps naturally to a Git-tracked folder.
 
 ### API-based distribution
 
-The Skills API provides workspace-scoped distribution. Skills uploaded via the API are available to all workspace members. See [Using Skills with the API](/docs/en/build-with-claude/skills-guide) for upload, versioning, and management endpoints.
+The Skills API provides workspace-scoped distribution. Skills uploaded through the API are available to all workspace members. See [Using Skills with the API](/docs/en/build-with-claude/skills-guide) for upload, versioning, and management endpoints.
 
 ### Versioning strategy