What is Zozo?
Zozo is a harness that orchestrates vendor agent runtimes — Claude Code (via the Claude Agent SDK) and Codex (via codex exec --json) — so subscription-backed coding agents can be driven programmatically instead of only interactively.
A few things Zozo is not:
- It is not a model API client. Zozo never calls a vendor's raw completions API; every Run happens inside a vendor Runtime the harness wraps in a Provider, on that Runtime's own subscription auth.
- It is not a chat product. The unit of work is a Run inside a Thread, and every Run's output streams into one append-only Event journal that is the durable, replayable source of truth for that Thread.
- It is not an agent-to-agent bus. When more than one agent needs to coordinate, a caller scripts the turn-taking explicitly.
Where to go next
- Quickstart — already have an invite? Go from sign-up to your first Run streaming.
- Core concepts — the vocabulary this documentation uses throughout: Provider, Runtime, Thread, Run, Event.
- Tenant concepts — Two surfaces, Work model, Auth & consent, Quotas, and Data & privacy: what the control-plane/Stack split means for you, and why.
- Task guides — how-only walkthroughs for specific things you'll do: connect a personal subscription credential, reconnect after a credential alert, manage billing, export your data, close your account, check break-glass shell access, and check network quarantine.
- Tenant reference — the flat lookup: billing lifecycle + grace, the two quotas, export-archive contents, and Credential kinds, each guarded against drift.
This site is an early seed — more sections land as the harness's own documentation (parent: issue #505) fills in, one already-shipped feature at a time (see this site's own README.md).