Agents in the cloud with ganja as the control plane

What it does

Subagents, teammates and parallel workstreams run in the cloud, and ganja becomes their control plane. The terminal stays the cockpit, and the only agent process on the user's machine is the one the user talks to.

Source

Outside beads: the README's opening paragraph (README.md:3-4) and its Design section (README.md:16-18).

File and line references in this issue are to main as of 75a7a92.

Against the three criteria

• Direction (README): This is the README's direction: "a cloud-native AI coding agent that lives in your terminal" (README.md:3-4), and everything ganja fans out "is headed for the cloud, with ganja as their control plane" (README.md:16-18).
• Today's terminal users: Every teammate runs on the lead's machine today — in-process, in a tmux pane or as a foreign CLI; ganja serve with attach is the only road that runs the engine away from the terminal.
• Evidence: Nothing of it is built; the README says so (README.md:31-34). Three pieces of groundwork exist: the teammate backend seam of D538 and D539; the rule that ganja-serve never links ganja-teammate-local, because the closure ganja serve ships is the closure a cloud worker will ship (crates/AGENTS.md:38); and the -local in ganja-teammate-local, which reserves the name of a cloud sibling.

Depends on

No other idea, but it needs parts that do not exist: a control-plane service, a cloud-side execution environment, a transport between the terminal and workers, a scheduler for many workers, authentication and billing. It blocks #65 and #64.

Verdict

• Verdict: do
• Size: XL — a new execution environment and an external service.
• Exception to the probe rule: no.
• Date: 2026-09-19
• Verdict ticket: #48

Theme: #51

Start with README.md:3-4 and README.md:16-18, then read crates/AGENTS.md:38 and the teammate backend seams from D538/D539; use ganja serve with attach as the current remote-execution entry point. Done means the control-plane service, cloud execution environment, terminal-worker transport, multi-worker scheduler, authentication, and billing exist and support the stated cloud direction.