Installation

Commando is shipped as a single npm package, sui-commando, that runs on Windows, Linux, and macOS. The postinstall hook handles binary downloads, PATH patching, and external CLI config bootstrap.

Supported platforms

Install

npm install -g sui-commando@beta

That's it. The hook will:

1. Detect OS + arch (bootstrap/platform.ts).
2. Download .tgz archives directly from the upstream Mysten Labs GitHub releases.
3. Extract them with the system tar and set the executable bit on Unix.
4. Patch your shell PATH (Windows registry; ~/.bashrc / ~/.zshrc / ~/.bash_profile / ~/.profile on Unix).
5. Bootstrap the Sui wallet (~/.sui/sui_config/client.yaml) and Walrus client config (~/.config/walrus/client_config.yaml, testnet default).
6. Generate ~/.commando/skills/AGENT.md from each binary's --help output.

Verify

cmdo doctor

Expected output (Linux example):

node: v20.x
platform: linux-x86_64
cpu: <model>
install root: /root/.commando
bin dir: /root/.commando/bin [ok]
skills file: /root/.commando/skills/AGENT.md [ok]
bin on PATH: yes
sui: present (+x)
walrus: present (+x)
site-builder: present (+x)
LLM provider: OpenAI (model=gpt-4o-mini) - key configured
doctor: all checks passed.

If bin on PATH is NO, open a new terminal (or source ~/.bashrc / source ~/.zshrc).

Where things live

Re-running the install

cmdo bootstrap is idempotent — it skips files that are already present and verified. Use it to:

• Recover from a partial install (network drop mid-download).
• Pick up a new binary version after upgrading the npm package.
• Re-patch PATH after a fresh shell config.

cmdo bootstrap

To force a full re-download, delete ~/.commando/bin/ first.

Skipping the postinstall (CI / Docker)

The 900 MB download is unwelcome in CI pipelines. Skip it with:

CMDO_SKIP_BOOTSTRAP=1 npm install -g sui-commando@beta

Then run cmdo bootstrap manually when (and where) you actually need the binaries — e.g., in a separate stage or only on the production runner.

Any non-empty value other than 0 or false enables the skip.

Tuning the downloader

The downloader supports HTTP Range resume, so a half-finished .part file is reused on the next attempt.

Optional: R2 manifest mirror (advanced)

By default, every install pulls binaries straight from upstream GitHub releases — no operator-owned mirror is involved. For CI mirrors, air-gapped enterprise installs, or future paid tiers we keep an opt-in R2 manifest path that adds per-binary SHA256 provenance.

Enable it by setting both of these env vars (Windows only — the legacy R2 manifest only ever covered Windows):

export CMDO_MANIFEST_URL="https://your-r2-worker.example.com/object?key=manifests/commando-x.y.z.json"
export CMDO_R2_TOKEN="<bearer-token-the-worker-accepts>"

When both are present, npm install -g sui-commando@beta fetches the manifest, verifies SHA256 per binary, and installs from there. When either is missing, the install transparently falls back to GitHub-direct.

Uninstall

npm uninstall -g sui-commando
rm -rf ~/.commando        # binaries, skills, sandbox
# Optional - if you don't use these CLIs elsewhere:
rm -rf ~/.sui ~/.config/walrus

On Windows, also remove %USERPROFILE%\.commando and the PATH entry that the installer added (the registry edit is reversed on next cmdo bootstrap if you reinstall later).

Next