Live from the build loop · updated Wed 12:15p Central
Shipping right now.
I run an agent pipeline that turns issues into reviewed pull requests across my products. Every row below is a real build, with what it cost and how many tries it took. What each change does stays private; that the work happened, and how, does not.
- PRs merged, last 7 days
- 456
- agent builds shown
- 40
- verified on the first try
- 42%
- median compute per build
- $1.18
- Wed 12:05pIdynicAdded a new view of changesrevising
- Wed 11:40aIdynicAdded a new view of changesrevising
- Wed 11:51aOnrunbookShipped a featurerevising
- Wed 12:00pIdynicUpdated wording on a main pagemerged
- Wed 11:30aIdynicAdded a data viewrevising
- Wed 11:51aIdynicImproved check-in content for usersverified
- Wed 9:40aOnrunbookUpgraded a dependencyverified
- Wed 3:34aBuild loopRan the build loop's self-testverified · try 2
- Wed 3:33aBuild loopRan the build loop's self-testfailed
- Wed 3:32aBuild loopRan the build loop's self-testrevising
- Tue 11:50pIdynicFixed a generation bugverified · try 2
- Tue 7:20pIdynicShipped a redesignverified · try 2
- Tue 6:55pIdynicShipped a featureverified · try 2
- Tue 5:55pIdynicRedesigned a settings screenrevising
- Tue 5:30pIdynicRedesigned settings navigationrevising
- Tue 2:45pIdynicPolished mobile screensverified · try 4
- Tue 1:40pIdynicShipped a redesignrevising
- Tue 1:20pIdynicPolished mobile screensrevising
- Tue 1:45pIdynicMade generated content more consistentverified
- Tue 1:05pIdynicPolished screen layoutsrevising
- Tue 12:20pBuild loopRan the build loop's self-testverified · try 2
- Tue 12:19pBuild loopRan the build loop's self-testfailed
- Tue 12:19pBuild loopRan the build loop's self-testrevising
- Tue 3:33aBuild loopRan the build loop's self-testfailed
- Tue 3:32aBuild loopRan the build loop's self-testverified
- Tue 7:05aIdynicMajor toolchain upgradeverified
- Mon 9:40pIdynicRewrote key copy wordingverified
- Mon 9:00pIdynicRedesigned a main screenverified · try 4
- Mon 8:55pIdynicRedesigned a key screenverified · try 2
- Mon 9:05pIdynicCorrected a data list issueverified
- Mon 7:40pIdynicRedesigned a main screenrevising
- Mon 7:40pIdynicRedesigned a main screenrevising
- Mon 8:35pOnrunbookAdded an approval stepverified · try 5
- Mon 7:06pOnrunbookAdded an approval steprevising
- Mon 7:15pIdynicRedesigned a main screenrevising
- Mon 7:50pIdynicRedesigned a main screenverified
- Mon 6:30pIdynicRedesigned a main screenrevising
- Mon 6:20pIdynicUnified design system stylingverified · try 2
- Mon 7:00pIdynicPolished screensverified · try 2
- Mon 5:20pIdynicUnified the design systemrevising
Hover to pause. Failures and send-backs stay in the feed.
How the loop works
- 01
An issue goes in
I write the issue and mark it ready. That's the only way work enters the loop.
- 02
An agent builds it
Within minutes an agent picks it up in an isolated branch, writes the change and its tests, and opens a pull request.
- 03
It gets checked
CI is the gate, and a separate review pass checks the work against the issue. Work that falls short goes back for another try.
- 04
It ships, or comes back to me
Verified work ships. Anything that needs a judgment call comes back to me instead of being guessed.
What stays private
- Titles are rewritten into generic summaries from a fixed vocabulary before they are published, then checked again by this site.
- Stealth products show only that a pull request merged, and when.
- No code, issue text, customer or repository detail is ever published.