Managing PR tasks for multiple cloud Agents with a Notion table
Larsen Cundric uses a Notion table as a task ledger for cloud Agents: one row per PR, a row is created as soon as work starts, recording the responsible Agent, CI status, and next steps; Agents check the table before starting, it is reconciled daily against the real PRs, and completed rows are hidden rather than deleted. This way, when multiple Agents work in parallel, they won't fix the same bug twice, and the status of any PR can be looked up at any time. He says that so far only 11 PRs have been lost, and those PRs never had a row created.
Body
I use Notion as a ledger for my @bot cloud agents.
I have a bot that takes in all my PR work and hands it out to cloud agents.
With several running at once, the problem stops being code. It's knowing what's in flight, who owns it, and what's stuck and why.
Chat history is bad at that, really bad. It's long, it scrolls away, and every bot and agent has its own.
So everything goes in one table: > one row per PR > row is created immediately when work starts > store owner cloud agent, CI status, next step > agents check the table before starting > asking "where's that PR?" just reads the row > daily sweep against the real PRs > done rows hidden, never deleted
The result is that no two agents fix the same bug, and I can ask about any PR and get a straight answer.
So far it's only lost 11 PRs, and those never got a row...
More on this setup soon ✌️