Claude Code overview - Anthropic =============== [Anthropic home page](https://docs.anthropic.com/) English Search... * [Research](https://www.anthropic.com/research) * [News](https://www.anthropic.com/news) * [Go to claude.ai](https://claude.ai/) * [Go to claude.ai](https://claude.ai/) Search... Navigation Claude Code Claude Code overview [Welcome](https://docs.anthropic.com/en/home)[User Guides](https://docs.anthropic.com/en/docs/welcome)[API Reference](https://docs.anthropic.com/en/api/getting-started)[Prompt Library](https://docs.anthropic.com/en/prompt-library/library)[Release Notes](https://docs.anthropic.com/en/release-notes/overview) * [Developer Console](https://console.anthropic.com/) * [Developer Discord](https://www.anthropic.com/discord) * [Support](https://support.anthropic.com/) ##### Get started * [Overview](https://docs.anthropic.com/en/docs/welcome) * [Initial setup](https://docs.anthropic.com/en/docs/initial-setup) * [Intro to Claude](https://docs.anthropic.com/en/docs/intro-to-claude) ##### Learn about Claude * Use cases * Models & pricing * [Security and compliance](https://trust.anthropic.com/) ##### Build with Claude * [Define success criteria](https://docs.anthropic.com/en/docs/build-with-claude/define-success) * [Develop test cases](https://docs.anthropic.com/en/docs/build-with-claude/develop-tests) * [Context windows](https://docs.anthropic.com/en/docs/build-with-claude/context-windows) * [Vision](https://docs.anthropic.com/en/docs/build-with-claude/vision) * Prompt engineering * [Extended thinking](https://docs.anthropic.com/en/docs/build-with-claude/extended-thinking) * [Multilingual support](https://docs.anthropic.com/en/docs/build-with-claude/multilingual-support) * Tool use (function calling) * [Prompt caching](https://docs.anthropic.com/en/docs/build-with-claude/prompt-caching) * [PDF support](https://docs.anthropic.com/en/docs/build-with-claude/pdf-support) * [Citations](https://docs.anthropic.com/en/docs/build-with-claude/citations) * [Token counting](https://docs.anthropic.com/en/docs/build-with-claude/token-counting) * [Batch processing](https://docs.anthropic.com/en/docs/build-with-claude/batch-processing) * [Embeddings](https://docs.anthropic.com/en/docs/build-with-claude/embeddings) ##### Agents and tools * Claude Code * [Overview](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview) * [Claude Code tutorials](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/tutorials) * [Troubleshooting](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/troubleshooting) * [Computer use (beta)](https://docs.anthropic.com/en/docs/agents-and-tools/computer-use) * [Model Context Protocol (MCP)](https://docs.anthropic.com/en/docs/agents-and-tools/mcp) * [Google Sheets add-on](https://docs.anthropic.com/en/docs/agents-and-tools/claude-for-sheets) ##### Test and evaluate * Strengthen guardrails * [Using the Evaluation Tool](https://docs.anthropic.com/en/docs/test-and-evaluate/eval-tool) ##### Administration * [Admin API](https://docs.anthropic.com/en/docs/administration/administration-api) ##### Resources * [Glossary](https://docs.anthropic.com/en/docs/resources/glossary) * [Model deprecations](https://docs.anthropic.com/en/docs/resources/model-deprecations) * [System status](https://status.anthropic.com/) * [Claude 3 model card](https://assets.anthropic.com/m/61e7d27f8c8f5919/original/Claude-3-Model-Card.pdf) * [Claude 3.7 system card](https://anthropic.com/claude-3-7-sonnet-system-card) * [Anthropic Cookbook](https://github.com/anthropics/anthropic-cookbook) * [Anthropic Courses](https://github.com/anthropics/courses) * [API features](https://docs.anthropic.com/en/docs/resources/api-features) ##### Legal center * [Anthropic Privacy Policy](https://www.anthropic.com/legal/privacy) Claude Code Claude Code overview ==================== Learn about Claude Code, an agentic coding tool made by Anthropic. Currently in beta as a research preview. Install [NodeJS 18+](https://nodejs.org/en/download), then run: ```sh npm install -g @anthropic-ai/claude-code ``` Do NOT use `sudo npm install -g` as this can lead to permission issues and security risks. If you encounter permission errors, see [configure Claude Code](https://docs.anthropic.com/_sites/docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#configure-claude-code) for recommended solutions. Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster through natural language commands. By integrating directly with your development environment, Claude Code streamlines your workflow without requiring additional servers or complex setup. Claude Code’s key capabilities include: * Editing files and fixing bugs across your codebase * Answering questions about your code’s architecture and logic * Executing and fixing tests, linting, and other commands * Searching through git history, resolving merge conflicts, and creating commits and PRs **Research preview** Code is in beta as a research preview. We’re gathering developer feedback on AI collaboration preferences, which workflows benefit most from AI assistance, and how to improve the agent experience. This early version will evolve based on user feedback. We plan to enhance tool execution reliability, support for long-running commands, terminal rendering, and Claude’s self-knowledge of its capabilities in the coming weeks. Report bugs directly with the `/bug` command or through our [GitHub repository](https://github.com/anthropics/claude-code). * * * [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#before-you-begin) Before you begin ------------------------------------------------------------------------------------------------------------------ ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#check-system-requirements) Check system requirements * **Operating Systems**: macOS 10.15+, Ubuntu 20.04+/Debian 10+, or Windows via WSL * **Hardware**: 4GB RAM minimum * **Software**: * Node.js 18+ * [git](https://git-scm.com/downloads) 2.23+ (optional) * [GitHub](https://cli.github.com/) or [GitLab](https://gitlab.com/gitlab-org/cli) CLI for PR workflows (optional) * [ripgrep](https://github.com/BurntSushi/ripgrep?tab=readme-ov-file#installation) (rg) for enhanced file search (optional) * **Network**: Internet connection required for authentication and AI processing * **Location**: Available only in [supported countries](https://www.anthropic.com/supported-countries) **Troubleshooting WSL installation** Currently, Claude Code does not run directly in Windows, and instead requires WSL. If you encounter issues in WSL: 1. **OS/platform detection issues**: If you receive an error during installation, WSL may be using Windows `npm`. Try: * Run `npm config set os linux` before installation * Install with `npm install -g @anthropic-ai/claude-code --force --no-os-check` (Do NOT use `sudo`) 2. **Node not found errors**: If you see `exec: node: not found` when running `claude`, your WSL environment may be using a Windows installation of Node.js. You can confirm this with `which npm` and `which node`, which should point to Linux paths starting with `/usr/` rather than `/mnt/c/`. To fix this, try installing Node via your Linux distribution’s package manager or via [`nvm`](https://github.com/nvm-sh/nvm). ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#install-and-authenticate) Install and authenticate 1 Install Claude Code Run in your terminal: `npm install -g @anthropic-ai/claude-code` Do NOT use `sudo npm install -g` as this can lead to permission issues and security risks. If you encounter permission errors, see [configure Claude Code](https://docs.anthropic.com/_sites/docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#configure-claude-code) for recommended solutions. 2 Navigate to your project `cd your-project-directory` 3 Start Claude Code Run `claude` to launch 4 Complete authentication Follow the one-time OAuth process with your Console account. You’ll need active billing at [console.anthropic.com](https://console.anthropic.com/). * * * [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#core-features-and-workflows) Core features and workflows -------------------------------------------------------------------------------------------------------------------------------- Claude Code operates directly in your terminal, understanding your project context and taking real actions. No need to manually add files to context - Claude will explore your codebase as needed. Claude Code uses `claude-3-7-sonnet-20250219` by default. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#security-and-privacy-by-design) Security and privacy by design Your code’s security is paramount. Claude Code’s architecture ensures: * **Direct API connection**: Your queries go straight to Anthropic’s API without intermediate servers * **Works where you work**: Operates directly in your terminal * **Understands context**: Maintains awareness of your entire project structure * **Takes action**: Performs real operations like editing files and creating commits ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#from-questions-to-solutions-in-seconds) From questions to solutions in seconds ```bash # Ask questions about your codebase claude > how does our authentication system work? # Create a commit with one command claude commit # Fix issues across multiple files claude "fix the type errors in the auth module" ``` * * * ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#initialize-your-project) Initialize your project For first-time users, we recommend: 1. Start Claude Code with `claude` 2. Try a simple command like `summarize this project` 3. Generate a CLAUDE.md project guide with `/init` 4. Ask Claude to commit the generated CLAUDE.md file to your repository [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#use-claude-code-for-common-tasks) Use Claude Code for common tasks -------------------------------------------------------------------------------------------------------------------------------- Claude Code operates directly in your terminal, understanding your project context and taking real actions. No need to manually add files to context - Claude will explore your codebase as needed. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#understand-unfamiliar-code) Understand unfamiliar code ``` > what does the payment processing system do? > find where user permissions are checked > explain how the caching layer works ``` ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#automate-git-operations) Automate Git operations ``` > commit my changes > create a pr > which commit added tests for markdown back in December? > rebase on main and resolve any merge conflicts ``` ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#edit-code-intelligently) Edit code intelligently ``` > add input validation to the signup form > refactor the logger to use the new API > fix the race condition in the worker queue ``` ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#test-and-debug-your-code) Test and debug your code ``` > run tests for the auth module and fix failures > find and fix security vulnerabilities > explain why this test is failing ``` ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#encourage-deeper-thinking) Encourage deeper thinking For complex problems, explicitly ask Claude to think more deeply: ``` > think about how we should architect the new payment service > think hard about the edge cases in our authentication flow ``` Claude Code will show when Claude (3.7 Sonnet) is using extended thinking. You can proactively prompt Claude to “think” or “think deeply” for more planning-intensive tasks. We suggest that you first tell Claude about your task and let it gather context from your project. Then, ask it to “think” to create a plan. Claude will think more based on the words you use. For example, “think hard” will trigger more extended thinking than saying “think” alone. For more tips, see [Extended thinking tips](https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/extended-thinking-tips). ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#automate-ci-and-infra-workflows) Automate CI and infra workflows Claude Code comes with a non-interactive mode for headless execution. This is especially useful for running Claude Code in non-interactive contexts like scripts, pipelines, and Github Actions. Use `--print` (`-p`) to run Claude in non-interactive mode. In this mode, you can set the `ANTHROPIC_API_KEY` environment variable to provide a custom API key. Non-interactive mode is especially useful when you pre-configure the set of commands Claude is allowed to use: ```sh export ANTHROPIC_API_KEY=sk_... claude -p "update the README with the latest changes" --allowedTools "Bash(git diff:*)" "Bash(git log:*)" Edit ``` * * * [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#control-claude-code-with-commands) Control Claude Code with commands -------------------------------------------------------------------------------------------------------------------------------- ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#cli-commands) CLI commands | Command | Description | Example | | --- | --- | --- | | `claude` | Start interactive REPL | `claude` | | `claude "query"` | Start REPL with initial prompt | `claude "explain this project"` | | `claude -p "query"` | Run one-off query, then exit | `claude -p "explain this function"` | | `cat file | claude -p "query"` | Process piped content | `cat logs.txt | claude -p "explain"` | | `claude config` | Configure settings | `claude config set --global theme dark` | | `claude update` | Update to latest version | `claude update` | | `claude mcp` | Configure Model Context Protocol servers | [See MCP section in tutorials](https://docs.anthropic.com/en/docs/agents/claude-code/tutorials#set-up-model-context-protocol-mcp) | **CLI flags**: * `--print` (`-p`): Print response without interactive mode * `--json`: Return JSON output in `--print` mode, useful for scripting and automation * `--verbose`: Enable verbose logging, shows full turn-by-turn output (helpful for debugging in both print and interactive modes) * `--dangerously-skip-permissions`: Skip permission prompts ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#slash-commands) Slash commands Control Claude’s behavior within a session: | Command | Purpose | | --- | --- | | `/bug` | Report bugs (sends conversation to Anthropic) | | `/clear` | Clear conversation history | | `/compact [instructions]` | Compact conversation with optional focus instructions | | `/config` | View/modify configuration | | `/cost` | Show token usage statistics | | `/doctor` | Checks the health of your Claude Code installation | | `/help` | Get usage help | | `/init` | Initialize project with CLAUDE.md guide | | `/login` | Switch Anthropic accounts | | `/logout` | Sign out from your Anthropic account | | `/memory` | Edit CLAUDE.md memory files | | `/pr_comments` | View pull request comments | | `/review` | Request code review | | `/terminal-setup` | Install Shift+Enter key binding for newlines (iTerm2 and VSCode only) | | `/vim` | Enter vim mode for alternating insert and command modes | [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#manage-claudes-memory) Manage Claude’s memory ----------------------------------------------------------------------------------------------------------------------------- Claude Code can remember your preferences across sessions, like style guidelines and common commands in your workflow. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#determine-memory-type) Determine memory type Claude Code offers three memory locations, each serving a different purpose: | Memory Type | Location | Purpose | Use Case Examples | | --- | --- | --- | --- | | **Project memory** | `./CLAUDE.md` | Team-shared conventions and knowledge | Project architecture, coding standards, common workflows | | **Project memory (local)** | `./CLAUDE.local.md` | Personal project-specific preferences | Your sandbox URLs, preferred test data | | **User memory** | `~/.claude/CLAUDE.md` | Global personal preferences | Code styling preferences, personal tooling shortcuts | All memory files are automatically loaded into Claude Code’s context when launched. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#how-claude-looks-up-memories) How Claude looks up memories Claude Code reads memories recursively: starting in the cwd, Claude Code recurses up to _/_ and reads any CLAUDE.md or CLAUDE.local.md files it finds. This is especially convenient when working in large repositories where you run Claude Code in _foo/bar/_, and have memories in both _foo/CLAUDE.md_ and _foo/bar/CLAUDE.md_. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#quickly-add-memories-with-the-shortcut) Quickly add memories with the `#` shortcut The fastest way to add a memory is to start your input with the `#` character: ``` # Always use descriptive variable names ``` You’ll be prompted to select which memory file to store this in. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#directly-edit-memories-with-memory) Directly edit memories with `/memory` Use the `/memory` slash command during a session to open any memory file in your system editor for more extensive additions or organization. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#memory-best-practices) Memory best practices * **Be specific**: “Use 2-space indentation” is better than “Format code properly”. * **Use structure to organize**: Format each individual memory as a bullet point and group related memories under descriptive markdown headings. * **Review periodically**: Update memories as your project evolves to ensure Claude is always using the most up to date information and context. [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#manage-permissions-and-security) Manage permissions and security -------------------------------------------------------------------------------------------------------------------------------- Claude Code uses a tiered permission system to balance power and safety: | Tool Type | Example | Approval Required | ”Yes, don’t ask again” Behavior | | --- | --- | --- | --- | | Read-only | File reads, LS, Grep | No | N/A | | Bash Commands | Shell execution | Yes | Permanently per project directory and command | | File Modification | Edit/write files | Yes | Until session end | ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#tools-available-to-claude) Tools available to Claude Claude Code has access to a set of powerful tools that help it understand and modify your codebase: | Tool | Description | Permission Required | | --- | --- | --- | | **AgentTool** | Runs a sub-agent to handle complex, multi-step tasks | No | | **BashTool** | Executes shell commands in your environment | Yes | | **GlobTool** | Finds files based on pattern matching | No | | **GrepTool** | Searches for patterns in file contents | No | | **LSTool** | Lists files and directories | No | | **FileReadTool** | Reads the contents of files | No | | **FileEditTool** | Makes targeted edits to specific files | Yes | | **FileWriteTool** | Creates or overwrites files | Yes | | **NotebookReadTool** | Reads and displays Jupyter notebook contents | No | | **NotebookEditTool** | Modifies Jupyter notebook cells | Yes | ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#permission-rules) Permission rules You can manage Claude Code’s allowed tools with `/allowed-tools`. Your personal project permission settings are saved in your global Claude config (in `~/.claude.json`). Shared project permissions are loaded from `.claude/settings.json` when Claude Code is launched. These settings are shared across everyone working with this code so that each user doesn’t have to configure commonly used safe tools. Example .claude/settings.json ```JSON { "permissions": { "allow": [ "Bash(npm run lint)", "Bash(npm run test:*)" ] } } ``` Permission rules use the format: `Tool(optional-specifier)` For example, adding `WebFetchTool` to the list of allow rules would allow any use of the web fetch tool without requiring user approval. Some tools have more fine-grained controls to allow specific tool invocations without user approval. See the table below for examples. MCP tool names follow the format: `mcp__server_name__tool_name`, where: * `server_name` is the name of the MCP server as configured in Claude Code * `tool_name` is the specific tool provided by that server | Rule | Description | | --- | --- | | **Bash(npm run build)** | Matches the exact Bash command `npm run build`. | | **Bash(npm run test:\*)** | Matches Bash commands starting with `npm run test`. See note below about command separator handling. | | **mcp\_\_puppeteer\_\_puppeteer\_navigate** | Matches the `puppeteer_navigate` tool from the `puppeteer` MCP server. | | **WebFetchTool(domain:example.com)** | Matches fetch requests to example.com | Claude Code is aware of command separators (like `&&`) so a prefix match rule like `Bash(safe-cmd:*)` won’t give it permission to run the command `safe-cmd && other-cmd` ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#protect-against-prompt-injection) Protect against prompt injection Prompt injection is a technique where an attacker attempts to override or manipulate an AI assistant’s instructions by inserting malicious text. Claude Code includes several safeguards against these attacks: * **Permission system**: Sensitive operations require explicit approval * **Context-aware analysis**: Detects potentially harmful instructions by analyzing the full request * **Input sanitization**: Prevents command injection by processing user inputs * **Command blocklist**: Blocks risky commands that fetch arbitrary content from the web like `curl` and `wget` **Best practices for working with untrusted content**: 1. Review suggested commands before approval 2. Avoid piping untrusted content directly to Claude 3. Verify proposed changes to critical files 4. Report suspicious behavior with `/bug` While these protections significantly reduce risk, no system is completely immune to all attacks. Always maintain good security practices when working with any AI tool. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#configure-network-access) Configure network access Claude Code requires access to: * api.anthropic.com * statsig.anthropic.com * sentry.io Allowlist these URLs when using Claude Code in containerized environments. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#environment-variables) Environment variables Claude Code supports the following environment variables to control its behavior: | Variable | Purpose | | --- | --- | | `DISABLE_AUTOUPDATER` | Set to `1` to disable the automatic updater | | `DISABLE_BUG_COMMAND` | Set to `1` to disable the `/bug` command | | `DISABLE_COST_WARNINGS` | Set to `1` to disable cost warning messages | | `HTTP_PROXY` | Specify HTTP proxy server for network connections | | `HTTPS_PROXY` | Specify HTTPS proxy server for network connections | | `MCP_TIMEOUT` | Timeout in milliseconds for MCP server startup | | `MCP_TOOL_TIMEOUT` | Timeout in milliseconds for MCP tool execution | * * * [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#configure-claude-code) Configure Claude Code ---------------------------------------------------------------------------------------------------------------------------- Configure Claude Code by running `claude config` in your terminal, or the `/config` command when using the interactive REPL. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#configuration-options) Configuration options Claude Code supports global and project-level configuration. To manage your configurations, use the following commands: * List settings: `claude config list` * See a setting: `claude config get <key>` * Change a setting: `claude config set <key> <value>` * Push to a setting (for lists): `claude config add <key> <value>` * Remove from a setting (for lists): `claude config remove <key> <value>` By default `config` changes your project configuration. To manage your global configuration, use the `--global` (or `-g`) flag. #### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#global-configuration) Global configuration To set a global configuration, use `claude config set -g <key> <value>`: | Key | Value | Description | | --- | --- | --- | | `autoUpdaterStatus` | `disabled` or `enabled` | Enable or disable the auto-updater (default: `enabled`) | | `env` | JSON (eg. `'{"FOO": "bar"}'`) | Environment variables that will be applied to every session | | `preferredNotifChannel` | `iterm2`, `iterm2_with_bell`, `terminal_bell`, or `notifications_disabled` | Where you want to receive notifications (default: `iterm2`) | | `theme` | `dark`, `light`, `light-daltonized`, or `dark-daltonized` | Color theme | | `verbose` | `true` or `false` | Whether to show full bash and command outputs (default: `false`) | ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#auto-updater-permission-options) Auto-updater permission options When Claude Code detects that it doesn’t have sufficient permissions to write to your global npm prefix directory (required for automatic updates), you’ll see a warning that points to this documentation page. For detailed solutions to auto-updater issues, see the [troubleshooting guide](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/troubleshooting#auto-updater-issues). #### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#recommended-create-a-new-user-writable-npm-prefix) Recommended: Create a new user-writable npm prefix ```bash # First, save a list of your existing global packages for later migration npm list -g --depth=0 > ~/npm-global-packages.txt # Create a directory for your global packages mkdir -p ~/.npm-global # Configure npm to use the new directory path npm config set prefix ~/.npm-global # Note: Replace ~/.bashrc with ~/.zshrc, ~/.profile, or other appropriate file for your shell echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc # Apply the new PATH setting source ~/.bashrc # Now reinstall Claude Code in the new location npm install -g @anthropic-ai/claude-code # Optional: Reinstall your previous global packages in the new location # Look at ~/npm-global-packages.txt and install packages you want to keep # npm install -g package1 package2 package3... ``` **Why we recommend this option:** * Avoids modifying system directory permissions * Creates a clean, dedicated location for your global npm packages * Follows security best practices Since Claude Code is actively developing, we recommend setting up auto-updates using the recommended option above. #### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#disabling-the-auto-updater) Disabling the auto-updater If you prefer to disable the auto-updater instead of fixing permissions, you can use: ```bash claude config set -g autoUpdaterStatus disabled ``` #### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#project-configuration) Project configuration Manage project configuration with `claude config set <key> <value>` (without the `-g` flag): | Key | Value | Description | | --- | --- | --- | | `allowedTools` | array of tools | Which tools can run without manual approval | | `ignorePatterns` | array of glob strings | Which files/directories are ignored when using tools | For example: ```sh # Let npm test to run without approval claude config add allowedTools "Bash(npm test)" # Let npm test and any of its sub-commands to run without approval claude config add allowedTools "Bash(npm test:*)" # Instruct Claude to ignore node_modules claude config add ignorePatterns node_modules claude config add ignorePatterns "node_modules/**" ``` See [Permission rules](https://docs.anthropic.com/_sites/docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#permission-rules) for the `allowedTools` rule format. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#optimize-your-terminal-setup) Optimize your terminal setup Claude Code works best when your terminal is properly configured. Follow these guidelines to optimize your experience. **Supported shells**: * Bash * Zsh * Fish #### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#themes-and-appearance) Themes and appearance Claude cannot control the theme of your terminal. That’s handled by your terminal application. You can match Claude Code’s theme to your terminal during onboarding or any time via the `/config` command #### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#line-breaks) Line breaks You have several options for entering linebreaks into Claude Code: * **Quick escape**: Type `\` followed by Enter to create a newline * **Keyboard shortcut**: Press Option+Enter (Meta+Enter) with proper configuration To set up Option+Enter in your terminal: **For Mac Terminal.app:** 1. Open Settings → Profiles → Keyboard 2. Check “Use Option as Meta Key” **For iTerm2 and VSCode terminal:** 1. Open Settings → Profiles → Keys 2. Under General, set Left/Right Option key to “Esc+” **Tip for iTerm2 and VSCode users**: Run `/terminal-setup` within Claude Code to automatically configure Shift+Enter as a more intuitive alternative. #### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#notification-setup) Notification setup Never miss when Claude completes a task with proper notification configuration: ##### Terminal bell notifications Enable sound alerts when tasks complete: ```sh claude config set --global preferredNotifChannel terminal_bell ``` **For macOS users**: Don’t forget to enable notification permissions in System Settings → Notifications → \[Your Terminal App\]. ##### iTerm 2 system notifications For iTerm 2 alerts when tasks complete: 1. Open iTerm 2 Preferences 2. Navigate to Profiles → Terminal 3. Enable “Silence bell” and “Send notification when idle” 4. Set your preferred notification delay Note that these notifications are specific to iTerm 2 and not available in the default macOS Terminal. #### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#handling-large-inputs) Handling large inputs When working with extensive code or long instructions: * **Avoid direct pasting**: Claude Code may struggle with very long pasted content * **Use file-based workflows**: Write content to a file and ask Claude to read it * **Be aware of VS Code limitations**: The VS Code terminal is particularly prone to truncating long pastes #### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#vim-mode) Vim Mode Claude Code supports a subset of Vim keybindings that can be enabled with `/vim` or configured via `/config`. The supported subset includes: * Mode switching: `Esc` (to NORMAL), `i`/`I`, `a`/`A`, `o`/`O` (to INSERT) * Navigation: `h`/`j`/`k`/`l`, `w`/`e`/`b`, `0`/`$`/`^`, `gg`/`G` * Editing: `x`, `dw`/`de`/`db`/`dd`/`D`, `cw`/`ce`/`cb`/`cc`/`C`, `.` (repeat) * * * [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#manage-costs-effectively) Manage costs effectively -------------------------------------------------------------------------------------------------------------------------------- Claude Code consumes tokens for each interaction. The average cost is $6 per developer per day, with daily costs remaining below $12 for 90% of users. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#track-your-costs) Track your costs * Use `/cost` to see current session usage * Check [historical usage](https://support.anthropic.com/en/articles/9534590-cost-and-usage-reporting-in-console) in the Anthropic Console. Note: Users need Admin or Billing roles to view Cost tab * Set [workspace spend limits](https://support.anthropic.com/en/articles/9796807-creating-and-managing-workspaces) for the Claude Code workspace. Note: Users need Admin role to set spend limits. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#reduce-token-usage) Reduce token usage * **Compact conversations:** * Claude uses auto-compact by default when context exceeds 95% capacity * Toggle auto-compact: Run `/config` and navigate to “Auto-compact enabled” * Use `/compact` manually when context gets large * Add custom instructions: `/compact Focus on code samples and API usage` * Customize compaction by adding to CLAUDE.md: ```markdown # Summary instructions When you are using compact, please focus on test output and code changes ``` * **Write specific queries:** Avoid vague requests that trigger unnecessary scanning * **Break down complex tasks:** Split large tasks into focused interactions * **Clear history between tasks:** Use `/clear` to reset context Costs can vary significantly based on: * Size of codebase being analyzed * Complexity of queries * Number of files being searched or modified * Length of conversation history * Frequency of compacting conversations For team deployments, we recommend starting with a small pilot group to establish usage patterns before wider rollout. * * * [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#model-configuration) Model configuration ------------------------------------------------------------------------------------------------------------------------ By default, Claude Code uses `claude-3-7-sonnet-20250219`. You can override this using the following environment variables: ```bash # Anthropic API ANTHROPIC_MODEL='claude-3-7-sonnet-20250219' ANTHROPIC_SMALL_FAST_MODEL='claude-3-5-haiku-20241022' # Amazon Bedrock ANTHROPIC_MODEL='us.anthropic.claude-3-7-sonnet-20250219-v1:0' ANTHROPIC_SMALL_FAST_MODEL='us.anthropic.claude-3-5-haiku-20241022-v1:0' # Google Vertex AI ANTHROPIC_MODEL='claude-3-7-sonnet@20250219' ANTHROPIC_SMALL_FAST_MODEL='claude-3-5-haiku@20241022' ``` You can also set these variables using the global configuration: ```bash # Configure for Anthropic API claude config set --global env '{"ANTHROPIC_MODEL": "claude-3-7-sonnet-20250219"}' # Configure for Bedrock claude config set --global env '{"CLAUDE_CODE_USE_BEDROCK": "true", "ANTHROPIC_MODEL": "us.anthropic.claude-3-7-sonnet-20250219-v1:0"}' # Configure for Vertex AI claude config set --global env '{"CLAUDE_CODE_USE_VERTEX": "true", "ANTHROPIC_MODEL": "claude-3-7-sonnet@20250219"}' ``` See our [model names reference](https://docs.anthropic.com/en/docs/about-claude/models/all-models#model-names) for all available models across different providers. [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#use-with-third-party-apis) Use with third-party APIs -------------------------------------------------------------------------------------------------------------------------------- Claude Code requires access to both Claude 3.7 Sonnet and Claude 3.5 Haiku models, regardless of which API provider you use. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#connect-to-amazon-bedrock) Connect to Amazon Bedrock ```bash CLAUDE_CODE_USE_BEDROCK=1 ``` If you’d like to access Claude Code via proxy, you can use the `ANTHROPIC_BEDROCK_BASE_URL` environment variable: ```bash ANTHROPIC_BEDROCK_BASE_URL='https://your-proxy-url' ``` If you don’t have prompt caching enabled, also set: ```bash DISABLE_PROMPT_CACHING=1 ``` Requires standard AWS SDK credentials (e.g., `~/.aws/credentials` or relevant environment variables like `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`). To set up AWS credentials, run: ```bash aws configure ``` Contact Amazon Bedrock for prompt caching for reduced costs and higher rate limits. Users will need access to both Claude 3.7 Sonnet and Claude 3.5 Haiku models in their AWS account. If you have a model access role, you may need to request access to these models if they’re not already available. Access to Bedrock in each region is necessary because inference profiles require cross-region capability. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#connect-to-google-vertex-ai) Connect to Google Vertex AI ```bash CLAUDE_CODE_USE_VERTEX=1 CLOUD_ML_REGION=us-east5 ANTHROPIC_VERTEX_PROJECT_ID=your-project-id ``` If you’d like to access Claude Code via proxy, you can use the `ANTHROPIC_VERTEX_BASE_URL` environment variable: ```bash ANTHROPIC_VERTEX_BASE_URL='https://your-proxy-url' ``` If you don’t have prompt caching enabled, also set: ```bash DISABLE_PROMPT_CACHING=1 ``` Claude Code on Vertex AI currently only supports the `us-east5` region. Make sure your project has quota allocated in this specific region. Users will need access to both Claude 3.7 Sonnet and Claude 3.5 Haiku models in their Vertex AI project. Requires standard GCP credentials configured through google-auth-library. To set up GCP credentials, run: ```bash gcloud auth application-default login ``` For the best experience, contact Google for heightened rate limits. [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#connect-though-a-proxy) Connect though a proxy ------------------------------------------------------------------------------------------------------------------------------ When using Claude Code with an LLM proxy (like [LiteLLM](https://docs.litellm.ai/docs/simple_proxy)), you can control authentication behavior using the following environment variables and configs. Note that you can mix and match these with Bedrock and Vertex-specific settings. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#environment-variables-2) Environment variables * `ANTHROPIC_AUTH_TOKEN`: Custom value for the `Authorization` and `Proxy-Authorization` headers (the value you set here will be prefixed with `Bearer `) * `ANTHROPIC_CUSTOM_HEADERS`: Custom headers you want to add to the request (in `Name: Value` format) * `HTTP_PROXY`: Set the HTTP proxy URL * `HTTPS_PROXY`: Set the HTTPS proxy URL If you prefer to configure via a file instead of environment variables, you can add any of these variables to the `env` object in your global Claude config (in _~/.claude.json_). ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#global-configuration-options) Global configuration options * `apiKeyHelper`: A custom shell script to get an API key (invoked once at startup, and cached for the duration of each session) * * * [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#development-container-reference-implementation) Development container reference implementation -------------------------------------------------------------------------------------------------------------------------------- Claude Code provides a development container configuration for teams that need consistent, secure environments. This preconfigured [devcontainer setup](https://code.visualstudio.com/docs/devcontainers/containers) works seamlessly with VS Code’s Remote - Containers extension and similar tools. The container’s enhanced security measures (isolation and firewall rules) allow you to run `claude --dangerously-skip-permissions` to bypass permission prompts for unattended operation. We’ve included a [reference implementation](https://github.com/anthropics/claude-code/tree/main/.devcontainer) that you can customize for your needs. While the devcontainer provides substantial protections, no system is completely immune to all attacks. Always maintain good security practices and monitor Claude’s activities. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#key-features) Key features * **Production-ready Node.js**: Built on Node.js 20 with essential development dependencies * **Security by design**: Custom firewall restricting network access to only necessary services * **Developer-friendly tools**: Includes git, ZSH with productivity enhancements, fzf, and more * **Seamless VS Code integration**: Pre-configured extensions and optimized settings * **Session persistence**: Preserves command history and configurations between container restarts * **Works everywhere**: Compatible with macOS, Windows, and Linux development environments ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#getting-started-in-4-steps) Getting started in 4 steps 1. Install VS Code and the Remote - Containers extension 2. Clone the [Claude Code reference implementation](https://github.com/anthropics/claude-code/tree/main/.devcontainer) repository 3. Open the repository in VS Code 4. When prompted, click “Reopen in Container” (or use Command Palette: Cmd+Shift+P → “Remote-Containers: Reopen in Container”) ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#configuration-breakdown) Configuration breakdown The devcontainer setup consists of three primary components: * [**devcontainer.json**](https://github.com/anthropics/claude-code/blob/main/.devcontainer/devcontainer.json): Controls container settings, extensions, and volume mounts * [**Dockerfile**](https://github.com/anthropics/claude-code/blob/main/.devcontainer/Dockerfile): Defines the container image and installed tools * [**init-firewall.sh**](https://github.com/anthropics/claude-code/blob/main/.devcontainer/init-firewall.sh): Establishes network security rules ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#security-features) Security features The container implements a multi-layered security approach with its firewall configuration: * **Precise access control**: Restricts outbound connections to whitelisted domains only (npm registry, GitHub, Anthropic API, etc.) * **Default-deny policy**: Blocks all other external network access * **Startup verification**: Validates firewall rules when the container initializes * **Isolation**: Creates a secure development environment separated from your main system ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#customization-options) Customization options The devcontainer configuration is designed to be adaptable to your needs: * Add or remove VS Code extensions based on your workflow * Modify resource allocations for different hardware environments * Adjust network access permissions * Customize shell configurations and developer tooling * * * [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#next-steps) Next steps ------------------------------------------------------------------------------------------------------ [Claude Code tutorials --------------------- Step-by-step guides for common tasks](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/tutorials)[Troubleshooting --------------- Solutions for common issues with Claude Code](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/troubleshooting)[Reference implementation ------------------------ Clone our development container reference implementation.](https://github.com/anthropics/claude-code/tree/main/.devcontainer) * * * [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#license-and-data-usage) License and data usage ------------------------------------------------------------------------------------------------------------------------------ Claude Code is provided as a Beta research preview under Anthropic’s [Commercial Terms of Service](https://www.anthropic.com/legal/commercial-terms). ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#how-we-use-your-data) How we use your data We aim to be fully transparent about how we use your data. We may use feedback to improve our products and services, but we will not train generative models using your feedback from Claude Code. Given their potentially sensitive nature, we store user feedback transcripts for only 30 days. #### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#feedback-transcripts) Feedback transcripts If you choose to send us feedback about Claude Code, such as transcripts of your usage, Anthropic may use that feedback to debug related issues and improve Claude Code’s functionality (e.g., to reduce the risk of similar bugs occurring in the future). We will not train generative models using this feedback. ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#privacy-safeguards) Privacy safeguards We have implemented several safeguards to protect your data, including limited retention periods for sensitive information, restricted access to user session data, and clear policies against using feedback for model training. For full details, please review our [Commercial Terms of Service](https://www.anthropic.com/legal/commercial-terms) and [Privacy Policy](https://www.anthropic.com/legal/privacy). ### [​](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#license) License © Anthropic PBC. All rights reserved. Use is subject to Anthropic’s [Commercial Terms of Service](https://www.anthropic.com/legal/commercial-terms). Was this page helpful? YesNo [Embeddings](https://docs.anthropic.com/en/docs/build-with-claude/embeddings)[Claude Code tutorials](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/tutorials) [x](https://x.com/AnthropicAI)[linkedin](https://www.linkedin.com/company/anthropicresearch) On this page * [Before you begin](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#before-you-begin) * [Check system requirements](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#check-system-requirements) * [Install and authenticate](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#install-and-authenticate) * [Core features and workflows](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#core-features-and-workflows) * [Security and privacy by design](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#security-and-privacy-by-design) * [From questions to solutions in seconds](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#from-questions-to-solutions-in-seconds) * [Initialize your project](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#initialize-your-project) * [Use Claude Code for common tasks](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#use-claude-code-for-common-tasks) * [Understand unfamiliar code](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#understand-unfamiliar-code) * [Automate Git operations](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#automate-git-operations) * [Edit code intelligently](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#edit-code-intelligently) * [Test and debug your code](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#test-and-debug-your-code) * [Encourage deeper thinking](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#encourage-deeper-thinking) * [Automate CI and infra workflows](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#automate-ci-and-infra-workflows) * [Control Claude Code with commands](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#control-claude-code-with-commands) * [CLI commands](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#cli-commands) * [Slash commands](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#slash-commands) * [Manage Claude’s memory](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#manage-claudes-memory) * [Determine memory type](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#determine-memory-type) * [How Claude looks up memories](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#how-claude-looks-up-memories) * [Quickly add memories with the # shortcut](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#quickly-add-memories-with-the-shortcut) * [Directly edit memories with /memory](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#directly-edit-memories-with-memory) * [Memory best practices](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#memory-best-practices) * [Manage permissions and security](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#manage-permissions-and-security) * [Tools available to Claude](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#tools-available-to-claude) * [Permission rules](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#permission-rules) * [Protect against prompt injection](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#protect-against-prompt-injection) * [Configure network access](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#configure-network-access) * [Environment variables](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#environment-variables) * [Configure Claude Code](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#configure-claude-code) * [Configuration options](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#configuration-options) * [Global configuration](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#global-configuration) * [Auto-updater permission options](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#auto-updater-permission-options) * [Recommended: Create a new user-writable npm prefix](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#recommended-create-a-new-user-writable-npm-prefix) * [Disabling the auto-updater](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#disabling-the-auto-updater) * [Project configuration](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#project-configuration) * [Optimize your terminal setup](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#optimize-your-terminal-setup) * [Themes and appearance](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#themes-and-appearance) * [Line breaks](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#line-breaks) * [Notification setup](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#notification-setup) * [Handling large inputs](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#handling-large-inputs) * [Vim Mode](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#vim-mode) * [Manage costs effectively](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#manage-costs-effectively) * [Track your costs](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#track-your-costs) * [Reduce token usage](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#reduce-token-usage) * [Model configuration](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#model-configuration) * [Use with third-party APIs](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#use-with-third-party-apis) * [Connect to Amazon Bedrock](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#connect-to-amazon-bedrock) * [Connect to Google Vertex AI](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#connect-to-google-vertex-ai) * [Connect though a proxy](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#connect-though-a-proxy) * [Environment variables](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#environment-variables-2) * [Global configuration options](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#global-configuration-options) * [Development container reference implementation](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#development-container-reference-implementation) * [Key features](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#key-features) * [Getting started in 4 steps](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#getting-started-in-4-steps) * [Configuration breakdown](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#configuration-breakdown) * [Security features](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#security-features) * [Customization options](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#customization-options) * [Next steps](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#next-steps) * [License and data usage](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#license-and-data-usage) * [How we use your data](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#how-we-use-your-data) * [Feedback transcripts](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#feedback-transcripts) * [Privacy safeguards](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#privacy-safeguards) * [License](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#license)