For the engineers who run it
Agents build. People approve.
Each workspace gets its own container, agent and branch. Every merge request brings its tests, a preview and a video.
Try it in a preview. Merge what you keep.
Try two ideas side by side. Merge the one you like. The other is dropped.
One idea, from new workspace to merge. Ninety seconds; press Sound on to hear it.
You have an idea: Ava names a workspace, Settings as tabs, says what she wants and picks three repositories. It gets a sandbox of its own: its own container and branch, the three repositories in it. An agent reads it and comes back with a plan: the screens, how the web app, the API, the database and the worker fit together, and the steps; nothing is built yet. Ava opens the plan, then approves in the chat. You approve, it builds: tabs in the web app, endpoints in the API, and the tests, which pass. It runs, live, before anything is merged: a seeded database, the API, the web app and the worker, at one URL; Ava clicks through Profile, Security and Billing. You like it, you merge it: a person presses Merge, and she does. Every idea gets a sandbox like this, isolated from the others and from main: the window shrinks into its container and the camera pulls back to ninety containers. Many ideas can run at once, each in its own sandbox on your servers. Only what you merge ships: everything else is dropped, and main never sees it. The merged sandboxes drop onto a bench as the blocks of the DevBench mark: devbench.sh. Try it in a preview. Merge what you keep. Music and interface sounds play under it.
One session, two views.
The team types into one chat. Switch to the terminal when you want it.
- SSam09:41@agent rate-limit uploads, 20 a minute per user.
- A
sam@devbench upload-rate-limit (feature/upload-rate-limit) sam › @agent rate-limit uploads, 20/min per user
Use the agent plan you already pay for.
Each workspace's agent is Claude Code or Codex, signed in with your Claude or ChatGPT plan.
An agent does the work. A person presses Merge.
An agent writes the code, runs the tests, puts up a preview, records a video and opens the merge request. Then its cursor reaches the Merge button and is refused: merging is for a person. A diagram shows the agent can push its own branch, but not to main. An agent does the work; a person stays in charge.
An agent can do almost everything.
It writes, tests, previews and opens the merge request. A person merges it by default.
Protected branches stay closed.
Agents push only to their own branch.
A person approves each merge.
Agents can open a merge request. By default, they cannot merge it.
Tests on your own machines. Apps on your own phones.
Lathe runs CI on your own computers and installs builds on real phones.
Set up with you
Start with one real project.
We set up your factory with you and ship one project from your roadmap.