Skip to main content

Install

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

System requirements

  • Node 24+ (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 WednesdayAI under WSL2.

Install methods

The installer script is the recommended way to install WednesdayAI. It handles Node detection, installation, and onboarding in one step.
For VPS/cloud hosts, avoid third-party “1-click” marketplace images when possible. Prefer a clean base OS image (for example Ubuntu LTS), then install WednesdayAI yourself with the installer script.

Installer script

Downloads the CLI, installs it globally via npm, and launches the onboarding wizard.
That’s it — the script handles Node detection, installation, and onboarding.To skip onboarding and just install the binary:
For all flags, env vars, and CI/automation options, see Installer internals.The hosted installers are served from the published npm tarball. The canonical origin is the pinned, versioned CDN path:
The URL pins the installer script; --version / -Tag pins the wednesdayai package it installs (both default to latest).https://unpkg.com/wednesdayai@latest/scripts/install.sh is an optional moving alias that always resolves to the newest release; the hosted install.sh URL follows it.
If you already have Node 24+ and prefer to manage the install yourself:
npm 11.16+ warns when install scripts run without an allowlist, and npm 12 blocks them outright. --allow-scripts=<list> names exactly the packages whose install scripts we trust; with the list shown above the install is warning-free on npm 12 (tested with npx npm@12 install -g).
  • npm ≤ 11.15: no allowlist mechanism — omit the flag.
  • npm 11.16: install works, but prints a warning unless the flag is present.
  • npm 12: install scripts are blocked unless the flag is present.
  • npm approve-scripts only works for project installs; it has no effect on global installs.
If you have libvips installed globally (common on macOS via Homebrew) and sharp fails, force prebuilt binaries:
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.
For contributors or anyone who wants to run from a local checkout.
1

Clone and build

Clone the WednesdayAI repo and build:
2

Install the CLI from a tarball

Build a local npm tarball and install that copy globally:
The package exposes both wednesdayai and the compatibility openclaw command.
3

Run onboarding

For deeper development workflows, see Setup.

Other install methods

Docker

Containerized or headless deployments.

Podman

Rootless container: run setup-podman.sh once, then the launch script.

Nix

Declarative install via Nix.

Ansible

Automated fleet provisioning.

After install

Verify everything is working:
If you need custom runtime paths, use:
  • OPENCLAW_HOME for home-directory based internal paths
  • OPENCLAW_STATE_DIR for mutable state location
  • OPENCLAW_CONFIG_PATH for config file location
See Environment vars for precedence and full details.

Troubleshooting: openclaw not found

Quick diagnosis:
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 wednesdayai and the compatibility openclaw command).Fix — add it to your shell startup file (~/.zshrc or ~/.bashrc):
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).

Update / uninstall

Updating

Keep WednesdayAI up to date.

Migrating

Move to a new machine.

Uninstall

Remove WednesdayAI completely.