Skip to main content
The Apollo CLI (@aui.io/apollo) is the operator console for Apollo agents. One install gives you two surfaces: a scriptable command-line interface (apollo <command>) and a full-screen terminal UI (bare apollo) for the author/test loop. It enables a local-first development workflow: import an agent as a typed YAML program, edit it in your IDE with schema support, validate, test against the live runtime, and push changes back as new versions.
The CLI is designed to be driven by coding agents as much as by humans. Every command is fully non-interactive with a --json output mode, and importing an agent installs authoring skill packs for Cursor and Claude Code — so tools like Cursor, Claude Code, and the Agent Builder can author, run, and iterate on an agent end-to-end.

​
Quick Start

​
Mental Model

Context is positional: the nearest .apollorc walking up from your current directory selects the agent you are working on. apollo status always tells you where you stand.

​
Key Features

Import an agent as a typed YAML program under bundle/src/. Edit it in VSCode, Cursor, or any editor — the checkout ships JSON Schemas for every file. Version control is git: diffs against policies/global.yaml are real diffs, and rollback is git revert.
apollo validate checks the local program deterministically before any push. apollo diff compares your working tree with the last baseline (or the selected remote version with --remote), and apollo push --dry-run previews exactly what would ship.
Talk to your agent against the real Apollo-1 runtime with apollo chat — including your local, unpushed edits via --local . — and read the decision trace with --trace. Inspect full conversations with apollo thread messages and apollo thread trace.
Ask the grounded authoring advisor a question with apollo advise, run a complete build turn with apollo build (gated: green pushes a new version, red refuses), and grade the agent with apollo regress and apollo evaluate, run server-side over your checkout.
Manage the full lifecycle — draft, publish, archive — with apollo version. Publishing is also the rollback operation: re-publishing an older version makes it live again.
Create knowledge hubs and upload documents with apollo kb, spin up a per-agent test database with apollo mockdb, and store credentials referenced from connections.yaml with apollo vault.
Replay the scripted suite through the simulator with apollo regress, and go looking for what no script covers with apollo evaluate — improvising simulated callers planned from your guidelines and graded by a judge. Both measure against the case bank in bundle/build/cases.yaml.
Bare apollo on a TTY launches the full-screen terminal UI: an Author mode (validate, diff, push, pull, versions, resources) and a Talk mode (converse with the running agent), with an action palette (Ctrl+K) that shows the CLI equivalent of every operation.

​
The TUI in One Minute

Bare apollo on a TTY launches the TUI (apollo tui and --tui force it; any subcommand, --json, --no-input, or a non-TTY always runs the CLI). It has two primary modes — Author (the program cockpit) and Talk (converse with the running agent): In Author, single letters run quick actions (v validate · d diff · p push · l pull · r versions · m resources · o open in IDE), and free text is a copilot instruction to the author backend. In Talk, the composer sends everything to the agent verbatim.
The TUI runs on Bun. Without Bun installed, apollo prints install guidance and the CLI remains fully usable.

​
Get Started

Installation

Install the CLI and authenticate with your account.

Hello world

Build your first agent end to end, from empty folder to published version.

Command Reference

Full reference for every CLI command.

Configuration

Checkout structure, config files, and environment variables.

Workflows

Common development workflows and best practices.