Install Claude Code
Install Claude Code on macOS, Windows, or Linux and verify it, before connecting it to StoryClaw.
Claude Code ships a native installer that bundles its own runtime — Node.js is not required — and updates itself in the background.
System requirements
| Item | Requirement | Notes |
|---|---|---|
| macOS | 13.0 or later | Apple Silicon and Intel |
| Windows | 10 (1809+) / 11 / Server 2019+ | Native or WSL |
| Linux | Ubuntu 20.04+, Debian 10+, Alpine 3.19+ | — |
| Hardware | 4 GB+ RAM, x64 or ARM64 | — |
| Node.js | 22 or later recommended | Only relevant for the npm install |
macOS
In a terminal:
curl -fsSL https://claude.ai/install.sh | bashHomebrew works too:
brew install --cask claude-codeHomebrew builds do not update themselves — run brew upgrade claude-code yourself.
Windows
In PowerShell:
irm https://claude.ai/install.ps1 | iexIn CMD:
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmdWinGet works too (also no self-updates — run winget upgrade Anthropic.ClaudeCode yourself):
winget install Anthropic.ClaudeCodeThe install needs no administrator rights. Installing Git for Windows is recommended — Claude Code uses the Git Bash it provides to run its Bash tool; without it, commands run through PowerShell instead. If your project lives in WSL, install and launch from the WSL terminal using the Linux steps below rather than from PowerShell.
Linux
In a terminal:
curl -fsSL https://claude.ai/install.sh | bashDebian, Fedora, RHEL, and Alpine can also install from the officially signed apt / dnf / apk repositories; commands are in the Claude Code setup docs. Those installs do not self-update either — they follow your system's upgrade flow.
Installing with npm
If you already run a stable Node.js setup, or the native installer is blocked on your machine, npm is the officially supported fallback:
npm install -g @anthropic-ai/claude-codeSince v2.1.198 the npm package declares Node.js 22 as its required version — older versions print an EBADENGINE warning during install but usually finish anyway; upgrade Node.js if you hit problems. This installs the same native binary, and Node.js is not used at runtime. Do not use sudo npm install -g — it causes permission and security problems. Upgrade with npm install -g @anthropic-ai/claude-code@latest, not npm update -g: the latter is bound by the semver range from the original install and may not reach the newest version.
Verify the installation
In a terminal:
claude --versionA version number means the install succeeded. If you get command not found, open a new terminal first — the installer updated PATH, and already-open sessions still use the old value.
Claude Code still talks to Anthropic at this point. Continue with Configure Claude Code to point it at StoryClaw.
Editor extensions
Claude Code also runs inside your editor, sharing the same configuration as the command line — once StoryClaw is connected, the extension needs no setup of its own.
- VS Code / Cursor — install the Claude Code extension, or search for "Claude Code" in the Extensions panel (
Cmd+Shift+X/Ctrl+Shift+X). It adds inline diffs,@-mentions for files, and change-plan review. - JetBrains IDEs — install the Claude Code plugin from the JetBrains Marketplace, then restart the IDE. IntelliJ IDEA, PyCharm, WebStorm, and others are supported.
Troubleshooting
| Symptom | Fix |
|---|---|
claude: command not found right after installing | Open a new terminal. If that fails, add the install directory to PATH: on macOS / Linux run echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc; on Windows add %USERPROFILE%\.local\bin to the user Path variable and reopen the terminal. |
| Installed, but the file is missing | Check that the binary exists: ls ~/.local/bin/claude on macOS / Linux, Test-Path "$env:USERPROFILE\.local\bin\claude.exe" on Windows. If it does, only PATH is wrong. |
CMD reports 'irm' is not recognized | You are in CMD — use the CMD command above. Conversely, The token '&&' is not a valid statement separator means you are in PowerShell. |
npm install -g fails with EACCES or another permission error | Do not use sudo. Fix your npm global prefix, or manage Node.js with nvm. |
| Download fails or hangs | A network issue. Behind a proxy, set export https_proxy=http://127.0.0.1:7890 ($env:https_proxy="http://127.0.0.1:7890" on Windows) and rerun the install command. |
| Windows SmartScreen blocks the installer | Click "More info" → "Run anyway". |