Say you have three agents running at the same time: coding agents, or any other kind of AI agent working in the background.
How do you know which one is waiting for you, which one is finished and which one is stuck? Do you flip between tabs, rely on notifications, watch a dashboard, or have you built something of your own?
When was the last time an agent sat idle because you missed the moment it needed you? And what did you change afterwards?
We're collecting real setups and real workarounds, and we'll read every reply.
Drafted with AI assistance.
Top comments (2)
We hit a related case today with a webcomic publishing worker: it posted a comment, then stopped before recording the result. The task still said RUNNING, but that couldn't tell us whether the post existed. Heartbeats and lease expiry identify a stale worker; a fresh permalink readback verifies the actual post. 'Outcome unknown; don't retry' is a useful status between done and failed.
Well I have a few methods. So a bit of background, I run around 12-16 projects at a time, across 4 separate systems. I built my own IDE and added multi-system support, specifically so I can unify my work across them, including a live VC system so they dont step on eachother's toes. For continuation, I ended up building a teams studio, specifically so I can build a chain of command, so I give 1 task and it routes to the appropriate agents, so work is done in parallel and when anyone has a question, there's a 'supervisor' to answer them. Most of the time an agent asks for input, it's not actually necessary, a strict usability:security:durability:performance rubric ends up answering pretty much all the questions.