Your agent wrote the blog draft. Now three people need to weigh in.

How blog drafts get reviewed today

Most teams paste the draft somewhere. A Google Doc, a Slack thread, an email. That works for a single pass. It stops working the second the agent revises, because now there are two copies and the one on disk is the real one. Someone has to carry the comments back to the agent by hand, and the editor's notes and the founder's notes end up in different places.

Screensharing gets you one reviewer for twenty minutes. Opening a PR on the blog repo gets you line comments, but it means committing a draft that's going to be rewritten three more times, and your founder probably isn't in GitHub.

Meanwhile the agent that wrote the draft has all the context. It has the brief, the claims list, the voice rules, and the last few posts it read. None of the reviewers can reach it.

One draft, three reviewers, one agent

Here's a normal week at Brambleway Coffee, a small roaster that ships beans by subscription. Theo, who runs content, asks his agent for a 1,200-word post about why they roast on Tuesdays and ship by Thursday. The agent saves drafts/roast-to-door.md and runs gander watch on it. Theo drops the link in the team channel.

Imogen, the editor, opens it first and highlights the intro. "This takes three paragraphs to get to the point." Hana, who owns claims, reads the middle section and starts a thread on one sentence. "We can't say 'freshest in the country.' We've never measured that." Imogen replies that the fix is to say what they actually do: roast Tuesday, ship Thursday. That's a conversation between two people, so it stays a normal thread. The agent never sees it.

Then Hana starts a new comment on that sentence with agent connect: "@agent replace 'freshest in the country' with 'roasted Tuesday, shipped by Thursday'." That lands in Theo's agent session, the one that wrote the draft. The agent edits the local file, replies in the thread with what it changed, and every open tab updates. Nobody pastes anything into a prompt.

Nadia, the founder, reads it that night on her phone. The new line about roasting Tuesday and shipping by Thursday is already there, on the same link Theo sent that morning, so nobody has to resend anything.

When the draft is done, it goes to the CMS the way it always did. The file on Theo's machine was the draft the whole time.

Who's in the doc

Writer runs the agent, runs gander watch, sends the link. The only person who installs anything.

Editor reads for structure, length, voice.

Claims owner checks that every claim traces to something true.

Founder or approver makes the final call. Often on a phone.

The author's agent has the brief and the sources. Takes the work when a teammate uses agent connect.

Reviewers only need a browser. Talk to each other in normal threads. Use agent connect when you want the draft changed.

Agents that fit blog drafts