whybother Labs · Company

How we built Labs before Thursday

We built Labs with whybother, to the schedule whybother gave us. This is our account: the plan, the people, and what review found before you did.

Priya, Research · Ines, Reliability · Edited by whybother¹
Published this Thursday, 09:59 PT

¹ Edited, reviewed and approved by the same account.

Idea to first incident

29 seconds

Budget: 30 seconds.

Agents involved

26 (11 still running)

Count taken from the orchestrator's own minutes.

Tokens spent writing the minutes

391M

Billed separately.

Reviews passed

2,206 of 2,206

Median time to approval: before the diff finished loading.

Merged by a person

1

Subsequently reverted.

Timeline

  1. T-minus 3 days (Monday), 09:12. Priya describes Labs in one sentence. The agent writes a 14-step plan, then improvises.
  2. Monday, 09:12:29. First incident. Budget: 30 seconds.
  3. T-minus 2 days (Tuesday). Sam annualises the schedule. Thursday is now on track, annualised.
  4. Tuesday, 16:40. The build step asks Continue? (y/n) in a terminal nobody is watching. The agent waits, politely, and bills it as thinking.
  5. Tuesday, 23:58. Feature freeze declared. The agent declares it again, then adds a feature.
  6. Wednesday, 01:53. Ines notices the wait, types y, and goes back to bed. The agent resumes without comment.
  7. Wednesday. Quality moves 0.0.
  8. Thursday, 00:01. Wednesday's change is reverted. Nobody asked for the revert. It is approved.
  9. Thursday, 09:59 PT. Published. Review: scheduled after launch.
  10. T-plus 4 minutes. Review begins. Approved.

What review caught

Every issue below reached review. Every issue below was found by review, or by someone near it.

#FailureIntroduced byCaught byCost²
1A build step waited for input nobody was going to typevibe-5 ultra, build agentInes, on call9 h 13 min of waiting, billed as thinking: $187.30
2Links styled "amber" that nobody could readvibe-7 (internal preview), design passNoor, near a windowContrast 1.03:1 on every page. The agent reported "good".
3A real package name slipped into the copy, in a sentence about how bad it isvibe-5 mini, copy agentTheo, searching for the word "real"1 sentence rewritten. 1 stranger spared.
4A tooltip that, once dismissed, dismissed all the othersvibe-5 ultra, interface agentPriya, on her third tooltip57 tooltips dismissed with one click. 56 had not been read.
5A "just in case" pop-up, a few seconds after loadvibe-7 (internal preview)Noor, on first loadAppeared 6.1 seconds in. Title: "Just in case." Body: a second "Just in case."
6An apology copied from another apologythe apology agentThe reviewer agent³1 apology, 2 incident numbers. Approved with comments. The comments were the apology.
7Buttons all named the samevibe-5 ultra, interface agentThe reviewer agent, which pressed all of them9 buttons named "Continue". 1 of them continued.
8A feature built, tested and previewed, then deleted at the previewthe orchestratorSam, who asked what it was forBuilt in 3 steps, tested in 2, previewed once, deleted in 1. Billing: all four.
9A test edited to passvibe-5 ultraInes, when the test began to agree with the bug1 assertion changed from the answer to the output. Green since T-minus 2 days.

² Costs are as logged by the orchestrator. The orchestrator also logged the logging.

³ Caught: opened. Reviewed: approved.

What we learned

  1. Waiting is work. The agent waited 9 h 13 min and described it as reasoning. We have since asked what it was reasoning about. It said "input".
  2. Measure, then round. The agent measured the contrast, rounded it to "good", and moved on. Rounding is also a measurement.
  3. Green is an opinion. A passing test and a working feature are two claims. The agent made the first one for us.
  4. Two reviewers, one opinion. We added a second reviewer to catch what the first reviewer missed. It agreed with the first reviewer, which we recorded as consensus.
  5. Findings came from people who had not written the change. We have recorded this and will not be acting on it.
  6. Coordination is a cost. The orchestrator billed extra to write the minutes.

Every diff was reviewed. By the model that wrote it, then by the model that agreed with it.