Summary
Priority: P0 | Category: Attention Routing
Aggregate all pending human-input requests across all sessions into a single, actionable queue — visible from the menu bar without opening any terminal.
Problem
When agents need human approval (tool use permissions, file writes, destructive actions), the request lives inside the individual terminal/session. If you're not looking at that terminal, you don't know it's waiting. The agent sits idle. You find out minutes or hours later when you happen to check.
With multiple agents, this becomes a constant tax. You poll terminals. You context-switch to check "is anything waiting?" You miss approvals. Agents stall.
Proposed Solution
A unified approval queue sorted by priority. Each item shows:
- Which session is asking
- What it's asking for (tool approval, decision, file write, etc.)
- How long it's been waiting
- A one-line summary of what the agent is trying to do
- Quick-action buttons: Approve / Deny / Open Session
For simple approvals (tool permissions the user has approved before), consider an "auto-approve similar" option to reduce future friction (related: #15 — settings.json permission suggestions).
Acceptance Criteria
Open Questions
Summary
Priority: P0 | Category: Attention Routing
Aggregate all pending human-input requests across all sessions into a single, actionable queue — visible from the menu bar without opening any terminal.
Problem
When agents need human approval (tool use permissions, file writes, destructive actions), the request lives inside the individual terminal/session. If you're not looking at that terminal, you don't know it's waiting. The agent sits idle. You find out minutes or hours later when you happen to check.
With multiple agents, this becomes a constant tax. You poll terminals. You context-switch to check "is anything waiting?" You miss approvals. Agents stall.
Proposed Solution
A unified approval queue sorted by priority. Each item shows:
For simple approvals (tool permissions the user has approved before), consider an "auto-approve similar" option to reduce future friction (related: #15 — settings.json permission suggestions).
Acceptance Criteria
Open Questions