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
pnpmonly if you build from source
On Windows, we strongly recommend running WednesdayAI under WSL2.
Install methods
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;
- macOS / Linux / WSL2
- Windows (PowerShell)
- macOS / Linux / WSL2
- Windows (PowerShell)
- macOS / Linux / WSL2
- Windows (PowerShell)
--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.npm / pnpm
npm / pnpm
If you already have Node 24+ and prefer to manage the install yourself:
- npm
- pnpm
npm install-scripts warnings?
npm install-scripts warnings?
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-scriptsonly works for project installs; it has no effect on global installs.
From source
From source
For contributors or anyone who wants to run from a local checkout.For deeper development workflows, see Setup.
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
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:OPENCLAW_HOMEfor home-directory based internal pathsOPENCLAW_STATE_DIRfor mutable state locationOPENCLAW_CONFIG_PATHfor config file location
Troubleshooting: openclaw not found
PATH diagnosis and fix
PATH diagnosis and fix
Quick diagnosis:If On Windows, add the output of
$(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):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.