Installer internals
WednesdayAI ships two installer scripts, served fromopenclaw.ai.
Quick commands
- install.sh
- install.ps1
If install succeeds but neither
wednesdayai nor the compatibility openclaw command is found in a new terminal, see Node.js troubleshooting.install.sh
Flow (install.sh)
1
Detect OS
Supports macOS and Linux (including WSL). If macOS is detected, installs Homebrew if missing.
2
Ensure Node.js 24+
Checks Node version and installs Node 24 if needed (Homebrew on macOS, NodeSource setup scripts on Linux apt/dnf/yum).
3
Ensure Git
Installs Git if missing.
4
Install WednesdayAI
npmmethod (default): global npm install ofwednesdayai@<version-or-tag>gitmethod: clone/update repo, install deps with pnpm, build, then install wrapper at~/.local/bin/openclaw
5
Post-install tasks
- Runs
openclaw doctor --non-interactiveon upgrades and git installs (best effort).openclawremains a compatibility binary for the same install. - Attempts onboarding when appropriate (TTY available, onboarding not disabled, and bootstrap/config checks pass)
- Defaults
SHARP_IGNORE_GLOBAL_LIBVIPS=1
Source checkout detection
If run inside a WednesdayAI checkout (package.json + pnpm-workspace.yaml), the script offers:
- use checkout (
git), or - use global install (
npm)
npm and warns.
The script exits with code 2 for invalid method selection or invalid --install-method values.
Examples (install.sh)
- Default
- Skip onboarding
- Git install
- Dry run
Flags reference
Flags reference
Environment variables reference
Environment variables reference
install.ps1
Flow (install.ps1)
1
Ensure PowerShell + Windows environment
Requires PowerShell 5+.
2
Ensure Node.js 24+
If missing, attempts install via winget, then Chocolatey, then Scoop.
3
Install WednesdayAI
npmmethod (default): global npm install ofwednesdayai@<tag>gitmethod: clone/update repo, install/build with pnpm, and install wrapper at%USERPROFILE%\.local\bin\openclaw.cmd
4
Post-install tasks
Adds needed bin directory to user PATH when possible, then runs
openclaw doctor --non-interactive on upgrades and git installs (best effort).Examples (install.ps1)
- Default
- Git install
- Custom git directory
- Dry run
- Debug trace
Flags reference
Flags reference
Environment variables reference
Environment variables reference
If
-InstallMethod git is used and Git is missing, the script exits and prints the Git for Windows link.CI and automation
Use non-interactive flags/env vars for predictable runs.- install.sh (non-interactive npm)
- install.sh (non-interactive git)
- install.ps1 (skip onboarding)
Troubleshooting
Why is Git required?
Why is Git required?
Git is required for
git install method. For npm installs, Git is still checked/installed to avoid spawn git ENOENT failures when dependencies use git URLs.Why does npm hit EACCES on Linux?
Why does npm hit EACCES on Linux?
Some Linux setups point npm global prefix to root-owned paths.
install.sh can switch prefix to ~/.npm-global and append PATH exports to shell rc files (when those files exist).Windows: "npm error spawn git / ENOENT"
Windows: "npm error spawn git / ENOENT"
Install Git for Windows, reopen PowerShell, rerun installer.
Windows: "openclaw is not recognized"
Windows: "openclaw is not recognized"
Run
npm config get prefix and add that directory to your user PATH (no \bin suffix needed on Windows), then reopen PowerShell.Windows: how to get verbose installer output
Windows: how to get verbose installer output
install.ps1 does not currently expose a -Verbose switch.
Use PowerShell tracing for script-level diagnostics:openclaw not found after install
openclaw not found after install
Usually a PATH issue. See Node.js troubleshooting.