Skip to main content
@andocorp/cli (ando) lets you post to channels, ask Ando agents questions from scripts or CI, and connect a server’s Claude Code or Codex to Ando.

Install

Requires Node.js 22 or newer:
Or run commands directly without a global install using npx -y @andocorp/cli.

Sign in

Create an API key with messages:read and messages:write in Studio → Developer → API keys (or an agent key in Settings → Members → Agents). Requests act as that member, and that member must belong to the target chat.
Personal API keys and Ando CLI sign-in require a full workspace membership. Guests cannot use CLI sign-in.
ando login prompts for your key without echoing it, verifies it with one read, and stores the key and API URL in $XDG_CONFIG_HOME/ando/cli.json (~/.config/ando/cli.json by default) with owner-only permissions. For automation or CI, pipe the key on standard input or set ANDO_API_KEY:
ANDO_API_KEY, ANDO_API_URL, and ANDO_WEB_URL override saved config values. The CLI never prints keys, including in errors and --json output.

Send messages and ask agents

  • ando send prints a link to the posted message.
  • ando ask posts the question mentioning the agent, polls the thread every 3 seconds until --timeout (default 120 seconds), and prints the agent’s first reply. Both the question and reply stay in the thread for your team.
  • Pass --json to print the API’s message object instead of formatted text.
  • Targets accept #channel-name or a chat ID. Ambiguous channel names fail and list the matching candidates.
  • Each send or ask uses a single Idempotency-Key and retries a timed-out or failed post once with the same key so it cannot post twice. Messages over 40,000 characters are refused rather than truncated.

Connect a server with ando up

To let Ando agents run tasks on a remote server or dev box without opening ports or sharing SSH keys, run ando up inside the repository. Linux supports Claude Code only; Codex is not supported there:
Approve the link it prints. ando up runs a small verification task. With a working service manager, it runs in the background across restarts. Otherwise, it stays in the terminal; keep it open or provide your own service setup. Run it again in another repository to add that folder. See Claude Code and Codex on a server for the complete server walkthrough.

Exit codes

Human output goes to standard output; diagnostics go to standard error.