コンテンツにスキップ

Install

このコンテンツはまだ日本語訳がありません。

Already followed Getting Started? You’re all set — this page is for alternative install methods, platform-specific instructions, and maintenance.

  • Node 22+ (the installer script will install it if missing)
  • macOS, Linux, or Windows
  • pnpm only if you build from source
On Windows, we strongly recommend running CoderClaw under [WSL2](https://learn.microsoft.com/en-us/windows/wsl/install). The **installer script** is the recommended way to install CoderClaw. It handles Node detection, installation, and onboarding in one step. Downloads the CLI, installs it globally via npm, and launches the onboarding wizard.
<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).
If you already have Node 22+ and prefer to manage the install yourself:
<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>
For contributors or anyone who wants to run from a local checkout.
<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).
Containerized or headless deployments. Rootless container: run `setup-podman.sh` once, then the launch script. Declarative install via Nix. Automated fleet provisioning. CLI-only usage via the Bun runtime.

Verify everything is working:

Terminal window
coderclaw doctor # check for config issues
coderclaw status # gateway status
coderclaw dashboard # open the browser UI

If you need custom runtime paths, use:

  • CODERCLAW_HOME for home-directory based internal paths
  • CODERCLAW_STATE_DIR for mutable state location
  • CODERCLAW_CONFIG_PATH for config file location

See Environment vars for precedence and full details.

Quick diagnosis:
Terminal window
node -v
npm -v
npm prefix -g
echo "$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):

Terminal window
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).

Keep CoderClaw up to date. Move to a new machine. Remove CoderClaw completely.