You can install Claude Code with a global npm command, then launch it from your project directory. The 15 minutes in this guide is a target for a straightforward setup, not a completion time Anthropic guarantees. Before starting, check the requirements, choose an eligible sign-in route, and avoid the four common snags: using sudo, confusing account access with installation, choosing the wrong Windows environment, and overlooking network or terminal settings.
Check your computer before installing
Anthropic’s setup documentation lists these requirements for Claude Code:
As an Amazon Associate I earn from qualifying purchases.
- macOS 10.15 or later, Ubuntu 20.04 or later, Debian 10 or later, or Windows 10 or later using WSL 1/2 or Git for Windows.
- At least 4 GB of RAM and Node.js 18 or later.
- An internet connection and residence in an Anthropic-supported country.
- Bash, Zsh, or Fish is preferred.
Requirements and availability can change; check Anthropic’s Claude Code setup guide for the current details. Installation does not itself provide account eligibility or access to a particular sign-in route.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Install and start Claude Code
- Open a terminal. Confirm Node.js is available and meets the listed minimum. If Node.js is missing or too old, install or update it using the method appropriate for your operating system.
- Install Claude Code globally:
npm install -g @anthropic-ai/claude-code. Do not addsudo. Anthropic’s setup documentation warns: “Do NOT usesudo npm install -gas this can lead to permission issues and security risks.” - Move into your project directory with
cd, then runclaude. Starting there lets Claude Code work in the project you intend to use. - Complete the sign-in flow for the account or enterprise deployment you plan to use. The available routes and their conditions are explained below.
- Check the installation by running
claude doctor. Anthropic says this checks the installation type and version.
Choose the authentication route that fits your account
These routes are different ways to authenticate, not different installation commands. Pick the one that matches your account or organization:
| Route | Who it fits | Condition stated by Anthropic |
|---|---|---|
| Anthropic Console | Users signing in through Anthropic’s developer console | Active billing is required. |
| Claude.ai | Users signing in with a Claude.ai account | A Pro or Max plan is required. |
| Amazon Bedrock or Google Vertex AI | Enterprise deployments using these cloud platforms | Use the enterprise setup for the relevant platform. |
Anthropic lists these options in its setup documentation. Plan eligibility, billing, and enterprise configuration can change, so confirm the current conditions there. If the command installed successfully but sign-in fails, first check whether your chosen route is available to your account rather than reinstalling the CLI.
Four mistakes that derail a quick setup
1. Adding sudo to the npm command
Use npm install -g @anthropic-ai/claude-code without elevated privileges. Anthropic cautions that sudo npm install -g can create permission issues and security risks. If a global install reports a permissions problem, do not reflexively rerun it with sudo; consult the setup instructions for the supported installation approach for your environment.
2. Treating a billing or login problem as an installation failure
The install command puts the CLI on your system; it does not make every account route eligible. Console sign-in requires active billing, while the Claude.ai route is listed for Pro or Max. For organization-managed use, check the Bedrock or Vertex AI setup. Separate the question “Did the executable install?” from “Can this account authenticate?” and use claude doctor to check installation details.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →3. Using the wrong Windows environment
Anthropic documents two Windows choices: WSL 1/2 or native Windows with Git for Windows. If you use portable Git and Claude Code cannot find Bash, the guide shows setting CLAUDE_CODE_GIT_BASH_PATH to the full path of bash.exe. Follow the Windows instructions in the official setup guide for the environment you selected rather than mixing WSL and native Windows steps.
Rank #3
4. Overlooking managed-network or terminal behavior
On a corporate or otherwise managed network, a working local install may still be unable to reach required services. Anthropic’s proxy guide says HTTP_PROXY and HTTPS_PROXY are supported; NO_PROXY and SOCKS proxies are not. Custom certificates may require SSL_CERT_FILE and NODE_EXTRA_CA_CERTS. The guide lists api.anthropic.com, statsig.anthropic.com, and sentry.io among destinations to allow. Ask your network administrator to check the applicable proxy and certificate settings rather than assuming the npm installation is broken.
A separate terminal issue can make multiline prompts awkward. In VS Code or iTerm2, Anthropic documents /terminal-setup for enabling Shift+Enter line breaks. See the interactive mode documentation for terminal behavior.
Make the first session useful
Once Claude Code is running in the project directory, ask it for a summary of the project to orient the session. Anthropic also suggests using /init to generate a CLAUDE.md file, then committing that file so the project’s guidance is available in version control. Review the generated content before committing it, as you would any project change.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
