from line 1
11# Quickstart
22
3> Welcome to Claude Code!
3> Install Claude Code in your terminal, sign in, and use the CLI to explore your codebase and make your first code change.
44
5This quickstart guide will have you using AI-powered coding assistance in a few minutes. By the end, you'll understand how to use Claude Code for common development tasks.
5This quickstart covers Claude Code in your terminal: installing the CLI, signing in from your first session, and using it for common development tasks in your own project.
66
77## Before you begin
88
from line 9
99Make sure you have:
1010
1111* A terminal or command prompt open
12 * If you've never used the terminal before, check out the [terminal guide](/docs/en/terminal-guide)
1312* A code project to work with
1413* A [Claude subscription](https://claude.com/pricing?utm_source=claude_code\&utm_medium=docs\&utm_content=quickstart_prereq) (Pro, Max, Team, or Enterprise), [Claude Console](https://platform.claude.com/) account, or access through a [supported cloud provider](/docs/en/third-party-integrations)
1514
1615<Note>
17 This guide covers the terminal CLI. Claude Code is also available on the [web](https://claude.ai/code), as a [desktop app](/docs/en/desktop), in [VS Code](/docs/en/vs-code) and [JetBrains IDEs](/docs/en/jetbrains), in [Slack](/docs/en/slack), and in CI/CD with [GitHub Actions](/docs/en/github-actions) and [GitLab](/docs/en/gitlab-ci-cd). See [all interfaces](/docs/en/overview#use-claude-code-everywhere).
16 These cases are covered on other pages:
17
18 * **Never used a terminal before**: start with the [terminal guide](/docs/en/terminal-guide)
19 * **Want Claude Code somewhere other than the terminal**: Claude Code is also available on the [web](https://claude.ai/code), as a [desktop app](/docs/en/desktop), in [VS Code](/docs/en/vs-code) and [JetBrains IDEs](/docs/en/jetbrains), in [Slack](/docs/en/slack), and in CI/CD with [GitHub Actions](/docs/en/github-actions) and [GitLab](/docs/en/gitlab-ci-cd). See [all interfaces](/docs/en/overview#use-claude-code-everywhere).
1820</Note>
1921
2022## Step 1: Install Claude Code
from line 31
2931 curl -fsSL https://claude.ai/install.sh | bash
3032 ```
3133
34 On Windows, your prompt shows `PS C:\` when you're in PowerShell and `C:\` without the `PS` when you're in CMD.
35
3236 **Windows PowerShell:**
3337
3438 ```powershell theme={null}
from line 47
4347
4448 When the installer finishes, open a new terminal window and run `claude --version`. A working installation prints a version number. If your shell says `claude` isn't found or isn't recognized, the install directory isn't on your PATH yet: see [Fix your PATH](/docs/en/troubleshoot-install#command-not-found-claude-after-installation).
4549
46 If you see `The token '&&' is not a valid statement separator`, you're in PowerShell, not CMD. If you see `'irm' is not recognized as an internal or external command`, you're in CMD, not PowerShell. Your prompt shows `PS C:\` when you're in PowerShell and `C:\` without the `PS` when you're in CMD.
50 If you see `The token '&&' is not a valid statement separator`, you're in PowerShell, not CMD. If you see `'irm' is not recognized as an internal or external command`, you're in CMD, not PowerShell.
4751
48 If the install command fails with `syntax error near unexpected token '<'`, a `403`, or another curl error, see [Troubleshoot installation](/docs/en/troubleshoot-install#find-your-error) to match the error to a fix and for alternative install methods.
52 If the install command fails with `syntax error near unexpected token '<'`, a `403`, or any other error, see [Troubleshoot installation](/docs/en/troubleshoot-install#find-your-error) to match the error to a fix and for alternative install methods.
4953
5054 [Git for Windows](https://git-scm.com/downloads/win) is recommended on native Windows so Claude Code can use the Bash tool. If Git for Windows is not installed, Claude Code uses PowerShell as the shell tool instead. WSL setups do not need Git for Windows.
5155
from line 91
8791
8892The command prints a version number followed by `(Claude Code)`.
8993
90## Step 2: Log in to your account
94## Step 2: Start your first session
9195
92Claude Code requires an account to use. Start an interactive session with the `claude` command and you'll be prompted to log in on first use:
96Open your terminal in any project directory and start Claude Code:
9397
9498```bash theme={null}
99cd /path/to/your/project
95100claude
96101```
97102
98For Claude subscription or Console accounts, follow the prompts to complete authentication in your browser. If you've set the `ANTHROPIC_API_KEY` environment variable, Claude Code skips the login prompt and asks you to approve the key instead. To switch accounts later or re-authenticate, type `/login` inside the running session:
103Replace `/path/to/your/project` with the path to the project you want to work on.
99104
100```text wrap theme={null}
101/login
102```
105Claude Code prompts you to log in on first use. For Claude subscription or Console accounts, follow the prompts to complete authentication in your browser. If you've set the `ANTHROPIC_API_KEY` environment variable and you approve the key when Claude Code asks whether to use it, Claude Code skips the login prompt.
103106
104107You can log in using any of these account types:
105108
from line 113
110113
111114Once logged in, your credentials are stored and you won't need to log in again. Learn more in [Credential Management](/docs/en/authentication#credential-management).
112115
113## Step 3: Start your first session
116The Claude Code prompt appears with the version, current model, and working directory shown above it. Type `/help` for available commands or `/resume` to continue a previous conversation. To switch accounts later or re-authenticate, type `/login` inside the running session.
114117
115Open your terminal in any project directory and start Claude Code:
118## Step 3: Ask your first question
116119
117```bash theme={null}
118cd /path/to/your/project
119claude
120```
120Try one of these commands:
121121
122Replace `/path/to/your/project` with the path to the project you want to work on.
123
124You'll see the Claude Code prompt with the version, current model, and working directory shown above it. Type `/help` for available commands or `/resume` to continue a previous conversation.
125
126## Step 4: Ask your first question
127
128Start by understanding your codebase. Try one of these commands:
129
130122```text wrap theme={null}
131123what does this project do?
132124```
from line 155
163155 Claude Code reads your project files as needed. You don't have to manually add context.
164156</Note>
165157
166## Step 5: Make your first code change
158## Step 4: Make your first code change
167159
168Now have Claude Code do some actual coding. Try a simple task:
160Try a small task:
169161
170162```text wrap theme={null}
171163add a hello world function to the main file
from line 165
173165
174166Claude Code finds the appropriate file and shows you the change. If it asks before making the change, select **Yes** to approve.
175167
176With Claude Code v2.1.283 or later, auto mode is the [built-in starting permission mode](/docs/en/permission-modes#eliminate-prompts-with-auto-mode) for interactive terminal sessions: a classifier reviews actions instead of you, and Claude edits most files and runs most commands without asking you. On earlier versions, auto mode is the built-in starting permission mode only on Pro, Max, and Team plans. For the session you start right after installing, see [First session after an install or upgrade](/docs/en/env-vars#first-session-after-an-install-or-upgrade).
168The session's [permission mode](/docs/en/permission-modes) sets which actions Claude can take without asking you first. Press `Shift+Tab` at any time to switch the permission mode of the session you're in.
177169
178<Note>
179 Your settings or your organization can set a different starting permission mode. [Which permission mode a session starts in](/docs/en/permission-modes#which-mode-a-session-starts-in) lists what does. Press `Shift+Tab` at any time to switch the permission mode of the session you're in.
180</Note>
170## Step 5: Use Git with Claude Code
181171
182## Step 6: Use Git with Claude Code
183
184172Claude Code makes Git operations conversational:
185173
186174```text wrap theme={null}
from line 193
205193help me resolve merge conflicts
206194```
207195
208## Step 7: Fix a bug or add a feature
196## Step 6: Fix a bug or add a feature
209197
210Claude is proficient at debugging and feature implementation.
211
212198Describe what you want in natural language:
213199
214200```text wrap theme={null}
from line 207
221207there's a bug where users can submit empty forms - fix it
222208```
223209
224Claude Code will:
210## Step 7: Test out other common workflows
225211
226* Locate the relevant code
227* Understand the context
228* Implement a solution
229* Run tests if available
230
231## Step 8: Test out other common workflows
232
233212There are a number of ways to work with Claude:
234213
235214**Refactor code**
from line 308
329308
330309Now that you've learned the basics, explore more advanced features:
331310
332<CardGroup cols={2}>
333 <Card title="How Claude Code works" icon="microchip" href="/docs/en/how-claude-code-works">
334 Understand the agentic loop, built-in tools, and how Claude Code interacts with your project
335 </Card>
311* [How Claude Code works](/docs/en/how-claude-code-works): understand the agentic loop, built-in tools, and how Claude Code interacts with your project
312* [Best practices](/docs/en/best-practices): get better results with effective prompting and project setup
313* [Common workflows](/docs/en/common-workflows): step-by-step guides for common tasks
314* [Extend Claude Code](/docs/en/features-overview): customize with CLAUDE.md, skills, hooks, MCP, and more
336315
337 <Card title="Best practices" icon="star" href="/docs/en/best-practices">
338 Get better results with effective prompting and project setup
339 </Card>
316See [advanced setup](/docs/en/setup) for installation options, manual updates, or uninstallation instructions.
340317
341 <Card title="Common workflows" icon="graduation-cap" href="/docs/en/common-workflows">
342 Step-by-step guides for common tasks
343 </Card>
344
345 <Card title="Extend Claude Code" icon="puzzle-piece" href="/docs/en/features-overview">
346 Customize with CLAUDE.md, skills, hooks, MCP, and more
347 </Card>
348</CardGroup>
349
350318## Getting help
351319
352* **In Claude Code**: Type `/help` or ask a "how do I" question
353* **Documentation**: You're here! Browse other guides
354* **Courses**: Take [Claude Code 101](https://academy.claude.com/courses/claude-code-101) and other free self-paced courses on [Claude Academy](https://academy.claude.com/)
355* **Community**: Join the [Discord server](https://www.anthropic.com/discord) for tips and support
320* **In Claude Code**: type `/help` or ask a "how do I" question
321* **Documentation**: browse the other guides on this site
322* **Courses**: take [Claude Code 101](https://academy.claude.com/courses/claude-code-101) and other free self-paced courses on [Claude Academy](https://academy.claude.com/)
323* **Community**: join the [Discord server](https://www.anthropic.com/discord) for tips and support
356324
No line in this hunk matches that.