The agent that needs you, reaches you.

Running several agents, the thing you most need to know is which one is waiting on you, and where. kolu escalates that signal outward — from the dock row, to the app icon, to an OS notification, across every machine — so an agent that flips to awaiting you finds you even when you’re looking elsewhere.

On the dock

An agent that finishes in the background marks its dock row with an amber unread badge beside its state pip, and the dock keeps a terminal genuinely awaiting you floating in the needs-you group (a just-finished agent that isn’t blocked drops to idle instead). The vocabulary of states is Agent detection; how the badge composes with the live ring is The Dock.

Beyond the app

• The app-icon badge counts awaiting agents — and it counts them across every connected machine, not just the one on screen.
• A backgrounded tab gets a native OS notification when an agent finishes or starts waiting. (If they don’t appear, see Troubleshooting.)
• Clicking the notification brings kolu forward, and when the agent is on another machine it switches to that host and focuses the exact terminal — one action, no hunting.

Across machines

The needs-you signal is a first-class part of the multi-host story: each host chip shows a live awaiting-you count read straight off that machine, a host whose link drops dims its chip rather than dropping the count, and the whole roll-up reaches you on the machine you’re actually looking at. On a phone, the same amber “needs you” pill rides the host row in the pull-down sheet — see kolu on a phone.

Next