How to Install Claude Code: A Beginner's Setup Guide (2026)

Most guides treat installing Claude Code as a single copy-paste command. That works right up until it doesn’t: you hit a permission error, the terminal can’t find the claude command afterward, or you log in and have no idea what to type next. The command is the easy part. Knowing what surrounds it is what actually gets you to a working setup.

This guide walks through the whole path: what you need before you start, the exact steps on Windows and macOS, and the first command you run once everything is wired up. No prior terminal experience is assumed. By the end you’ll have Claude Code installed, authenticated, and answering its first question about your own code.

What you need before installing Claude Code

To install Claude Code you need a supported operating system, a terminal, an internet connection, and a paid Claude subscription — the free tier does not include Claude Code.

Here is the short checklist:

A supported OS. Windows 10 (version 1809 or later) or Windows 11, macOS 13 or later, or a modern Linux distribution. About 4 GB of RAM and an internet connection are the only real hardware demands.
A terminal. On Windows that’s PowerShell (built in) or the newer Windows Terminal. On macOS it’s the Terminal app in Applications → Utilities. Claude Code runs inside this text window — it is not a separate app with buttons.
A Claude account with a paid plan. Claude Code is included with Pro, Max, Team, and Enterprise plans, as well as API access through the Anthropic Console. The free Claude.ai tier does not unlock it. Check the official docs for the current plan details, since pricing and inclusions change.

You do not need to install Node.js, Python, or any other runtime first. The modern native installer is self-contained. If you’ve read older tutorials telling you to run npm install, that path still exists but is no longer the recommended one for most people.

It also helps to know what you’re installing before you commit. If “an AI coding tool in the terminal” sounds abstract, the plain-English explainer in what is Claude Code and the broader Claude Code guide give you the mental model in a few minutes.

How to install Claude Code on Windows

On Windows, the fastest way to install Claude Code is to open PowerShell and run a single install command that downloads and sets up everything for you.

Step by step:

Open PowerShell. Press the Windows key, type PowerShell, and open it. You don’t need to run it as Administrator for a standard install.
Run the native installer. Paste this and press Enter:
```
irm https://claude.ai/install.ps1 | iex
```
This downloads the official installer and runs it. It places the claude command somewhere your system can find it and may briefly print progress as it works.
Close and reopen PowerShell. This refreshes your environment so the new claude command is recognized. Skipping this is the single most common reason people think the install “failed.”
Verify it worked. In the fresh window, type:
```
claude --version
```
A version number means you’re set. If instead you see “command not found,” your terminal hasn’t picked up the new command yet — reopening it usually fixes that.

If your workplace blocks the script-piping approach, Claude Code also offers a standard downloadable installer and an npm-based path. Both are documented officially; the one-line command above is simply the least fiddly for most people.

How to install Claude Code on macOS

On macOS, you install Claude Code by running one curl command in the Terminal, or by using Homebrew if you already have it.

The standard route:

Open Terminal. Find it in Applications → Utilities, or press Cmd+Space, type Terminal, and hit Enter.
Run the native installer. Paste and press Enter:
```
curl -fsSL https://claude.ai/install.sh | bash
```
This pulls down the official installer and sets up the claude command. macOS may ask for your password — that’s the system confirming you allow the change, not Claude requesting anything special.
Open a new Terminal tab or window so your shell loads the new command.
Confirm the install. Run:
```
claude --version
```
A version number means you’re good to go.

If you already use Homebrew, you can skip curl entirely:

brew install --cask claude-code

Homebrew is a popular package manager for macOS. If you don’t know what it is, you don’t need it — the curl command above is complete on its own.

One macOS note: if Terminal feels intimidating, that’s normal. You only need to paste two commands to be up and running, and nothing here permanently changes your system in a way you can’t reverse.

Your first command: starting and logging into Claude Code

To start Claude Code, navigate to a project folder in your terminal and run claude, then log in through the browser window it opens.

Here’s the sequence the first time:

Move into a project folder. Claude Code works best when pointed at actual code. Use cd (change directory) to get there. For example:
```
cd Documents/my-project
```
If you don’t have a project yet, an empty folder is fine for testing.
Launch it. Type:
```
claude
```
The first run kicks off authentication. Claude Code opens your browser and asks you to sign in with your Claude account and approve access. Once you confirm, the terminal connects and you’re in.
Ask it something real. You’re now at an interactive prompt. Type a plain-English request and press Enter. Good first prompts:
- What does this project do?
- Explain the file structure to me.
- Find any obvious bugs in this code.

Claude Code reads your files, reasons about them, and replies — and it can edit files or run commands when you ask, pausing for your approval before anything significant happens. That approval step is your safety net; you stay in control of every change.

If you’re brand new to working this way, the Claude Code tutorial walks through a full first session, and Claude Code for non-coders is written specifically for people who’ve never lived in a terminal. To exit a session, type /exit or press Ctrl+C twice.

Where to go after a successful install

Once Claude Code is installed and answering questions, the next steps are learning its everyday workflows and connecting it to external tools through MCP.

A few directions worth exploring:

Build real working habits. Claude Code rewards a rhythm of small, reviewable steps rather than one giant request. The patterns in Claude Code workflows save a lot of trial and error.
Extend it with MCP. The Model Context Protocol lets Claude Code reach beyond your files — into databases, browsers, and external APIs. Start with Claude Code MCP and a shortlist of the best MCP servers to add real capabilities.
See how it compares. If you’re weighing tools, Claude Code vs Cursor and Claude Code vs GitHub Copilot lay out the trade-offs honestly so you can decide what fits your work.

You don’t need any of this on day one. Install it, ask it to explain a file, and let the rest come as you go.

FAQ

Is Claude Code free?

No. Claude Code requires a paid Claude plan — Pro, Max, Team, or Enterprise — or API access billed through the Anthropic Console. The free Claude.ai chat tier does not include it. Plan names, pricing, and exactly what’s bundled change over time, so confirm the current details on the official documentation.

Do I need to know how to code to install Claude Code?

No. Installation is just pasting one command into a terminal and signing in through your browser. Using Claude Code productively is easier if you understand code, but the tool is designed to explain things in plain language, and many non-developers use it to read, understand, and modify projects. The Claude Code for non-coders guide is built for exactly this audience.

Do I need Node.js to install Claude Code?

Not anymore. The recommended native installer is self-contained and requires no Node.js, Python, or other runtime. An older npm-based installation method still exists and works, but most people should use the one-line native installer for Windows and macOS shown above.

Why does my terminal say “claude: command not found” after installing?

This almost always means your terminal hasn’t refreshed since the install. Close the window completely and open a new one, then try claude --version again. If it still fails, the installer may not have added Claude Code to your system path; the official setup docs cover how to fix the path for your specific shell.

What is the difference between Claude Code and the Claude chat app?

The Claude chat app at Claude.ai is a web interface for conversations. Claude Code runs in your terminal and works directly with the files on your computer — it can read your whole project, edit files, and run commands with your approval. They share the same underlying model but solve different problems. For a fuller picture, see what is Claude Code.

Conclusion

Installing Claude Code comes down to three things: a supported system with a paid Claude plan, one install command for your OS, and one claude command to start your first session. The native installer removes the old hurdles — no runtimes to configure, no manual setup — so the friction that used to trip up beginners is mostly gone.

The real value starts after the install. Point Claude Code at a project, ask it to explain what’s there, and approve changes as you go. From that first “explain this file” prompt, you can grow into proper workflows and tool integrations at your own pace. If anything in your setup behaves differently from this guide, the official Claude Code docs are the authoritative reference and stay current as the tool evolves.