←News detail

Larsen CundricUpdated Nov 4 04:20

Multi-agent collaboration ultimately can't avoid ticket tracking

AI summary

The author believes that every multi-agent setup will eventually reinvent a ticket-tracking system; his own approach is to put the tracking table directly into Notion. The quoted post further explains: he uses Notion as a ledger for cloud agents, with one row per PR, recording the responsible agent, CI status, and next steps; agents check the table before starting work, thereby preventing two agents from fixing the same bug.

Quoted post

Larsen Cundric

@larsencc

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 ✌️

View original

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 ✌️

View original post

Body

Every multi-agent setup ends up reinventing a ticket tracker.

Mine just went straight to Notion.

Source

Larsen Cundric