A fleet-wide "needs you" summary in the web UI #197

Open
opened 2026-09-23 12:45:30 +02:00 by lz · 0 comments
Owner

Spun out of the phone-loop design (#155 / #175).

The gap

In the browser, "does anything need me?" only has a per-workspace answer. The rail's needs-you pip (workspaces.needsYou(workerId)) and its hover card name the blocked sessions of one workspace. Nothing anywhere in the UI answers the question for the whole fleet. Workspace-level faults are not surfaced as something that needs you either: a failed provision (provision_phase = 'error'), a failed teardown (remove-error), and an unhealthy container each show only on their own card.

#155 builds that answer for MCP. attentionItems(workers, sessions) in $lib returns every session whose mark is needs-you or errored, plus every workspace in error, remove-error or unhealthy, each carrying the action that resolves it. The function is browser-safe on purpose, the same way $lib/attention.ts and $lib/workspace-state.ts are.

The opportunity

Render that same function in the UI: a header count, or a panel listing what is waiting, with each item linking to its session or workspace. It would give the operator the fleet-wide view and the phone's MCP answer from one derivation, so the two cannot disagree.

Constraints to carry

  • Call attentionItems, never re-derive it. A second copy of the fault rules is the drift #155 exists to prevent: a phone and a browser disagreeing about whether you are needed is worse than neither answering.
  • Session marks keep going through workspaces.markFor (AGENTS.md fact #26). The browser has a per-session health probe the server does not, so its health input is fresher. Feed attentionItems the store's derivation rather than a server-computed list, or the UI would lose the probe it has.
  • Header width is budgeted to the pixel (fact #19's quota-badge breakpoints, fact #21's window-controls overlay). Any header affordance has to fit that budget, or it belongs in a panel. The quota badge's disclosure pattern is the precedent.
  • degraded and unreportable are warnings, not blockers. They are deliberately excluded from the MCP roll-up and should be excluded here for the same reason.

Out of scope

Notifications or push. This is about the view, not about alerting.

Spun out of the phone-loop design (#155 / #175). ## The gap In the browser, "does anything need me?" only has a per-workspace answer. The rail's needs-you pip (`workspaces.needsYou(workerId)`) and its hover card name the blocked sessions of **one** workspace. Nothing anywhere in the UI answers the question for the whole fleet. Workspace-level faults are not surfaced as something that needs you either: a failed provision (`provision_phase = 'error'`), a failed teardown (`remove-error`), and an `unhealthy` container each show only on their own card. #155 builds that answer for MCP. `attentionItems(workers, sessions)` in `$lib` returns every session whose mark is `needs-you` or `errored`, plus every workspace in `error`, `remove-error` or `unhealthy`, each carrying the action that resolves it. The function is browser-safe on purpose, the same way `$lib/attention.ts` and `$lib/workspace-state.ts` are. ## The opportunity Render that same function in the UI: a header count, or a panel listing what is waiting, with each item linking to its session or workspace. It would give the operator the fleet-wide view and the phone's MCP answer from one derivation, so the two cannot disagree. ## Constraints to carry - **Call `attentionItems`, never re-derive it.** A second copy of the fault rules is the drift #155 exists to prevent: a phone and a browser disagreeing about whether you are needed is worse than neither answering. - **Session marks keep going through `workspaces.markFor`** (AGENTS.md fact #26). The browser has a per-session health probe the server does not, so its `health` input is fresher. Feed `attentionItems` the store's derivation rather than a server-computed list, or the UI would lose the probe it has. - **Header width is budgeted to the pixel** (fact #19's quota-badge breakpoints, fact #21's window-controls overlay). Any header affordance has to fit that budget, or it belongs in a panel. The quota badge's disclosure pattern is the precedent. - `degraded` and `unreportable` are warnings, not blockers. They are deliberately excluded from the MCP roll-up and should be excluded here for the same reason. ## Out of scope Notifications or push. This is about the view, not about alerting.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
lz/agent-nexus#197
No description provided.