How to Install Claude Code in 10 Minutes (Even If You’ve Never Touched a Terminal)

If you have been told that how to install Claude Code is a job for developers only, this guide is going to change your mind. Claude Code is Anthropic’s AI coding agent that lives in your terminal — and despite the word “code,” you do not need to be a programmer to run it. You just need to get it installed once, and that is exactly what we are going to do here: a calm, no-jargon walkthrough that takes about ten minutes, even if you have never opened a terminal in your life.

I run more than ten autonomous businesses on top of Claude Code, and the single biggest thing standing between most solopreneurs and their first automated win is not talent — it is the install. So we are going to remove that wall. By the end of this post you will have Claude Code installed on your Mac or Windows machine, you will have fixed the four errors that trip up almost every beginner, and you will have pointed it at a real business task instead of a throwaway “hello world” demo.

Before You Install Claude Code: What You Actually Need (and What You Don’t)

Let’s clear the fog first, because most install guides assume you already know what half the words mean. Here is the honest list of what you need before you install Claude Code — and, just as importantly, what you can safely ignore.

You need three things:

• A computer running macOS, Windows, or Linux. Anything from the last five years is fine. Claude Code is a lightweight command-line tool, not a heavy program — it will not slow your machine down.
• A terminal. This is the plain text window where you type commands. Your Mac already has one called Terminal. On Windows we will use something called WSL, which I will walk you through. Do not be intimidated by it — a terminal is just a text box that follows instructions.
• A Claude account. A Claude Pro or Max subscription is the simplest way to power Claude Code, though you can also connect an Anthropic API key if you prefer usage-based billing. If you are weighing the cost, read our breakdown of whether Claude Code is free and what it really costs a solopreneur before you commit.

What you do NOT need: a coding background, a fancy code editor, a GitHub account, or any prior command-line experience. You do not need to “learn to code” first. Claude Code writes and edits the files; your job is to describe what you want in plain English.

One technical requirement matters and it is the one beginners miss: if you install using the Node method (the most common one), you need Node.js version 18 or newer. We will check for it and install it together — no guessing.

Subscription or API key — which should a beginner pick?

You will hit this decision on your very first login, so let’s settle it now. If you already pay for Claude Pro or Max, logging in with that account is the no-brainer choice: predictable monthly cost, nothing to configure. If you would rather pay only for what you use, an Anthropic API key bills per token instead. For most solopreneurs starting out, the subscription is calmer — you experiment freely without watching a meter. You can always switch later; the install is identical either way.

How to Install Claude Code on a Mac (Step by Step)

Mac is the smoothest path, so we will start here. Open Terminal — press Cmd + Space, type “Terminal,” and hit Enter. You now have the text window we need.

Step 1 — Check for Node.js. Type this and press Enter:

node --version

If you see something like v20.11.0 (any number 18 or higher), you are ready — skip to Step 3. If you see command not found, you need Node first.

Step 2 — Install Node.js (only if you need it). The friendliest way is to install Node.js from the official site — download the “LTS” version and run the installer like any normal app. Prefer the terminal? If you already have Homebrew, run brew install node. Either way, close and reopen Terminal when it finishes, then run node --version again to confirm.

Step 3 — Install Claude Code. This is the single command that does the real work:

npm install -g @anthropic-ai/claude-code

The -g means “install it globally” so you can run it from any folder. Give it thirty seconds. When the text stops scrolling and you get your prompt back, Claude Code is installed.

Step 4 — Confirm it worked. Type:

claude --version

A version number means success. If instead you get command not found, don’t panic — that is the most common hiccup and we fix it in the errors section below. Prefer to skip Node entirely? Anthropic also ships a native installer you can run with curl -fsSL https://claude.ai/install.sh | bash, which downloads Claude Code directly without npm. Both paths end in the same place.

How to Install Claude Code on Windows (WSL, the Easy Way)

Windows has one extra step, but it is genuinely easy once you know the trick. Claude Code runs best inside WSL — the Windows Subsystem for Linux. That sounds scary; it is not. WSL is a free, official Microsoft feature that gives Windows a small, friendly Linux terminal. Think of it as a clean workshop inside your house where the tools just work.

Step 1 — Turn on WSL. Open the Start menu, type “PowerShell,” right-click it and choose Run as administrator. In the blue window, type:

wsl --install

Press Enter. Windows will download and set up Ubuntu (a version of Linux) for you. When it is done, restart your computer — this part matters.

Step 2 — Open your new Linux terminal. After the restart, open the Start menu and launch “Ubuntu.” The first time, it will ask you to create a username and password. This is separate from your Windows login — pick something simple and write it down. You now have a proper terminal.

Step 3 — Install Node.js inside WSL. Paste these two lines, one at a time:

sudo apt update
sudo apt install -y nodejs npm

It will ask for the password you just created. Typing it shows nothing on screen — that is normal, just type and press Enter.

Step 4 — Install Claude Code. Same command as the Mac:

npm install -g @anthropic-ai/claude-code

Then confirm with claude --version. That’s it — you now have Claude Code running on Windows. If you would rather understand what this tool actually is before you dive deeper, our operator’s guide to the Claude Code CLI explains how to run it like a business tool, not just a coding toy.

The 4 Install Errors Beginners Hit — and the Exact Fixes

Ninety percent of “I couldn’t install Claude Code” stories come down to four errors. None of them mean you did anything wrong — they are just the normal friction of a first setup. Here is each one and the exact fix.

Error 1: “node: command not found” or a version below 18

This means Node.js is missing or too old. Go back and install the current LTS version of Node from the official site (Mac) or run sudo apt install -y nodejs npm (WSL). Close and reopen your terminal afterward so it picks up the new version, then confirm with node --version.

