My claude command isn't working. What now?

Why this is the answer, not a step-by-step fix

There are at least a dozen reasons typing claude might not work on your machine. Your PATH isn't set up. npm installed it in a folder your shell can't see. You have two versions from different installers fighting each other. You installed it in a terminal window that needs to be restarted. Your shell is bash instead of zsh and the installer only updated one of them. And so on.

A single webpage cannot cover every one of those cases in a way that's both clear and correct. But an AI model that can see your exact error and respond to you personally can. That's literally what these tools are for. The course's core idea is that you delegate work to a model instead of memorizing the steps yourself, and debugging your own tool install is no exception.

Once your claude command launches successfully, you'll use Claude Code itself for most future troubleshooting. But right now, while it's still broken, you need an agent that isn't depending on the broken tool — which means the web version of Claude, Gemini, or ChatGPT in your browser.

How to make the web model useful to you

A few tips that make this conversation go faster:

• ›Tell it your operating system upfront. "I'm on a Mac" or "I'm on Windows 11" saves it from guessing. If you know which version (macOS Sonoma, Windows 11 Home, etc.), that helps too, but the basic OS name is enough to get started.
• ›Say how you installed Claude Code. Did you run the official installer from claude.ai? Did you install via npm? Did a colleague do it for you? The model will ask a different first question in each case, so telling it upfront saves a round trip.
• ›Paste the exact error, not your paraphrase of it. "It says command not found" is less useful than a screenshot showing zsh: command not found: claude. Exact words matter because they tell the model which shell and which failure mode.
• ›Paste new screenshots as the conversation goes. The model will tell you to try something, then ask what happened. Show it what happened. Don't summarize — paste.
• ›If it tells you to run a destructive command, ask what it does first. The model will sometimes suggest commands that delete files or change system settings. You can always ask "what does this command do before I run it?" and make sure you understand the answer before pressing Enter.

Plain-English PATH context, if you want it

You don't need this section to fix the problem. It's only here in case you're curious why "command not found" happens in the first place and want a mental model before the AI model starts walking you through the fix.

When you type a command in your terminal, your shell doesn't search your whole computer for a program with that name. It only looks in a specific list of folders, called your PATH. PATH is just a list of folders separated by colons, stored as an environment variable on your machine. When you type claude, your shell walks through each folder in PATH in order and runs the first claude it finds.

"Command not found" means the claude binary is definitely on your computer — it's just sitting in a folder that isn't on your PATH. The fix is always some variation of "tell your shell to look in the right folder." Which exact folder depends on how Claude Code was installed, which is why it's easier to let the AI model handle it than to guess.