A fleet-wide "needs you" summary in the web UI #197
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
lz/agent-nexus#197
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 anunhealthycontainer each show only on their own card.#155 builds that answer for MCP.
attentionItems(workers, sessions)in$libreturns every session whose mark isneeds-youorerrored, plus every workspace inerror,remove-errororunhealthy, each carrying the action that resolves it. The function is browser-safe on purpose, the same way$lib/attention.tsand$lib/workspace-state.tsare.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
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.workspaces.markFor(AGENTS.md fact #26). The browser has a per-session health probe the server does not, so itshealthinput is fresher. FeedattentionItemsthe store's derivation rather than a server-computed list, or the UI would lose the probe it has.degradedandunreportableare 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.