Wilmo in your terminal

Node.js 20 or newer. Run it with npx, or install it once.

npx @wilmo/cli login

# or
npm install -g @wilmo/cli
wilmo login

wilmo login opens your browser. Sign in to Wilmo as an organization admin and allow the Wilmo CLI. It then reads every team of the organization, read-only. The sign-in is stored in ~/.config/wilmo/credentials.json, readable by you only, and refreshes itself.

To use a team API key or an organization key instead, pass it, or read it from stdin with -:

wilmo login --api-key -  < key.txt

# or, for one shell or CI, without storing anything
export WILMO_API_KEY=...

wilmo whoami shows who you are signed in as. wilmo logout revokes the sign-in and forgets it.

Run a tool as wilmo <resource> <keyword>, with its input as --field value. The CLI matches the tool by its name, so tickets list runs list_tickets. When a name is ambiguous it lists the candidates instead of guessing.

# What you may call
wilmo tools

# The teams of your organization
wilmo teams list

# Open tickets about refunds, newest first
wilmo tickets list --q refund --status open --limit 10

# One conversation
wilmo ticket get --ticket_id <ticket_id>

# Any tool by its exact name, input as JSON
wilmo call list_tickets --json '{"channel":"email","limit":5}'

Every public command, and the tool it runs:

Every operation in the API reference shows its CLI command and its flags.

In a terminal the CLI prints a table. In a pipe it prints JSON, so it composes with jq. Choose with --output.

wilmo tickets list --status open --output json | jq '.tickets[].subject'

Pin the API version a script was written for, so its output never changes under it. The first version is 2026-11-06.

wilmo tickets list --api-version 2026-11-06