All ideas

Detect and pause duplicate in-flight agent work

1 person asked for this · Orchestration

Detect and pause duplicate in-flight agent work Harness-driven collision detection should protect usage before agents duplicate active, planned, or shipped work. Runnable reproduction / implementation sketch onAgentProgress(snapshot) -> findSimilarWork(active agents + planned/in development/shipped tickets) -> confidence >= 0.90: checkpoint + soft pause + notify -> confidence >= 0.70: inject related-work context Steps Track each agent objective, scope, files, and progress. Compare against agents and backlog lifecycle states. Inject related context without an MCP call. Checkpoint and soft-pause only high-confidence duplicates. Let users stand down, redirect, merge, or resume. Safety Product proposal. Similarity alone must never hard-kill an agent. Observed Agents explicitly told to inspect the backlog still filed differently worded duplicates. Sanity review repeatedly consolidated overlapping roots. Expected / proposed Prevent duplicate work while preserving user control and avoiding destructive cancellation. Why it matters Reduces wasted tokens, overlapping implementations, duplicate tickets, and concurrent work obscuring features.

This gathers what several people told us separately. Their original messages stay private: only this rewording is public, and nobody sees who wrote what.

Discussion1

  • The team6 days ago

    Thanks for taking the time to send this. We're cleaning up older requests, and this one isn't on our roadmap for now, so we're closing it. If it still matters to you, please submit a new request describing how you'd use it today: fresh requests with current use cases are the ones we look at first.

You will be told by email and in the app on every reply. Every message carries a link to stop them.