mao

fan-out / fan-in / organizer

One prompt. Every coding agent. One reconciled answer.

Mao sends one prompt to Claude Code, Codex, OpenCode, Cursor Agent, Antigravity and Pi at once. Each agent then revises its answer after reading the others, and an organizer agent merges them into one document. A hosted console tracks agent sessions on every machine running a Mao worker.

How it works

Invite-only. Sign in with an approved Latent Byte account.

No account yet? Join the waitlist and we will email you when a spot opens.

mao run --prompt task.md -a claude,codex,pi,opencodesample
task.md Find why the nightly export drops rows and propose a fix.
fan-out, concurrent
claude
codex
pi
opencode
fan-in, reconcile
each agent reads the other answers and revises its own
organizer, merge
merged.md
One organizer agent merges the revised answers into a single document.

console

Every agent session, on every machine, in one view

Workers report which agents are running where, including sessions you started by hand in a terminal. For most agents, turn status is read from the agent's own transcript, so you can see who is thinking, running a tool, or waiting on you.

Topologysample data
workstationmacOS
3 sessions
  • claudebilling-serviceterminalexecuting ยท Bash
  • codexbilling-servicemao-launchedwaiting_input
  • pidocs-siteterminalidle
build-boxLinux
2 sessions
  • opencodemobile-appmao-launchedthinking
  • antigravitymobile-appmao-launchedidle

architecture

The browser asks. Workers do.

The hosted console never reaches into your machines. It queues typed commands in a Postgres registry, and the worker on each machine claims its own work.

  1. 01Hosted console

    Every console API call needs a verified Latent Byte login and an operator allowlist entry. Actions become typed worker commands.

    topology_refreshagent_probesession_handoff
  2. 02Postgres registry

    Durable record of sessions, commands and machine state. Schema migrations are append-only, checksummed, and guarded in CI.

    mao_worker_commandsmao_sessionsmao_machine_status
  3. 03Per-machine worker

    Claims commands for its own machine under a renewable lease, runs local agents, and reports machine and session topology. If a worker dies, its commands return to the queue.

    FOR UPDATE SKIP LOCKEDlease renewaltopology report

beyond the terminal

Start and steer work from where you already are

GitHub mentions

Mention the Mao app on an issue or pull request. Allowed users' requests become queued jobs that a worker runs in a PR workspace.

Discord commands

Owner-only slash commands start, prompt, stop and hand off agent sessions from a phone.

Reviewable artifacts

Agents publish HTML plans and reports as immutable revisions. Reviewers annotate them in a sandboxed preview.

Session handoffs

Package a session's context so a fresh agent, even a different one, continues it in a terminal or in Discord.

guardrails

Built so the web tier stays boring

No shell in the browser

The UI only calls HTTP APIs. It never runs commands or reads files on your machines.

Credentials stay on workers

Agent logins and worker credentials stay on the machine. Session text is redacted before it reaches the browser.

Contracts are checked in

API contracts are committed OpenAPI snapshots. CI fails if the server or the generated TypeScript types drift.

Real CLIs, not wrappers

Each agent runs as its own CLI through a small subprocess runner, with per-agent timeouts and retries.