Tickets in,
Product out.
Autobuild runs coding agents through a fixed pipeline that plans, implements, reviews, and verifies every ticket before it merges.
Every ticket runs the pipeline
Each ticket moves through deterministic phases inside its own build-runner. Every phase is a fresh agent session, with artifacts knitting them together.
back to implement
A dispatcher spawns builds
The dispatcher claims ready tickets and starts a build-runner for each. Runners are isolated, all state is logged.
events
artifacts
streams
events · artifacts · streams
Break it down. Merge it whole.
Split a big feature into as many tickets as it needs. Each build merges on the feature’s own branch, siblings stay in sync automatically, and main sees the whole thing once, verified, when you say so.
$ bun ab ticket tree main AUT-837 [node] Website for 1.0 AUT-838 [work] (Done) Verify animated figures and docs pages on the website AUT-839 [work] (Done) Animate the pipeline figure on the website AUT-840 [work] (Done) Animate the dispatcher and intake figures on the website AUT-841 [work] (Done) Show the integration tree on the landing page AUT-842 [work] (Done) Add a documentation section to the website AUT-843 [work] (Done) Document builds, dispatch, integration and tickets on the website AUT-844 [work] (Done) Document operating, seams and configuration on the website AUT-863 [work] (Done) Keep the website capture unit test within its timeout AUT-874 [work] (Done) Give the website one shared header across the landing page and docs AUT-875 [work] (Done) Lay out the docs pages like a standard documentation site AUT-876 [work] (Done) Add Copy as Markdown to every docs page 11 tickets merged on ab-node/website-integration · main receives one pull request
All local, all remote, or anywhere between
Every seam is an adapter you can customize for your project. The build pipeline stays the same.
where work comes from
what starts builds
where a build runs
who does the thinking
where code merges
where state lives
how you watch
Built for throughput, not latency
One build may take longer than a chat with an agent. The trade is far more changes merging every day, and with much greater reliability.
Nothing in the pipeline waits on you. You don't approve tool calls, paste errors back, or watch a terminal.
Builds run side by side, each in its own workspace, up to the limit you set. Your attention stops being the ceiling.
Let the queue fill itself
Once tickets are the interface, anything that can write a ticket can put work in front of you.
persistent memory
any agent harness
dispatcher
persistent memory
any agent harness
dispatcher
product calls
answered by
the agent