←Story detail

Trending story

Larsen Cundric shares using a Notion table to manage cloud Agent PRs

2 reports2 story updatesUpdated Nov 4 03:49

Understand this story

AI overview

Larsen Cundric shared his approach of using a Notion table as a cloud Agent task ledger: one row per PR, with a row created as soon as work begins, recording the responsible Agent, CI status, and next steps; Agents check the table before starting, reconcile it daily against the real PRs, and completed rows are hidden but not deleted. He says that this way, when multiple Agents work in parallel, they won't fix the same bug repeatedly, and the status of any PR can be looked up at any time. He also said that so far he has only lost 11 PRs, and those PRs never had rows created for them.

AI-generated from public reports

Latest development · Report

Multi-agent collaboration ultimately can't avoid ticket tracking

Developments

1 confirmed developments

  1. Larsen Cundric shares his approach to managing cloud Agent PRs with a Notion table

    Source:Larsen Cundric

Reports and discussion timeline

Browse reports and discussion by time. Their evidence levels remain distinct.

Nov 4

  1. Larsen Cundric

    Multi-agent collaboration ultimately can't avoid ticket tracking

    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.

  2. Larsen Cundric

    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.

Related stories

  1. Related storiesThe DeepSeek Harness team shares its Super-agent design exploration
  2. Related storiesDeepSeek releases DeepSeek-V4.1-Flash-1017
  3. Related storiesEnglish translation is being prepared.
  4. Related storiesAdo introduces the Claude Code mods mechanism