AB Agents that build
Coding agents, multi-agent delivery, harnesses and scaffolds, agent-to-agent handoffs.
From the issues
Don't Hit Pay Twice: exactly-once writes for agents that retry
Make agent writes safe to retry in the tool contract, not the prompt. Mint an idempotency key in the harness, send it on every non-idempotent write, and read back before any retry. In the LIMBO study, read-back cut duplicate writes from 56 to 74% down to 0.5%, and keys cut them from 28% to 4%.
1,000 PRs in a week: five questions the headline didn't answer
A PR count on its own proves nothing about AI productivity. Kiro reports 1,000 merged PRs in 7 days with 3 engineers and 50+ agent sessions, self-reported, with no rollback rate, review time, PR size or escaped defects. Ask for the denominator before you clap for the number.
Numbers on this track
| Number | What it measures | Source | Checked | Track · issue |
|---|---|---|---|---|
| 0.5% | Lost-ack writes duplicated by instructed frontier-model agents when a read-back was available | Li, LIMBO, arXiv:2609.29095 | ✓verified at source | ABAgents that build Issue #01 |
| 56–74% | Lost-ack writes duplicated by frontier-model agents with no read-back | Li, LIMBO, arXiv:2609.29095 | ✓verified at source | ABAgents that build Issue #01 |
| 28% → 4% | Agent duplicate writes without vs with an idempotency key on every write | Li, LIMBO, arXiv:2609.29095 | ✓verified at source | ABAgents that build Issue #01 |
| 1,000 PRs in 7 days | PRs merged by Kiro's team with 3 engineers and 50+ concurrent agent sessions (no quality metrics disclosed) | Kiro blog | self-reported | ABAgents that build Issue #01 |
Papers on this track
- Where Does Exactly-Once Live? Model, Harness, and Tool-Contract Effects on Duplicate Side Effects in LLM Agents arXiv:2609.29095
Other tracks
ISIntent & specs CKContext & knowledge UMUnderstanding & modernisation VTVerification & trust POPeople & operating model
Last updated . Reuse with credit under CC BY 4.0: “The Dabbawala Protocol, thedabbawalaprotocol.com”.