Skip to content
Open
991 changes: 991 additions & 0 deletions docs/upstream-improvements-context.md

Large diffs are not rendered by default.

97 changes: 54 additions & 43 deletions skills/working-with-claude-code/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ description: Use when working with Claude Code CLI, plugins, hooks, MCP servers,

## Overview

This skill provides complete, authoritative documentation for Claude Code directly from docs.claude.com. Instead of guessing about configuration paths, API structures, or feature capabilities, read the official docs stored in this skill's references directory.
This skill provides complete, authoritative documentation for Claude Code directly from code.claude.com. Instead of guessing about configuration paths, API structures, or feature capabilities, read the official docs stored in this skill's references directory.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

official Claude Code documentation domain site:anthropic.com

💡 Result:

Here are the official Claude Code documentation pages on Anthropic’s site:

  • Claude Code overview (official docs): docs.anthropic.com/en/docs/claude-code/overview. [1]
  • Claude Code SDK / Quickstart: docs.anthropic.com/s/claude-code-sdk. [2]
  • Product page / features: anthropic.com/claude-code. [3]

Sources: [1] [2] [3].


🌐 Web query:

code.claude.com Claude Code docs

💡 Result:

You can find the official Claude Code docs on Anthropic’s site:

(There are also third‑party mirrors/summaries, but use the Anthropic docs above for the authoritative reference.) [3]


Update domain reference: code.claude.com is not the official Claude Code documentation source.

The official Claude Code documentation is hosted at docs.anthropic.com/en/docs/claude-code/overview, not code.claude.com. SKILL.md should reference the authoritative Anthropic documentation domain (docs.anthropic.com) instead of the unverified code.claude.com domain to ensure accuracy and stability for documentation consumers.

🤖 Prompt for AI Agents
In skills/working-with-claude-code/SKILL.md around line 10, the domain reference
points to code.claude.com which is not the authoritative source; update the
reference to the official Claude Code docs at
docs.anthropic.com/en/docs/claude-code/overview, replacing any occurrences of
code.claude.com with the docs.anthropic.com URL and ensure any link text and
context reflect the authoritative Anthropic documentation domain.


## When to Use

Expand All @@ -34,6 +34,11 @@ Use this skill when:
| Troubleshoot issues | `troubleshooting.md` |
| General setup | `setup.md` or `quickstart.md` |
| Configuration options | `settings.md` |
| Web-based Claude Code | `claude-code-on-the-web.md` |
| Desktop app | `desktop.md` |
| Chrome extension | `chrome.md` |
| Sandboxing/security | `sandboxing.md` |
| Slack integration | `slack.md` |

## Documentation Organization

