Install the CLI

Everything you do with WAID goes through the waid command-line tool. Install it, then confirm your environment with waid doctor.

Download waid#

Every build is published on the downloads page with its size and sha256, so you can verify what you fetched and pin an exact version in CI. No sign-up is needed to download. Homebrew and npm packages are not available yet.

PlatformDownloadShape
macOS (Apple Silicon)waid-macos-arm64.pkgInstaller; puts waid in /usr/local/bin
Windows (x64)waid.exeThe binary itself — no installer
macOS (Intel)—Not built yet
Linux—Not built yet

macOS#

Double-click the .pkg. It installs waid to /usr/local/bin, which is already on your PATH.

If macOS doesn't open the package on a plain double-click, Control-click it and choose Open.

Windows#

The download is the executable, not a setup program — nothing installs it for you. Put waid.exe on your PATH yourself:

powershell
# A folder of your own for command-line tools
mkdir "$env:LOCALAPPDATA\waid"
Move-Item .\waid.exe "$env:LOCALAPPDATA\waid\waid.exe"
 
# Add it to your user PATH; takes effect in new terminals
[Environment]::SetEnvironmentVariable(
'Path',
[Environment]::GetEnvironmentVariable('Path', 'User') + ";$env:LOCALAPPDATA\waid",
'User'
)

If Windows prompts before the first run, choose More info → Run anyway. To confirm you have the exact published build, compare its checksum against the sha256 on the downloads page:

powershell
Get-FileHash .\waid.exe -Algorithm SHA256

Open a new terminal after changing PATH, or the current one won't find waid.

Verify the install:

bash
waid --help
waid version
waid help app
waid help service

Sign in to ICE#

Scaffolding, development, builds, and remote synchronization require an ICE session. Sign in through Splenta ID and check the shared CLI/Studio session:

bash
waid login
waid session --json

Pass --tenant <key> when selecting a tenant. Local app/service MCP generation does not require login. See the CLI reference.

Prerequisites#

You only need the toolchain for what you actually build:

  • Node.js + npm: required for every project. Your app is a standard Vite project, and WAID runs npm run build to produce the web bundle.
  • Android: the Android SDK (ANDROID_HOME / ANDROID_SDK_ROOT) and adb, to build and install Android apps.
  • iOS: Xcode and its command-line tools (macOS only).
  • Desktop: no extra setup beyond a working WAID install for most hosts.

The browser target needs no native toolchain; WAID still needs Node and an ICE session.

Check your setup#

bash
waid doctor # general environment health check
waid doctor android # Android SDK / adb / connected devices
waid doctor ios-signing # iOS signing: teams, provisioning profiles

Run waid doctor before your first native build to catch a missing SDK early.