The stages, in order
| State | Who acts | What happens |
|---|---|---|
awaiting-agent | Nobody yet | The brief exists but has not been claimed. Either no computer is assigned, the daemon is stopped, or the chosen engine is missing on that machine. |
queued | The paired computer | A machine that can run it exists and is online. The next heartbeat picks the brief up. |
planning | Lead | The Lead reads the brief and answers with a numbered list of build steps. It is told not to write code. |
awaiting-approval | You | The plan is stored and the build waits. Nothing is written to disk until you approve. |
running | Builder | A git checkpoint is taken, the plan is claimed, and the builder agent writes files inside the workspace folder. |
testing | The gate | The built page is opened in a real Chromium at desktop and phone widths. Eight checks are measured. See the browser gate. |
repairing | Repair | Only if a check failed. The failed checks become the brief for one repair pass, then the gate runs again. |
done | Nobody | Every check passed. The workspace is packed into a zip and stored, and the build can be published. |
What approval actually gates
The plan is the last cheap moment to say no. After approval the builder starts writing, so approval is not a formality: it is the point where a misread brief costs you nothing. Rejecting a plan stops the build with the state rejected and no files touched.
A plan is a numbered list of steps that can be checked in a browser. Not “make it beautiful”, but “the menu lists three drinks with prices”. That constraint exists because the gate has to verify each step, and a step nobody can measure cannot be verified.
One repair pass, not a loop
When the gate fails, exactly one repair run happens, briefed with the failed checks and the value each one measured. Then the gate runs again. If it still fails, the build is marked as needing another pass and stops there. A silent retry loop burns your model quota without telling you, and it hides the case where the brief itself was ambiguous.
Where the artifacts live
- Files are written into the workspace folder on the paired computer, under
~/.myrax/workspaces/<project-id>. - A checkpoint is a git commit taken before the first edit, so
rewindhas somewhere to go. - The zip is built from the workspace when all checks pass, excluding
.env, keys,node_modulesand.git, and its sha256 is recorded. - A snapshot can be frozen with Shield, so a build that passed can be restored later without rebuilding it.
What you see while it runs
Every seat writes to the same log: lead, builder, qa, repair, reviewer and system. The dashboard streams those lines into the build view as they happen, which is why a long build is legible rather than a spinner. Model usage per seat is recorded separately and shown per run.

