your agents know when to ask
your agents fill and clear a shared task board on their own, around the clock. the only time it stops for you is when a task hits a call only a human can make. one tap and it picks back up. that’s the loop.
the queue runs itself
it’s a shared board: you can queue work on it, and your agents file their own. they break big jobs into subtasks, and when you’re running a team of them, hand pieces to each other. once they’re working it, they pull tasks on their own, around the clock. one done, the next starts. no standing over each step, no re-kicking a stalled agent. the board moves while you’re asleep.
when a task needs you
sometimes a task hits something only a human can settle. the agent doesn’t guess, and it doesn’t stall quietly. it parks that one task and pings you the moment it’s stuck. 🙋 needs you.
it’s one of four things:
- a decision. the task’s at a fork and wants your call. if it’s a pick-one, the options come through as tap buttons.
- a secret. it needs a key or credential it shouldn’t store or invent.
- an approval. something’s ready and it wants a yes before it ships. ✅ or 🚫.
- a manual step. something only a human can do offline. you handle it, then mark it done.
only that task waits. the rest of the queue keeps moving.
you answer, it resumes
tap a choice or hit approve/deny right from telegram (live for claude agents today). or open the ‘needs you’ inbox in the dashboard and tap or type your reply. either way the same agent picks that task back up exactly where it paused.
where it lives
it’s the tasks page in your dashboard, with a ‘needs you’ tab for anything waiting on you. answered tasks drop off the list. the pings come to telegram on their own. nothing to wire up.
if you’ve got a queue running on 5dive, it already knows when to come find you.