Fix installation and runtime selection

Use this page when the shell cannot find Wago, no runtime is active, the wrong build is selected, or a cached artifact became stale.

The shell cannot find wago

If installation finished moments ago, open a new terminal. Then locate the executable:

command -v wago

If nothing appears, rerun the installer from Getting started. If two paths appear, the first one wins; remove or reorder the stale entry.

No runtime is active

The manager intentionally does not bundle one:

wago version install
wago version current
wago version which

Non-interactively:

wago version install --canary --use --no-input

The wrong variant is active

wago version switch canary --profile standard --build normal

wago version current reports version, profile, and build.

A .wago file stopped loading

Compiled artifacts are tied to Wago's format and the host architecture. Rebuild from the original Wasm:

wago build fib.wasm -o fib.wago

Distribute .wasm for portability or use wago compile for a target-specific standalone executable.

Inspect and clean caches

wago cache dir
wago cache size
wago cache prune --yes

Use wago cache clean only when you intend to regenerate the selected data.