Error 2: “claude: command not found” after a successful install

Frustrating, because the install looked like it worked. The cause is almost always that your terminal cannot yet see where npm put the program (a “PATH” issue). The quick fix: fully close your terminal window and open a brand-new one, then try claude --version again. Nine times out of ten that solves it, because the new window reloads your settings.

Error 3: “EACCES: permission denied” during install

This is npm complaining that it cannot write to a protected folder. Do not fix this by adding sudo in front of the command — that creates worse problems later. The clean fix is to install Node through a version manager like nvm, which keeps everything inside your own user folder where npm is allowed to write. Install nvm, install Node with it, then re-run the Claude Code install command with no sudo.

Error 4: Nothing works on Windows — because you skipped WSL

If you tried to install inside plain PowerShell or Command Prompt and hit a wall, this is your issue. Go back to the Windows section, install WSL, and run everything inside the Ubuntu terminal instead. This one fix resolves a huge share of Windows install problems in a single move.

Stuck on something not listed here? Copy the exact error message and paste it into a search — but honestly, once Claude Code is running, you can paste errors to it and have it explain them in plain English. That is the whole point.

Your First Login and First Session

Installed and confirmed? Now let’s actually start it. The first launch is where the magic clicks into place.

Step 1 — Make a folder to work in. Claude Code operates inside a folder (a “project”). Create a simple one and move into it:

mkdir my-first-project
cd my-first-project

Step 2 — Launch Claude Code. Type the one word that starts everything:

claude

Step 3 — Log in. The very first time, Claude Code opens your web browser and asks you to log in to your Claude account (or paste an API key). Approve it, and the browser hands the connection back to your terminal automatically. You only do this once — after that, Claude Code remembers you.

Step 4 — Say hello with intent. You will see a prompt waiting for you. Type a real instruction in plain English, for example: “Create a file called notes.txt with three ideas for a welcome email.” Watch Claude Code think, propose the change, and ask for your approval before it writes anything. That approval step is your safety net — nothing happens to your files without a yes from you. If you want to lock that safety down further as you grow, our guide to Claude Code hooks shows how operators put guardrails around what the agent is allowed to do.

That is a full session: you asked, it acted, you approved. Everything else you will ever do with Claude Code is a richer version of that same loop.

The First Thing to Build (a Business Task, Not a Coding Demo)

Most tutorials stop at “hello world,” and that is exactly why beginners install Claude Code and then never touch it again — they never saw it do anything useful. So let’s break that pattern. Your first build should be a small, real chore from your actual business. Here is a great starter that works for almost any solopreneur.

Task: turn a messy folder of files into an organized, dated archive. Most of us have a “Downloads” graveyard full of invoices, receipts, and PDFs. Point Claude Code at it and say:

“Look at the files in this folder. Write a small script that renames each PDF to include its date and a short description, then sorts them into subfolders by month. Explain what the script does before you run it, and ask me before making changes.”

Claude Code will read the folder, write the script, walk you through it in plain English, and only act once you approve. In two minutes you have automated a chore that used to eat an afternoon — and you have proof, in your own business, of what this tool does.

Other strong first tasks: draft a week of social captions from a single blog post, build a one-page pricing calculator for your service, or clean up a spreadsheet of leads and flag the duplicates. The rule is simple: pick something you already do by hand and hate. That is where the “wow” lives. If you want to see how far this goes, the same loop is what powers my Claude Code plugin stack across a fleet of automated brands.

One habit that makes every task better

Before you ask Claude Code to do anything real, spend thirty seconds telling it the context. Create a short file — many operators call it CLAUDE.md — in your project folder and write a few plain sentences: what the business does, what you want done, and any rules it should follow. Claude Code reads that file automatically at the start of every session, so instead of re-explaining yourself each time, you set the stage once and it remembers. This is the difference between a tool that “kind of helps” and one that feels like a teammate who already knows your business. Start scrappy — a single paragraph is plenty on day one — and add to it as you learn what you ask for most.

Where to Go Next

You have crossed the hardest line: from “I’ve heard of this” to “it’s running on my machine.” Here is the sane path forward so you build momentum instead of overwhelm.

• This week: run three real tasks, not tutorials. Repetition is how the terminal stops feeling foreign.
• Next: learn to keep a project tidy — one folder per job, a short notes file describing what you want. Claude Code works best when it has context.
• Then: explore the deeper features — custom commands, guardrails, and connecting your own tools — once the basics feel automatic.

The goal is not to become a programmer. It is to have a tireless operator sitting in your terminal, ready to do the work you describe. Installing it was step one. Using it every day is where the compounding starts.

Frequently Asked Questions About Installing Claude Code

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

No. Installing Claude Code is a few copy-paste commands, and using it is plain English. You describe the outcome; the agent writes and edits the code. Non-developers install and use it every day.

Is Claude Code free to install?

The tool itself installs for free, but running it requires either a Claude subscription or an Anthropic API key with usage-based billing. See our honest pricing breakdown for what it actually costs a solopreneur.

How long does it take to install Claude Code?

About ten minutes on a Mac, and around fifteen on Windows because of the one-time WSL setup. Most of that is downloading, not typing.

Can I install Claude Code on Windows without WSL?

A native Windows path exists, but for beginners WSL is far smoother and avoids the most common errors. If you are new to the terminal, use WSL — it is the shortcut, not the detour.

What do I do if the install fails?

Match your symptom to the four errors above — a missing Node version, a PATH issue, a permissions error, or skipping WSL on Windows. Between those four, you can resolve almost every failed install.

Final word: the terminal is not a gate that keeps you out — it is a door that lets your business in. You now know how to install Claude Code, how to fix what usually breaks, and how to point it at real work on day one. Go run one task today. That first automated win changes how you see everything else.