Signal & the attention queue

Signal is the app's home screen and its reason to exist: in one glance, is anything waiting on me?

The map

The top of the screen plots every enrolled host and its connection state — which machines are online, how many agents each is running. It's the fastest way to confirm "the Pi is up, the workstation is up, six agents running" from anywhere.

The attention queue

The centerpiece. Any agent that has blocked on a decision — typically a permission prompt — surfaces here, across all hosts, newest first. Each card names the host and agent and jumps straight into that agent's session cockpit, where you can read the state and answer.

An empty attention queue is the goal state: everything is running, nothing needs you.

The active field

Below the queue, every agent across every host is listed with its current status — including the ones happily working. Use it to spot-check long runs without opening each session.

Workflow

The intended loop:

1. A notification tells you something needs attention.
2. Signal tells you what and where.
3. The cockpit lets you decide and continue.

TIP — > Nothing on this screen is a local guess — it's live state from your bridges. If a host is missing from the map, that's real signal too: check c3bridge service status on the machine, or see troubleshooting.