Install
Dashboard

Needs you

Needs you is the list of things only a person can unblock: an agent at a permission prompt, an agent waiting for your next prompt, a message nobody has read, a run that finished, a repo waiting to be connected. Coordigent builds it on your machine, so it works with no account.

What goes on the list

An item is one of these, in this order:

  1. An agent that is Blocked. It stopped at a permission prompt. Answer it in the agent's terminal.
  2. An agent that is Waiting on you. It finished its turn and needs your next prompt.
  3. An Idle agent with an unread message that has waited more than 10 minutes. A working agent with unread messages is not listed, because it reads them at its next tool call.
  4. A finished headless run you have not opened, whether it is done, failed, timed out or lost. coord runs show <id> marks it seen. See Runs.
  5. A repo waiting to be connected. An agent is working in a repo this machine has not connected to your project. Answer Set up in VS Code, or run coord connect in the repo. See Connect a repo.

Within each kind, the item that has waited longest comes first. An item leaves the list as soon as its cause is gone: you answer the prompt, the agent reads the message, you open the run, you connect the repo or decline it.

Where it shows

  • CLI. A ⚑ NEEDS YOU block at the top of coord status and coord sessions (example below).
  • Live view. In the machine pane (L in coord), agents that need you are listed first.
  • Statusline. Claude Code's statusline adds ⚑ 1 needs you (or ⚑ 3 need you).
  • VS Code. The Needs you view has one row per item, and the Coordigent icon carries the count. Clicking an agent focuses its terminal. When an agent in your window first needs you, one notice says so.
  • Website. A "Needs you" card lists your own agents that are Blocked or Waiting on you. Unread messages, runs and repo questions stay on your machine.
  • Desktop notifications. When an agent becomes Blocked, your machine shows a notification, at most one per agent every 5 minutes. Waiting on you and messages never notify. A finished headless run notifies once.
⚑ NEEDS YOU · 1 aaaa blocked 0s permission prompt open — answer it in its terminal

Turning notifications off

Desktop notifications are on by default. To turn them off, add this to ~/.tower/preferences.json:

{ "desktopNotifications": false }

The list itself keeps working; only the notifications stop.

Next