01Pick your way in
Claude Code is the same engine whichever door you use. Pick the one that matches how you already work, and know you can switch later because they share your conversation history.
01Terminal (CLI)
The original. Works everywhere, has every command, and is the best fit if you live in a shell or work over SSH.
02VS Code extension
A chat panel inside your editor, with side-by-side diffs, file and selection context, and plan review. The easiest start if VS Code is home.
03Desktop app
A graphical app if you'd rather not use a terminal at all. Not covered today, but worth a look.
This article sets up the first two. Most people end up using both: the panel for everyday edits, the terminal for everything else.
02Setting up the terminal version
Check first. You need Windows 10 (1809 or later), macOS 13+, or a recent Ubuntu, Debian or Alpine, with at least 4 GB of RAM and an internet connection. And you need an account: a Claude Pro, Max, Team or Enterprise plan, or an Anthropic Console account. The free Claude plan does not include Claude Code.
Install. The native installer is the recommended route. Open a terminal and run the line for your system:
# Windows PowerShell (prompt starts with PS) irm https://claude.ai/install.ps1 | iex # Windows CMD (no PS in the prompt) curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd # macOS, Linux or WSL curl -fsSL https://claude.ai/install.sh | bash
It prints no progress while it downloads, so don't panic if it looks quiet. When it finishes, open a new terminal window and check:
PS C:\dev> claude --version # prints a version number PS C:\dev> claude doctor # checks install, settings and updates
Prefer a package manager? Windows has winget install Anthropic.ClaudeCode, macOS has brew install --cask claude-code, and Debian, Fedora and Alpine have apt, dnf and apk repositories. npm works too (npm install -g @anthropic-ai/claude-code, needs Node.js 22 or later). One difference matters: the native installer updates itself in the background, while winget, Homebrew and the Linux package managers do not, so run their upgrade command now and then (or claude update where it applies).
Windows notes. You don't need to run as Administrator. Git for Windows is optional: with it Claude Code uses Git Bash for shell commands, without it Claude Code uses PowerShell. If you want a Linux toolchain, install inside WSL and use the Linux command there.
If something fails: claude not found or not recognized almost always means your terminal was open before the install, so open a new one. Seeing The token '&&' is not a valid statement separator means you pasted the CMD command into PowerShell; 'irm' is not recognized means the PowerShell command went into CMD. claude doctor tells you what it found.
03Setting up VS Code
You need VS Code 1.94 or later (check under Help, About) and the same kind of account as above. No API key is needed.
Install the extension. Press Ctrl+Shift+X (Cmd+Shift+X on Mac), search for Claude Code (publisher: Anthropic) and click Install. Or from a terminal:
PS C:\dev> code --install-extension anthropic.claude-code
If it doesn't appear, run Developer: Reload Window from the Command Palette (Ctrl+Shift+P). It also installs in Cursor and other VS Code forks.
Open it. With a file open, click the Spark icon at the top right of the editor. No file open? Click Claude Code in the bottom-right status bar, or search "Claude Code" in the Command Palette. Then click Sign in and approve in your browser.
Give it context without typing paths.
01Select code
Whatever you highlight is visible to Claude. Press Alt+K (Option+K on Mac) to insert a reference like @app.ts#5-10 into your prompt.
02@-mention
Type @ and part of a name to attach a file, or @src/components/ for a folder. It fuzzy-matches, so partial names work.
03Terminal output
Reference a terminal with @terminal:name so Claude can read an error or log without you copy-pasting it.
Review changes in a real diff. In Manual mode, each edit opens as a side-by-side comparison and waits for you. Accept, reject, or tell Claude what to do instead. You can even edit the proposed text in the diff before accepting.
Pick a permission mode using the indicator at the bottom of the prompt box: Manual asks before edits and most commands, Plan describes what it will do and waits for your approval, Edit automatically makes edits without asking, and Auto lets a classifier review most actions. While you're learning, use Manual or Plan.
Shortcuts worth learning on day one:
Windows / Linux macOS Ctrl+Esc Cmd+Esc switch editor / Claude Ctrl+Shift+Esc Cmd+Shift+Esc new conversation in a tab Alt+K Option+K insert @-reference Ctrl+Shift+P Cmd+Shift+P type "Claude Code" for every command
Two more things. Hover over any message for the rewind button: you can revert your code to that point, fork the conversation, or both. And the history button at the top of the panel lets you search and resume earlier conversations.
Terminal inside VS Code: the extension bundles its own copy of Claude Code for the chat panel, but it does not add claude to your PATH. If you also want to type claude in VS Code's integrated terminal (Ctrl+`), do the terminal install from step 02 once. The two share conversation history, so claude --resume can pick up a panel conversation.
04Your first session: look before you touch
Open one of your own projects (ideally a git repository) in VS Code, or in a terminal with cd, and start Claude. It may ask whether you trust the folder. That's a real safety check: say yes only to projects you own or trust.
The best first prompt changes nothing:
PS C:\dev> claude > explain how this project is laid out and how to run it
It reads files, follows imports and answers from what it finds. This is the fastest way to learn an unfamiliar codebase, and also a test: if the answer is wrong, you've found what to add to your CLAUDE.md from Day 2.
Then make one small real change with a clear ask:
> add a /health route to src/server.ts that returns { ok: true }.
Follow the style of the other routes, then run the tests.
Read the proposed edits and commands before you approve them, then read the final diff like a teammate's pull request. If you don't like it, git restore . throws the changes away, and in VS Code you can also use the rewind button.
05Tips that save you time
01Work inside git
Commit before you start. Then trying something is cheap: git diff shows what changed and git restore . undoes it.
02Read first, write second
Ask it to explain or plan before it edits. Plan mode is made for this: it proposes, you approve.
03One task per session
Finished something? Type /clear to start fresh. Old, unrelated chat only clutters its context.
04Name the file
"Fix the bug in src/auth.ts" beats "fix the login bug". Less searching, fewer wrong guesses.
05Press Esc early
Going the wrong way? Interrupt right away and redirect. Don't wait for it to finish a bad idea.
06Check your setup
/status shows your version, account and model. claude doctor diagnoses problems.
07Let it run your tests
Say "run the tests" in the ask. When it can verify its own work, you review less.
08Resume, don't repeat
claude --continue resumes the last session here, claude --resume lets you choose one.
06When it doesn't work
claude not foundNo Spark icon in VS Code
Asked to sign in again
Panel never responds
Open a file first, or use the status bar; check VS Code is 1.94+; reload the window
Sign in again, and launch VS Code from a terminal with
code . if you use an API key variableCheck your connection, start a new conversation, then run
claude in a terminal for a clearer error07Try this today
claude doctor.Next up: talking to it. Prompts that get the result you meant the first time.