CLI for agents

The bird CLI is a single binary built to be driven by an agent. Output is JSON by default, errors go to stderr, and exit codes carry the failure category.

Get set up

The fastest path is to set up your coding agent: paste one prompt and your agent installs the CLI and Bird's skills for you. To install it by hand:

Exemple de code

curl -fsSL https://cli.bird.com/install.sh | sh
bird auth login

bird auth login runs a browser OAuth flow and stores a grant bound to one workspace and its region, so you do not configure an API key or host. bird auth status always exits 0 and reports valid: true once the token works. bird whoami returns the signed-in user (ID, email, and name), which is the identity the agent acts as and the MCP whoami tool returns.

The contract

JSON to stdout; errors and diagnostics to stderr; never mixed.
Exit codes: six semantic codes covering usage, not-found, auth, conflict, transient failures, and a general fallback. See the full table in CLI.
Mutations take input from flags, a JSON body via --body-file - (stdin), or both, with the flag winning.
--example prints a valid request body, --dry-run previews the request without sending, and --idempotency-key makes a retry safe.

Next steps

Set up your coding agent: paste a prompt and your agent installs the CLI and skills.
Agent skills: what each skill teaches your agent.
CLI reference: every command, flag, and output shape.
MCP server: the same Bird surface as MCP tools, for agents that call tools instead of running a shell.