Expand All @@ -42,47 +47,53 @@ All documentation is stored as individual markdown files in `references/`. Use t
```
references/
├── overview.md # Claude Code introduction
├── quickstart.md # Getting started guide
├── setup.md # Installation and setup
├── plugins.md # Plugin development
├── plugins-reference.md # Plugin API reference
├── plugin-marketplaces.md # Plugin marketplaces
├── skills.md # Skill creation
├── mcp.md # MCP server integration
├── hooks.md # Hooks overview
├── hooks-guide.md # Hooks implementation guide
├── slash-commands.md # Slash command reference
├── sub-agents.md # Subagent usage
├── settings.md # Configuration reference
├── cli-reference.md # CLI command reference
├── common-workflows.md # Common usage patterns
├── interactive-mode.md # Interactive mode guide
├── headless.md # Headless mode guide
├── output-styles.md # Output customization
├── statusline.md # Status line configuration
├── memory.md # Memory and context management
├── checkpointing.md # Checkpointing feature
├── analytics.md # Usage analytics
├── costs.md # Cost tracking
├── monitoring-usage.md # Usage monitoring
├── data-usage.md # Data usage policies
├── security.md # Security features
├── iam.md # IAM integration
├── network-config.md # Network configuration
├── terminal-config.md # Terminal configuration
├── model-config.md # Model configuration
├── llm-gateway.md # LLM gateway setup
├── amazon-bedrock.md # AWS Bedrock integration
├── google-vertex-ai.md # Google Vertex AI integration
├── vs-code.md # VS Code integration
├── jetbrains.md # JetBrains integration
├── devcontainer.md # Dev container support
├── github-actions.md # GitHub Actions integration
├── gitlab-ci-cd.md # GitLab CI/CD integration
├── quickstart.md # Getting started guide
├── setup.md # Installation and setup
├── common-workflows.md # Common usage patterns
├── claude-code-on-the-web.md # Web-based Claude Code
├── desktop.md # Desktop application
├── chrome.md # Chrome extension
├── plugins.md # Plugin development
├── plugins-reference.md # Plugin API reference
├── plugin-marketplaces.md # Plugin marketplaces
├── discover-plugins.md # Plugin discovery
├── skills.md # Skill creation
├── mcp.md # MCP server integration
├── hooks.md # Hooks overview
├── hooks-guide.md # Hooks implementation guide
├── slash-commands.md # Slash command reference
├── sub-agents.md # Subagent usage
├── settings.md # Configuration reference
├── cli-reference.md # CLI command reference
├── interactive-mode.md # Interactive mode guide
├── headless.md # Headless mode guide
├── output-styles.md # Output customization
├── statusline.md # Status line configuration
├── memory.md # Memory and context management
├── checkpointing.md # Checkpointing feature
├── sandboxing.md # Sandboxing and security isolation
├── analytics.md # Usage analytics
├── costs.md # Cost tracking
├── monitoring-usage.md # Usage monitoring
├── data-usage.md # Data usage policies
├── security.md # Security features
├── iam.md # IAM integration
├── network-config.md # Network configuration
├── terminal-config.md # Terminal configuration
├── model-config.md # Model configuration
├── llm-gateway.md # LLM gateway setup
├── amazon-bedrock.md # AWS Bedrock integration
├── google-vertex-ai.md # Google Vertex AI integration
├── microsoft-foundry.md # Microsoft Azure AI Foundry
├── vs-code.md # VS Code integration
├── jetbrains.md # JetBrains integration
├── devcontainer.md # Dev container support
├── github-actions.md # GitHub Actions integration
├── gitlab-ci-cd.md # GitLab CI/CD integration
├── slack.md # Slack integration
├── third-party-integrations.md # Other integrations
├── legal-and-compliance.md # Legal information
├── troubleshooting.md # Troubleshooting guide
└── migration-guide.md # Migration guide
├── legal-and-compliance.md # Legal information
└── troubleshooting.md # Troubleshooting guide
```
Comment on lines 47 to 97
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# First, check if the SKILL.md file exists
if [ ! -f "skills/working-with-claude-code/SKILL.md" ]; then
  echo "File not found: skills/working-with-claude-code/SKILL.md"
  exit 1
fi

# Run the provided verification script
python - <<'PY'
import re, pathlib, sys
p = pathlib.Path("skills/working-with-claude-code/SKILL.md")
text = p.read_text(encoding="utf-8")
# pull markdown filenames from the tree block lines
names = sorted(set(re.findall(r'`?([a-z0-9][a-z0-9\-]*\.md)`?', text)))
base = pathlib.Path("skills/working-with-claude-code/references")
missing = [n for n in names if not (base/n).exists()]
if missing:
    print("Missing reference files:")
    for n in missing: print(" -", n)
    sys.exit(1)
print(f"OK: {len(names)} referenced .md files exist under references/")
PY

Repository: obra/superpowers-developing-for-claude-code

Length of output: 173


🏁 Script executed:

# Also, let's list the actual contents of the references directory to see what exists
if [ -d "skills/working-with-claude-code/references" ]; then
  echo "=== Actual files in references/ directory ==="
  ls -1 "skills/working-with-claude-code/references" | grep "\.md$" | sort
else
  echo "references/ directory does not exist"
fi

Repository: obra/superpowers-developing-for-claude-code

Length of output: 884


Update references/ tree to include missing files: claude_code_docs_map.md and migration-guide.md.

The tree block in SKILL.md (lines 46-94) lists 45 files, but the actual references/ directory contains 48 files. The two missing entries are claude_code_docs_map.md and migration-guide.md. To prevent future drift, consider auto-generating this tree from the filesystem (e.g., via scripts/update_docs.js) rather than maintaining it manually.

🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

46-46: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents
In skills/working-with-claude-code/SKILL.md around lines 46 to 94, the
references/ tree is missing two files (claude_code_docs_map.md and
migration-guide.md); update the listed tree to include these two entries in the
appropriate alphabetical/structural positions, and to prevent future drift add
or update a docs generation step (e.g., scripts/update_docs.js) that reads the
references/ directory and regenerates the tree block automatically as part of
the docs build or a pre-commit hook.


## Workflow
Expand Down Expand Up @@ -121,7 +132,7 @@ path: ~/.claude/skills/working-with-claude-code/references/

## Updating Documentation

The skill includes `scripts/update_docs.js` to fetch the latest documentation from docs.claude.com.
The skill includes `scripts/update_docs.js` to fetch the latest documentation from code.claude.com.

Run when:
- Documentation seems outdated
Expand All @@ -133,7 +144,7 @@ node ~/.claude/skills/working-with-claude-code/scripts/update_docs.js
```

The script:
1. Fetches llms.txt from docs.claude.com
1. Fetches llms.txt from code.claude.com/docs/
2. Extracts all Claude Code documentation URLs
3. Downloads each page to `references/`
4. Reports success/failures
Expand Down
65 changes: 46 additions & 19 deletions skills/working-with-claude-code/references/amazon-bedrock.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,20 +7,20 @@
Before configuring Claude Code with Bedrock, ensure you have:

* An AWS account with Bedrock access enabled
* Access to desired Claude models (e.g., Claude Sonnet 4.5) in Bedrock
* Access to desired Claude models (for example, Claude Sonnet 4.5) in Bedrock
* AWS CLI installed and configured (optional - only needed if you don't have another mechanism for getting credentials)
* Appropriate IAM permissions

## Setup

### 1. Enable model access
### 1. Submit use case details

First, ensure you have access to the required Claude models in your AWS account:
First-time users of Anthropic models are required to submit use case details before invoking a model. This is done once per account.

1. Navigate to the [Amazon Bedrock console](https://console.aws.amazon.com/bedrock/)
2. Go to **Model access** in the left navigation
3. Request access to desired Claude models (e.g., Claude Sonnet 4.5)
4. Wait for approval (usually instant for most regions)
1. Ensure you have the right IAM permissions (see more on that below)
2. Navigate to the [Amazon Bedrock console](https://console.aws.amazon.com/bedrock/)
3. Select **Chat/Text playground**
4. Choose any Anthropic model and you will be prompted to fill out the use case form

### 2. Configure AWS credentials

Expand Down Expand Up @@ -48,7 +48,15 @@ aws sso login --profile=<your-profile-name>
export AWS_PROFILE=your-profile-name
```

**Option D: Bedrock API keys**
**Option D: AWS Management Console credentials**

```bash theme={null}
aws login
```

