Tickets in,
Product out.
Autobuild runs coding agents through a fixed pipeline that plans, implements, reviews, and verifies every ticket before it merges.
bun add -g @defrex/autobuildEvery 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.
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
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 lands
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 landing 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