How it works
Zero code to production
Ten steps. Each one is marked with what actually runs today — this is a v1 built against a real deadline, and the parts that are still a sketch are labelled as such.
Who actsStepStatus
You
01
liveOpen the project and start talkingNo template picker. A file tree on the left, a chat in the middle. You say what you want changed — the same conversation you would have in your editor.
You
02
partly builtPick the harness and modelClaude Code on Sonnet today. The picker persists your choice to the session and it shows up everywhere the agent is named.
Agent
03
liveIt reads the project, then plansThe agent explores the real repository in a cloud sandbox and comes back with a plan. Nothing has been written at this point — not by convention, but because plan mode routes every write through an approval callback that blocks until a human answers.
You
04
liveApprove, and it goes to autoApproval resolves that callback. The agent then edits, builds and finishes without stopping at each step. Anyone in the session can interrupt; it stops at a safe point and the sandbox stays warm.
Maldives
05
not built yetScanners sit in the pathSecrets, dependency advisories, prompt injection, dangerous tool calls — each off, alerting or blocking.
Maldives
06
liveIt builds before it shipsEvery run builds the project first. If the build breaks, the agent gets the error back and takes one attempt at fixing it. If it still fails, the version is saved red rather than deployed broken.
Maldives
07
not built yetIt tests itself in the cloudThe app driven end to end in a browser and on phone emulators, with a video per run. No video, no pass.
Teammates
08
liveAnyone drops inSame link, same chat. They watch it stream live, queue an instruction while it is mid-turn, or interrupt. One chat, so there is nothing to reconcile afterwards.
Maldives
09
liveVersion saved, preview deployedEvery run deploys to its own immutable URL, pass or fail — a failing build is still worth opening. Only a green run moves the shared link, so a teammate’s bookmark never breaks mid-run.
Maintainer
10
livePromote to productionThe one deliberate gate. Maintainers promote; editors request it and the request appears live in everyone else’s window. Promotion is a real alias move — the shared host starts serving that version.
Where it is freeInside the chat: reading, planning, writing, building, previewing. Nobody approves anything.
Where it is gatedLeaving the chat: promoting to production. Role-based, one gate.
What we are not claimingRoles are a product demonstration here, not a security boundary — anyone with this link can take any seat. Do not put real data in it.