Skip to main content

Installer internals

Velaclaw ships three installer scripts, served from velaclaw.ai.

Quick commands

If install succeeds but velaclaw is not found in a new terminal, see Node.js troubleshooting.

install.sh

Recommended for most interactive installs on macOS/Linux/WSL.

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 by default

Checks Node version and installs Node 24 if needed (Homebrew on macOS, NodeSource setup scripts on Linux apt/dnf/yum). Velaclaw still supports Node 22 LTS, currently 22.14+, for compatibility.
3

Ensure Git

Installs Git if missing.
4

Install Velaclaw

  • npm method (default): global npm install
  • git method: clone/update repo, install deps with pnpm, build, then install wrapper at ~/.local/bin/velaclaw
5

Post-install tasks

  • Refreshes a loaded gateway service best-effort (velaclaw gateway install --force, then restart)
  • Runs velaclaw doctor --non-interactive on upgrades and git installs (best effort)
  • 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 an Velaclaw checkout (package.json + pnpm-workspace.yaml), the script offers:
  • use checkout (git), or
  • use global install (npm)
If no TTY is available and no install method is set, it defaults to npm and warns. The script exits with code 2 for invalid method selection or invalid --install-method values.

Examples (install.sh)


install-cli.sh

Designed for environments where you want everything under a local prefix (default ~/.velaclaw) and no system Node dependency. Supports npm installs by default, plus git-checkout installs under the same prefix flow.

Flow (install-cli.sh)

1

Install local Node runtime

Downloads a pinned supported Node LTS tarball (the version is embedded in the script and updated independently) to <prefix>/tools/node-v<version> and verifies SHA-256.
2

Ensure Git

If Git is missing, attempts install via apt/dnf/yum on Linux or Homebrew on macOS.
3

Install Velaclaw under prefix

  • npm method (default): installs under the prefix with npm, then writes wrapper to <prefix>/bin/velaclaw
  • git method: clones/updates a checkout (default ~/velaclaw) and still writes the wrapper to <prefix>/bin/velaclaw
4

Refresh loaded gateway service

If a gateway service is already loaded from that same prefix, the script runs velaclaw gateway install --force, then velaclaw gateway restart, and probes gateway health best-effort.

Examples (install-cli.sh)


install.ps1

Flow (install.ps1)

1

Ensure PowerShell + Windows environment

Requires PowerShell 5+.
2

Ensure Node.js 24 by default

If missing, attempts install via winget, then Chocolatey, then Scoop. Node 22 LTS, currently 22.14+, remains supported for compatibility.
3

Install Velaclaw

  • npm method (default): global npm install using selected -Tag
  • git method: clone/update repo, install/build with pnpm, and install wrapper at %USERPROFILE%\.local\bin\velaclaw.cmd
4

Post-install tasks

  • Adds needed bin directory to user PATH when possible
  • Refreshes a loaded gateway service best-effort (velaclaw gateway install --force, then restart)
  • Runs velaclaw doctor --non-interactive on upgrades and git installs (best effort)

Examples (install.ps1)

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.

Troubleshooting

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.
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).
The scripts default SHARP_IGNORE_GLOBAL_LIBVIPS=1 to avoid sharp building against system libvips. To override:
Install Git for Windows, reopen PowerShell, rerun installer.
Run npm config get prefix and add that directory to your user PATH (no \bin suffix needed on Windows), then reopen PowerShell.
install.ps1 does not currently expose a -Verbose switch. Use PowerShell tracing for script-level diagnostics:
Usually a PATH issue. See Node.js troubleshooting.