[Learn more](https://docs.aws.amazon.com/signin/latest/userguide/command-line-sign-in.html) about `aws login`.

Comment on lines +51 to +58
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

aws login command AWS CLI credential method

💡 Result:

Short answer: there is no single built‑in "aws login" command for all credential types. Common AWS CLI credential methods:

  • Static keys via aws configure (stores aws_access_key_id / aws_secret_access_key). [1]
  • IAM Identity Center (SSO): run aws configure sso to create a profile, then aws sso login --profile to fetch cached temporary credentials. [2]
  • Environment variables (AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY / AWS_SESSION_TOKEN). [1][3]
  • Assume-role / STS (aws sts assume-role or profiles that source a role). [3]
  • Credential_process / external providers (custom command that returns JSON credentials). [1][3]
  • On‑host providers: EC2 instance profile, ECS task credentials, or container metadata. [3]
  • Third‑party helpers (aws-vault, aws-okta, etc.) which wrap one of the above.

If you tell me which authentication flow you need (SSO, long‑term keys, role assumption, EC2/ECS, or a tooling helper), I’ll give the exact commands and example config.

Sources: [1] AWS CLI configure docs; [2] AWS CLI IAM Identity Center (SSO) docs; [3] AWS CLI config/credentials file and provider documentation.


Remove or correct the invalid aws login command.

aws login is not a valid AWS CLI command. AWS CLI supports specific credential methods like aws configure for static keys, aws sso login --profile <profile-name> for IAM Identity Center (SSO), or environment variables. The documentation link references AWS signin, which may not validate this specific command. Replace this with a supported credential method or remove Option D if it doesn't match an actual AWS credential approach Claude Code uses.

🤖 Prompt for AI Agents
In skills/working-with-claude-code/references/amazon-bedrock.md around lines 51
to 58, the example shows the invalid command `aws login`; replace or remove this
to avoid misinformation. Update Option D to present a valid credential method
such as using `aws configure` for static keys, `aws sso login --profile
<profile-name>` for IAM Identity Center, or explain using environment variables,
and adjust the accompanying link/text to reference the matching AWS CLI
credential documentation; if none of these apply to Claude Code, remove Option D
entirely.

**Option E: Bedrock API keys**

```bash theme={null}
export AWS_BEARER_TOKEN_BEDROCK=your-bedrock-api-key
Expand All @@ -58,7 +66,7 @@ Bedrock API keys provide a simpler authentication method without needing full AW

#### Advanced credential configuration

Claude Code supports automatic credential refresh for AWS SSO and corporate identity providers. Add these settings to your Claude Code settings file (see [Settings](/en/docs/claude-code/settings) for file locations).
Claude Code supports automatic credential refresh for AWS SSO and corporate identity providers. Add these settings to your Claude Code settings file (see [Settings](/en/settings) for file locations).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify internal documentation links exist and sections/anchors are correct

# Check for Settings page
echo "=== Checking for settings.md page ==="
fd -t f "settings.md" 

# Check for VS Code page
echo "=== Checking for vs-code.md page ==="
fd -t f "vs-code.md" 

# Search for the specific section about third-party providers
echo "=== Searching for third-party providers section ==="
rg -n "using-third-party-providers|Using Third-Party Providers|Third-Party Providers" --type md -i

# Check the actual file structure under /en/ paths
echo "=== Listing markdown files under en directory ==="
find . -path "*/en/*.md" -type f | head -20

Repository: obra/superpowers-developing-for-claude-code

Length of output: 1740


🏁 Script executed:

#!/bin/bash
# Check the exact section heading and context around the third-party providers section
sed -n '45,60p' skills/working-with-claude-code/references/vs-code.md

Repository: obra/superpowers-developing-for-claude-code

Length of output: 690


🏁 Script executed:

#!/bin/bash
# Search for explicit anchor definitions (various markdown anchor formats)
echo "=== Checking for explicit anchors in vs-code.md ==="
rg -n "^\{#|<!-- ?#|id=|anchor=" skills/working-with-claude-code/references/vs-code.md

# Also check for the specific anchor text from the link
echo "=== Searching for the anchor text used in the link ==="
rg -n "using-third-party-providers-vertex-and-bedrock" skills/working-with-claude-code/references/vs-code.md

# Look at broader context around the section
echo "=== Broader context (lines 40-75) ==="
sed -n '40,75p' skills/working-with-claude-code/references/vs-code.md

Repository: obra/superpowers-developing-for-claude-code

Length of output: 1587


Fix incorrect anchor in VS Code link.

The link at line 113 references /en/vs-code#using-third-party-providers-vertex-and-bedrock, but this anchor does not exist in vs-code.md. The actual section heading is "#### Third-party providers and gateways" which generates the anchor #third-party-providers-and-gateways. Update the link to /en/vs-code#third-party-providers-and-gateways.

The files for /en/settings and /en/vs-code exist and are correct.

🤖 Prompt for AI Agents
In skills/working-with-claude-code/references/amazon-bedrock.md around line 69,
the VS Code link uses a nonexistent anchor
(/en/vs-code#using-third-party-providers-vertex-and-bedrock); update the link to
use the correct anchor /en/vs-code#third-party-providers-and-gateways so it
points to the "Third-party providers and gateways" section, ensuring the link
target is exactly /en/vs-code#third-party-providers-and-gateways.


When Claude Code detects that your AWS credentials are expired (either locally based on their timestamp or when Bedrock returns a credential error), it will automatically run your configured `awsAuthRefresh` and/or `awsCredentialExport` commands to obtain new credentials before retrying the request.

Expand All @@ -75,9 +83,9 @@ When Claude Code detects that your AWS credentials are expired (either locally b

##### Configuration settings explained

**`awsAuthRefresh`**: Use this for commands that modify the `.aws` directory (e.g., updating credentials, SSO cache, or config files). Output is shown to the user (but user input is not supported), making it suitable for browser-based authentication flows where the CLI displays a code to enter in the browser.
**`awsAuthRefresh`**: Use this for commands that modify the `.aws` directory, such as updating credentials, SSO cache, or config files. The command's output is displayed to the user, but interactive input isn't supported. This works well for browser-based SSO flows where the CLI displays a URL or code and you complete authentication in the browser.

**`awsCredentialExport`**: Only use this if you cannot modify `.aws` and must directly return credentials. Output is captured silently (not shown to the user). The command must output JSON in this format:
**`awsCredentialExport`**: Only use this if you can't modify `.aws` and must directly return credentials. Output is captured silently and not shown to the user. The command must output JSON in this format:

```json theme={null}
{
Expand Down Expand Up @@ -106,7 +114,7 @@ When enabling Bedrock for Claude Code, keep the following in mind:

* `AWS_REGION` is a required environment variable. Claude Code does not read from the `.aws` config file for this setting.
* When using Bedrock, the `/login` and `/logout` commands are disabled since authentication is handled through AWS credentials.
* You can use settings files for environment variables like `AWS_PROFILE` that you don't want to leak to other processes. See [Settings](/en/docs/claude-code/settings) for more information.
* You can use settings files for environment variables like `AWS_PROFILE` that you don't want to leak to other processes. See [Settings](/en/settings) for more information.

### 4. Model configuration

Expand All @@ -118,7 +126,7 @@ Claude Code uses these default models for Bedrock:
| Small/fast model | `us.anthropic.claude-haiku-4-5-20251001-v1:0` |

<Note>
For Bedrock users, Claude Code will not automatically upgrade from Haiku 3.5 to Haiku 4.5. To manually switch to a newer Haiku model, set the `ANTHROPIC_DEFAULT_HAIKU_MODEL` environment variable to the full model name (e.g., `us.anthropic.claude-haiku-4-5-20251001-v1:0`).
For Bedrock users, Claude Code won't automatically upgrade from Haiku 3.5 to Haiku 4.5. To manually switch to a newer Haiku model, set the `ANTHROPIC_DEFAULT_HAIKU_MODEL` environment variable to the full model name (for example, `us.anthropic.claude-haiku-4-5-20251001-v1:0`).
</Note>

To customize models, use one of these methods:
Expand All @@ -135,13 +143,11 @@ export ANTHROPIC_MODEL='arn:aws:bedrock:us-east-2:your-account-id:application-in
export DISABLE_PROMPT_CACHING=1
```

<Note>
[Prompt caching](/en/docs/build-with-claude/prompt-caching) may not be available in all regions
</Note>
<Note>[Prompt caching](https://docs.claude.com/en/docs/build-with-claude/prompt-caching) may not be available in all regions.</Note>

### 5. Output token configuration

When using Claude Code with Amazon Bedrock, we recommend the following token settings:
These are the recommended token settings for Claude Code with Amazon Bedrock:

```bash theme={null}
# Recommended output token settings for Bedrock
Expand All @@ -151,7 +157,7 @@ export MAX_THINKING_TOKENS=1024

**Why these values:**

* **`CLAUDE_CODE_MAX_OUTPUT_TOKENS=4096`**: Bedrock's burndown throttling logic sets a minimum of 4096 tokens as the max\_token penalty. Setting this lower won't reduce costs but may cut off long tool uses, causing the Claude Code agent loop to fail persistently. Claude Code typically uses less than 4096 output tokens without extended thinking, but may need this headroom for tasks involving significant file creation or Write tool usage.
* **`CLAUDE_CODE_MAX_OUTPUT_TOKENS=4096`**: Bedrock's burndown throttling logic sets a minimum of 4096 tokens as the `max_token` penalty. Setting this lower won't reduce costs but may cut off long tool uses, causing the Claude Code agent loop to fail persistently. Claude Code typically uses less than 4096 output tokens without extended thinking, but may need this headroom for tasks involving significant file creation or Write tool usage.

* **`MAX_THINKING_TOKENS=1024`**: This provides space for extended thinking without cutting off tool use responses, while still maintaining focused reasoning chains. This balance helps prevent trajectory changes that aren't always helpful for coding tasks specifically.

Expand All @@ -164,6 +170,7 @@ Create an IAM policy with the required permissions for Claude Code:
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AllowModelAndInferenceProfileAccess",
"Effect": "Allow",
"Action": [
"bedrock:InvokeModel",
Expand All @@ -172,8 +179,23 @@ Create an IAM policy with the required permissions for Claude Code:
],
"Resource": [
"arn:aws:bedrock:*:*:inference-profile/*",
"arn:aws:bedrock:*:*:application-inference-profile/*"
"arn:aws:bedrock:*:*:application-inference-profile/*",
"arn:aws:bedrock:*:*:foundation-model/*"
]
},
{
"Sid": "AllowMarketplaceSubscription",
"Effect": "Allow",
"Action": [
"aws-marketplace:ViewSubscriptions",
"aws-marketplace:Subscribe"
],
"Resource": "*",
"Condition": {
"StringEquals": {
"aws:CalledViaLast": "bedrock.amazonaws.com"
}
}
}
]
}
Expand Down Expand Up @@ -207,3 +229,8 @@ Claude Code uses the Bedrock [Invoke API](https://docs.aws.amazon.com/bedrock/la
* [Bedrock pricing](https://aws.amazon.com/bedrock/pricing/)
* [Bedrock inference profiles](https://docs.aws.amazon.com/bedrock/latest/userguide/inference-profiles-support.html)
* [Claude Code on Amazon Bedrock: Quick Setup Guide](https://community.aws/content/2tXkZKrZzlrlu0KfH8gST5Dkppq/claude-code-on-amazon-bedrock-quick-setup-guide)- [Claude Code Monitoring Implementation (Bedrock)](https://github.com/aws-solutions-library-samples/guidance-for-claude-code-with-amazon-bedrock/blob/main/assets/docs/MONITORING.md)


---

> To find navigation and other pages in this documentation, fetch the llms.txt file at: https://code.claude.com/docs/llms.txt
9 changes: 7 additions & 2 deletions skills/working-with-claude-code/references/analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,5 +83,10 @@ Tool acceptance rates and code metrics help you:

## Related resources

* [Monitoring usage with OpenTelemetry](/en/docs/claude-code/monitoring-usage) for custom metrics and alerting
* [Identity and access management](/en/docs/claude-code/iam) for role configuration
* [Monitoring usage with OpenTelemetry](/en/monitoring-usage) for custom metrics and alerting
* [Identity and access management](/en/iam) for role configuration


---

> To find navigation and other pages in this documentation, fetch the llms.txt file at: https://code.claude.com/docs/llms.txt
11 changes: 8 additions & 3 deletions skills/working-with-claude-code/references/checkpointing.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,11 @@ Checkpoints are designed for quick, session-level recovery. For permanent versio

## See also

* [Interactive mode](/en/docs/claude-code/interactive-mode) - Keyboard shortcuts and session controls
* [Slash commands](/en/docs/claude-code/slash-commands) - Accessing checkpoints using `/rewind`
* [CLI reference](/en/docs/claude-code/cli-reference) - Command-line options
* [Interactive mode](/en/interactive-mode) - Keyboard shortcuts and session controls
* [Slash commands](/en/slash-commands) - Accessing checkpoints using `/rewind`
* [CLI reference](/en/cli-reference) - Command-line options


---

> To find navigation and other pages in this documentation, fetch the llms.txt file at: https://code.claude.com/docs/llms.txt
Loading