Zozo

There are two ways in. The first is an Intake Session: you describe a feature in plain terms in the Dashboard and Zozo turns it into an issue plan. Small mode lets the agent make and explain the design decisions, Medium runs one grilling conversation for the judgments that remain yours, and Large (Wayfinder) charts open decisions as tickets resolved over several days. Every intake is read-only until you choose Publish, which creates real issues in dependency order. The second way in is simply labelling an existing issue ready-for-agent.

Once Auto-dispatch is on, Zozo selects eligible issues by priority. It checks for newly selectable work every five minutes, starts the next issue as soon as a run slot frees up, and a reconciler rechecks blockers on every watched project once a minute. Each attempt runs in a disposable cell with its own worktree and branch, where the agent reads the repo, edits files, runs your build and tests, and commits. If an issue turns out to be missing a decision that is not in the issue, the docs or the code, the attempt pauses, asks you on the same thread, sends a push to your phone and waits with no timeout. When the work is done it pushes the branch and opens a pull request. Merge policy is set per project: open-PR-only waits for your review, while auto-merge verifies the tested commit against the current base branch before landing it.

• •Dependency-aware auto-dispatch - Work blocked on another issue waits, and an issue whose last blocker closes rejoins the Frontier without anyone checking. Three consecutive attempts failing for the same reason trip a circuit breaker that ends the pass and returns unstarted issues to ready, and Suspend stops new selections while letting in-flight runs finish cleanly.
• •Clarification instead of guessing - When a load-bearing decision is missing, the attempt stops, posts its question and keeps every file it has touched in its worktree. Your answer resumes the same attempt with its context intact. Decisions are written back into your own repository as CONTEXT.md and ADR files, so later clarifications have more recorded facts to check against.
• •Intake Sessions and Wayfinder - Intake modes range from letting the agent settle codebase details to a multi-day Wayfinder map whose tickets resolve by research, judgment, a disposable prototype or prerequisite work. A Prototype option builds a live prototype of a screen you describe and hands off into an intake session (GitHub projects only).
• •Append-only event journal - Every turn, tool call, command and decision is journaled as it happens, and the Dashboard runs from that same record. One click exports a manifest, the raw journal and a git bundle for every unshipped attempt, and the system refuses to discard a branch whose commits never reached a pull request unless you confirm it.
• •Dedicated, isolated infrastructure - Each customer has their own VM, and runs execute in disposable cells bounded by a permission policy. The control plane receives account state, health fields and aggregate token usage rather than code. Hosted updates roll out in health-gated waves and revert automatically if a health check fails.
• •Per-project credentials and cost tracking - Each project can pin its own credential, for example a client repository on that client's API key and personal work on your own subscription. Every run reports its tokens and cost into a daily per-provider rollup, and a subscription credential requires your explicit, recorded consent before it runs unattended.

Zozo is aimed at developers who already use Claude Code or Codex and have a backlog of reasonably well-scoped issues they would like worked while they are away from the keyboard. Solo developers can connect the subscription they already pay for and let a single run at a time pace itself against that plan's usage limits. Freelancers and consultants who bill clients for agent work get per-project API-key credentials and a daily cost rollup that can become a line item on an invoice. Small teams on GitHub, or Bitbucket Cloud with Jira Cloud, can keep a queue of issues moving without babysitting terminal sessions while a human keeps the final merge decision.

The free Local Stack suits anyone who wants to try the loop on their own machine first, with the trade-off that it stops when its terminal closes. Hosted plans are Standard at $40 per month (one run at a time, three watched projects), Plus at $50 per month (three concurrent runs, six projects) and Pro at $60 per month (five concurrent runs, twelve projects), before tax and with a 14-day money-back window. Zozo is less relevant for interactive pair-programming inside a single task, where its own site notes a terminal agent is enough, and hosted stacks are currently limited to EU regions with new signups admitted in a small daily batch.