Install
Install
Section titled “Install”Already followed Getting Started? You’re all set — this page is for alternative install methods, platform-specific instructions, and maintenance.
System requirements
Section titled “System requirements”- Node 22+ (the installer script will install it if missing)
- macOS, Linux, or Windows
pnpmonly if you build from source
Install methods
Section titled “Install methods”<Tabs> <Tab title="macOS / Linux / WSL2"> ```bash curl -fsSL https://coderclaw.ai/install.sh | bash ``` </Tab> <Tab title="Windows (PowerShell)"> ```powershell iwr -useb https://coderclaw.ai/install.ps1 | iex ``` </Tab></Tabs>
That's it — the script handles Node detection, installation, and onboarding.
To skip onboarding and just install the binary:
<Tabs> <Tab title="macOS / Linux / WSL2"> ```bash curl -fsSL https://coderclaw.ai/install.sh | bash -s -- --no-onboard ``` </Tab> <Tab title="Windows (PowerShell)"> ```powershell & ([scriptblock]::Create((iwr -useb https://coderclaw.ai/install.ps1))) -NoOnboard ``` </Tab></Tabs>
For all flags, env vars, and CI/automation options, see [Installer internals](/install/installer).<Tabs> <Tab title="npm"> ```bash npm install -g coderclaw@latest coderclaw onboard --install-daemon ```
<Accordion title="sharp build errors?"> If you have libvips installed globally (common on macOS via Homebrew) and `sharp` fails, force prebuilt binaries:
```bash SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm install -g coderclaw@latest ```
If you see `sharp: Please add node-gyp to your dependencies`, either install build tooling (macOS: Xcode CLT + `npm install -g node-gyp`) or use the env var above. </Accordion> </Tab> <Tab title="pnpm"> ```bash pnpm add -g coderclaw@latest pnpm approve-builds -g # approve coderclaw, node-llama-cpp, sharp, etc. coderclaw onboard --install-daemon ```
<Note> pnpm requires explicit approval for packages with build scripts. After the first install shows the "Ignored build scripts" warning, run `pnpm approve-builds -g` and select the listed packages. </Note> </Tab></Tabs><Steps> <Step title="Clone and build"> Clone the [CoderClaw repo](https://github.com/SeanHogg/coderClaw) and build:
```bash git clone https://github.com/SeanHogg/coderClaw.git cd coderClaw pnpm install pnpm ui:build pnpm build ``` </Step> <Step title="Link the CLI"> Make the `coderclaw` command available globally:
```bash pnpm link --global ```
Alternatively, skip the link and run commands via `pnpm coderclaw ...` from inside the repo. </Step> <Step title="Run onboarding"> ```bash coderclaw onboard --install-daemon ``` </Step></Steps>
For deeper development workflows, see [Setup](/start/setup).Other install methods
Section titled “Other install methods”After install
Section titled “After install”Verify everything is working:
coderclaw doctor # check for config issuescoderclaw status # gateway statuscoderclaw dashboard # open the browser UIIf you need custom runtime paths, use:
CODERCLAW_HOMEfor home-directory based internal pathsCODERCLAW_STATE_DIRfor mutable state locationCODERCLAW_CONFIG_PATHfor config file location
See Environment vars for precedence and full details.
Troubleshooting: coderclaw not found
Section titled “Troubleshooting: coderclaw not found”node -vnpm -vnpm prefix -gecho "$PATH"If $(npm prefix -g)/bin (macOS/Linux) or $(npm prefix -g) (Windows) is not in your $PATH, your shell can’t find global npm binaries (including coderclaw).
Fix — add it to your shell startup file (~/.zshrc or ~/.bashrc):
export PATH="$(npm prefix -g)/bin:$PATH"On Windows, add the output of npm prefix -g to your PATH.
Then open a new terminal (or rehash in zsh / hash -r in bash).