The design choice that matters is that MCP calls do not own the process: a detached supervisor does, so a run keeps going through a harness restart and is picked up afterwards by run id. That is what makes real parallelism practical — start several runs, wait on an event condition across all of them rather than polling each transcript, and take the terminal view only when one asks for attention. Reviews follow the same shape: start the typed run, wait, then read the validated artifact rather than scraping the transcript.
A control plane in front of the Antigravity CLI. Runs are started as detached, supervised processes with their own state, logs and transcript, so the harness can restart, a call can time out, and the work carries on.
- Runs started in a workspace as a normal task, or as a persistent interactive conversation, or continued against an exact conversation id
- A run that cannot report success until a named file is non-empty, for work whose whole point is the artifact
- Sparse waiting instead of polling — wait on any_attention, any_terminal, all_terminal or any_event across a list of runs, and wake only when one of them happens
- One observation surface with four views: merged state across runs, or status, transcript or terminal for a single run, all bounded in size
- Input sent into a live run, with optional guards that reject the write if the event or transcript cursor moved after you last looked
- Runs cancelled cleanly, taking down the process group rather than orphaning it, and final results read back whole or in byte ranges
- Typed review runs over a commit, over branch and working-tree changes, or over a named file list, each producing an artifact that a companion tool validates and summarises
- Goals that create named targets and run them with bounded parallelism, inspected as one coordinated batch
- Bounded diagnostics over the bridge and the CLI, including a doctor action for when a run reports that authentication is needed
The Antigravity CLI (agy) installed and already signed in — agy --version only proves the binary exists, so run agy models first and complete the browser login if it asks. Also uv/uvx, and tmux on macOS, since foreground runs live in persistent tmux sessions that a terminal can attach to without killing the agent. AGY_CMD points the bridge at that authenticated agy executable. It runs over stdio as uvx codex-agy-bridge@latest, and Codex CLI installs it with codex mcp add. When a run still hits auth, it comes back with status="auth_required" and opens a visible sign-in session. MIT.
One command — codex mcp add codex-agy-bridge \ --env AGY_CMD="$(command -v agy)" \ -- "$(command -v uvx)" codex-agy-bridge@latest