What you’ll know by the end of this check

Which install path to pick (and which one to skip)
How to sign in with a Pro, Max, Enterprise, or API-key account
Where Claude Code lives and what it can see on disk

The shortest possible answer

On macOS / Linux / WSL: run the curl one-liner from claude.com/product/claude-code. On Windows: use PowerShell’s Invoke-RestMethod or curl in CMD.

Then cd into a project directory and run claude. It will ask for a color theme and a login method. Pick the account type that matches how you work (Pro/Max for personal, Enterprise if your org has it, API key if you’re billing by usage).

Which surface to pick

Surface	Pick it when
Terminal	You want the newest features first — they ship here before anywhere else.
VS Code / JetBrains	You want Claude Code inside your editor. Nearly identical experience.
Claude Desktop (Code toggle)	You want long-running sessions in the background while you do other work.
Web (`claude.ai/code`)	You’re working inside a GitHub repo and don’t want anything local.

Skip for auto-updates: Homebrew on macOS and winget on Windows both work, but neither auto-updates. If you want the newest flags and features without babysitting, use the curl install.

What it can see

Whichever directory you run claude in, it has access to that directory and all subfolders. Nothing above it. This is a feature — it gives you a natural scope fence. A project repo, a scratch folder, a single markdown directory. Whatever you point it at.

Things to try right now (5 minutes)

Install Claude Code with the method that matches your OS.
Run claude --version in your terminal to confirm it loaded.
cd into a safe project (a toy repo, a scratch folder), run claude, and let it walk you through login. Pick your color theme and account. Exit with Ctrl+C.

The canonical version

Full official lesson is at anthropic.skilljar.com/claude-code-101/469790.

Ready to verify this check?

claude runs. You’ve logged in. You’ve confirmed which surface you’re going to use day-to-day. Mark it cleared.