Checkout Structure
A checkout is a local directory holding one agent. Afterapollo agent import or apollo agent create, it looks like this:
Open the agent folder as your coding-tool project root so the skill packs are discovered. The skill packs, schemas, and
AGENTS.md come from the runtime the checkout’s version runs on: apollo pull refreshes them with the program, and apollo skills update refreshes them alone (skip them on pull with --no-skills / --no-schemas).The .apollorc Binding
.apollorc
.apollorc walking up from your current directory selects the agent. Commands run inside a checkout use its binding for organization, project, agent, version, and runtime.
Don’t edit
.apollorc manually — apollo agent use / import, apollo project use, apollo version use, apollo pull --tag, and apollo runtime use maintain it, and apollo push updates the tag on every push.User Configuration (~/.apollo/)
Environment Variables
Environment variables override file-based configuration — useful for CI/CD pipelines.Output & Exit Codes
With the global--json flag, every command emits exactly one envelope on stdout (the one exception, apollo chat --events, first streams one JSON line per frame, then the envelope):
validate finds errors, a --follow run ends red, push refuses an invalid program — error.detail carries the same object a success would put in data. Either envelope can also carry update, skills_update, and runtime_update fields when something is out of date; they’re additive, so a consumer that never looks for them sees the envelope it always did.
--verbose streams one redacted line per API request to stderr (auth/token/key/secret values never appear); the TUI shows the same stream live in its activity drawer.
Next Steps
Command Reference
Full reference for all CLI commands.
Workflows
Common development workflows and patterns.