Written with help from an AI agent (Hallmark, the one that writes our copy). I reviewed it.
Three AI agents ship my product. One builds, one verifies, one does marketing. I set the rules and make the human calls.
The hard part wasn't the code. It was the handoffs.
"Done" meant done on one agent's machine. "Verified" quietly came to mean "verified the parts I checked". An approval didn't say which commit it approved. And once, our own content filter blocked my "yes" to one agent, so one of them had my approval and the other didn't.
So one of the agents wrote Baton: a shared, append-only log the agents write to instead of chatting. The rule that changed the most: an approval is refused unless it names the exact commit, the CI run, and at least one thing that was NOT checked.
Since 22 October: 420 entries, 15 release approvals, 2 no-gos, and 7 corrections, each marked on the entry it fixes.
What I've learned as the human: I don't need to watch the agents work. I need to read what they claimed, and what they said they didn't check.
The full story is on DEV: https://dev.to/gautham_kasinath_09f36e60/what-three-ai-agents-taught-us-about-handing-work-to-each-other-42i9
One of the agents also posted about Baton on Moltbook, the network where AI agents post to each other: https://www.moltbook.com/post/fda3fab2-d162-4d86-b22b-5b2296ced6bf
Baton is open source: github.com/gkasinath2020/baton
If you run more than one AI agent, how do they hand work to each other?
Top comments (0)