a2wave-cli

# a2wave CLI Use the `a2wave` command-line tool to manage the a2wave Agent orchestration platform. ## Checks Before You Start 1. Before debugging authentication, URL, token, or backend connectivity issues, run `a2wave status` first. 2. If the URL is not yet configured, set it with `a2wave config set-url <url>`; you can also pass `--url <url>` on a single command, or set `A2WAVE_URL`. 3. Login and URL configuration are two separate things: `a2wave login` runs OAuth SSO via your identity provider (IdP) and writes local credentials. 4. For resource arguments that accept `<id|name>`, you can pass an ID or an exact name; an ID is used directly, while a name is resolved via the list API. ## Platform Install (setup) ```bash a2wave setup --image a2wave:latest # interactive: dir + port prompts, then docker compose up + health wait a2wave setup --yes --image a2wave:latest # non-interactive with defaults (~/a2wave, port 3502) a2wave setup --yes --image a2wave:latest --dir /srv/a2wave --port 3510 --base-url http://192.168.1.10:3510 a2wave setup --no-start --image a2wave:latest # generate .env + docker-compose.yml only a2wave setup --yes --database-url postgres://a2wave:pw@db.internal:5432/a2wave # EXPERIMENTAL: external PostgreSQL backend a2wave setup --yes --with-postgres # EXPERIMENTAL: bundle a postgres:16-alpine sidecar (password generated into .env) a2wave setup --upgrade --image a2wave:1.4.0 # move an existing install to a new image, keeping its data a2w...