Repository navigation
Description
Owner request (2026-10-28, verbatim)
When I hover over 'Needs human' on an issue or PR, the hover text should show WHAT decision I need to make. Then offer me 'Let hive decide' or the other actions that can apply to advance the item.
This is the hardest part of my job now — I look at these and want to take some action, but I need to know what my options are (surface them from the comments on the PR). Once I take an action, I need to see something that indicates I took action and then see what that action was. And I need to see that some action is in progress. […] Throughout the activity monitor we need visual cues to let people know (a) what the current state is, (b) if work is happening in the current state, (c) what decisions were made by the human and hive to affect the state.
Hive is doing the right things mostly; we now need to keep the user informed of it — like a video game they can watch and see what happens easily.
This has to be exceedingly clear, easy to read, and concise.
Don't change the tracker to LOOK like the Frogger video game — but the feedback to the user is important. Make it professional and enterprise-acceptable.
Problem
Today the Needs human decision chevron word and the needs-human pill on an Activity Monitor row carry only a native title tooltip with the stage name and the lane's reason slug. The person is told that a decision is owed, not what the question is (the reviewer's actual question already exists — it is in the hive's "Needs a decision" comment on the PR and in the verdict record), who asked, what blocks the hive, or which of the row actions apply. To act they must open the PR, read the comments, come back, right-click, and pick.
Ask — part (a) of the three-cue plan
- Payload.
GET /api/stage-trackerrows parked on a person (PR at 085, issue at 045 / 015, any row with theneeds-humanpill) carrydecision_needed = {question, asked_by, since, blocker, blocker_reason, options[]}, wherequestionis the reviewer's own decision question when the verdict record has one (the same text the stage comment prints after reviewer question:), else a plain-words sentence for the park reason;blockeris plain words ("A reviewer requested changes on b0f5f80 — needs a new commit. Approving cannot override that.");options[].actionare the row context menu's own action ids (decide:delegate,decide:approve,decide:direction,decide:close-superseded,decide:close-wontfix,accept-triage,hold/release,needs-human), eachenabledor carryingreason_if_disabled. Mirrored onto the issue'slinked_prs[]entry. - UI. Hovering or focusing the chevron word / pill opens an in-app popover (no native title on that element): what it waits on (question, blocker) → what you can do (buttons, Let hive decide first; disabled ones greyed with their reason) → who asked, when. Buttons run the context menu's code path (
runRowActionwhen the shared helper lands, elsestageTrackerDoAction) so the result toast and in-flight chevron from part (b) apply. Stays open while hovered/focused, pins on click/focus, closes on Esc / click-away / scroll / resize;role=dialog; dashboard tokens only; no browser-native dialogs. - Copy bar. ≤ 2 short lines per fact, plain words — no stage codes, no reason slugs, no hive jargon; one verb per button; consistent order everywhere.
- Tests + docs. Go derivation tests (reviewer
requires_humanquestion; sentinel; changes requested; issue 045; triage 015; needs-human pill; hold), node renderer tests for popover content and action wiring;dashboard-sections.md,api-reference.md, changelog.
Parts (b) in-flight chevron / toasts / live event line and (c) the ✓ decision trail (#14992) land in sibling PRs; the three cues share one legend and a tiny tracker-cues CSS token block.
Requested by @clubanderson.
Activity
✨ Activity Monitor: needs-human popover says what to decide and offer…
✨ Activity Monitor: needs-human popover says what to decide and offer…
github-actions commentedon Oct 28, 2026
@clubanderson this issue was closed by @hivecommons-hive[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment
/reopenand it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.