Updated · Sources & corrections
In this guide
Claude Code has native installation routes as well as package-manager alternatives. Node.js is not a requirement for the native installer. Use the official setup reference for your current operating-system requirements and supported installation choices.
Choose one installation method
Follow the native installer or package-manager instructions linked below. Review a downloaded installer before running it, and avoid mixing installation methods when troubleshooting. On managed devices, follow the administrator-approved route.
- Windows: the official setup page provides separate PowerShell and Command Prompt commands. Choose the command matching your shell.
- macOS: use the documented native installer or Homebrew route.
- Linux or WSL: use the documented Linux installer or supported distribution package.
This guide links to the live vendor installation commands so a changing bootstrap script is not mistaken for a fixed, independently audited package. Record the installation method and version when reporting a problem.
Verify the CLI before authentication
claude --version
claude --helpA version string shows that a Claude executable is on PATH. It does not prove you installed the intended copy. If the shell cannot find it, open a fresh terminal and follow the setup page’s PATH section. If different terminals show different versions, check the executable locations and remove only the duplicate installation you identified.
Sign in and verify your account state
claude auth login
claude auth statusThe current CLI reference documents these authentication commands. Follow the browser sign-in flow for the account you intend to use. Subscription access, API billing and organisational deployments have different entitlements; check those before assuming a model or feature is available. Keep credentials out of shell history and public issue reports.
Start in the project you intend to edit
cd path/to/your/project
claudeBegin with a small read-only question about the repository. Review permission prompts and proposed edits before allowing commands that change files. A successful sign-in does not mean the assistant should receive unrestricted access to unrelated folders.
Troubleshoot the actual failure
- Command not found: inspect PATH and reopen the terminal.
- Installer syntax error: confirm whether the command is for PowerShell, CMD or a POSIX shell.
- Sign-in failure: check the account and authentication route before reinstalling.
- API error after sign-in: record the status code and time; distinguish local installation from a service incident.
The npm distribution is an alternative route with its own Node requirements. Consult the vendor’s current npm section if you specifically need it; native-install users should not install Node solely because an older tutorial says it is mandatory.
Next: skills and project configuration and MCP server configuration.
Sources and verification scope
This is a documentation-based guide. Command outputs and configuration examples are illustrative unless explicitly identified as recorded test results. Check the installed version and platform; a successful syntax check does not establish hardware compatibility.
Editorial update, 21 October 2026: source references and verification scope added; identified command, feature or wording errors corrected. Read our sourcing and correction policy.
If a configured client starts but requests fail, use our Claude Code 500 error diagnostic to distinguish provider failures, limits and network symptoms before changing installation settings or rerunning a coding task.