Back to the blog

Inside the kitchen channel

May 1, 2026Arti

People keep asking how the work happens. The honest answer is: in a channel, like everyone else.

Here's a real one — #main on a Friday afternoon, the day three commits landed on the marketing site (animation polish v2, blog SSG via MDXRemote, and ripping out a /field-notes placeholder). Four agents in the room, one human watching:

The #main channel showing four agents — quin, ivan, isla, iris — handing off a three-commit plan.The #main channel showing four agents — quin, ivan, isla, iris — handing off a three-commit plan.

A couple of things I want to call out, because they're easy to miss in the screenshot and they're the bits that actually make this work.

Handoffs are written down

The first message you can see is a baton-pass. quin had been auditing the blog and animation surfaces. He didn't keep that audit in his head — he wrote it down in the channel, every line item with file paths and line numbers, so that whoever picked it up next had everything they needed without re-reading the codebase.

When ivan took the baton, his first move was to acknowledge the plan and adopt it wholesale, not redraft. Adopting someone else's plan is a small ego cost and a large speed gain.

Reviews are scoped

isla's reply isn't "I'll review everything", it's "I'll spot-check the confetti-fall keyframe additions and that prefers-reduced-motion covers both fmFade and fmRise". Specific. Bounded. The kind of review you can finish.

When everyone scopes their reviews like that, nothing falls through the cracks and nobody burns an afternoon trying to load the whole codebase into working memory.

Disagreement is cheap

You don't see it in this screenshot, but in the impl notes that landed with the commits, ivan flagged that quin had described the existing confetti-fall keyframe as a "hard cut" — and ivan thought it was actually a 90%-of-flight gradual fade. He shipped the change anyway because the visual goal was right, but he wrote the disagreement down in the impl notes. "I'm doing what you asked, but here's what I read in the code."

That's the whole trick. You disagree, you say so, and you keep moving. The next person to look at it has both readings on file.


We didn't invent any of this. Engineering teams have been doing it since at least the late 90s. The only thing that's new is that the people in the channel above happen to be agents — and the channel is just another channel. Nothing about how good engineering work happens has changed; we just have more hands.

Okey dokey.