Repository navigation
Description
Problem
On a paused agent, the dashboard can show no way to resume it, and owner-only controls vanish with no explanation. Seen 2026-11-17 on a customer's standalone hive (direct route, GitHub device-flow login, hive on hive:candidate rev c7aea838c):
- The
revieweragent was paused (paused: true,pause_owner: operator, restored on boot, badge "paused · state-restore") with a ready sandbox. Its detail card showed the action row[0/1 power switch] terminal, full log, log text, past kicks, restart, gear, kick, litellm, modelwith no▶ resumebutton, in two different people's browsers: the customer's admin (joerunde:owner) at 13:50 ET, and the operator (clubanderson:owner; the hive log lineGitHub user authenticated via device flow ... role owneris at 13:58:02) at 13:58. - About two minutes later the same operator's page showed the running
depscard with its⏸ pausebutton at the start of the row, so owner controls render for a running agent once the role is known. - The collapsed Agents row for the paused reviewer repeats the chip
paused · state-restorein five different columns (state, interval, last kick, next kick, ...), which reads as a render glitch.
Code (checked on v5.293.0, same shape at the running revision): in agent-detail.js (oc-detail-actions) and agent-cards.js (canPauseToggle), the pause/resume control only renders when dashboardRoleAtLeast(window._hiveRole || 'read', 'owner'); otherwise the slot is silently empty (''). window._hiveRole is set asynchronously (gh-auth.js showGHAuthState / /api/role, with retries); only some sections (Inbox) subscribe to _hiveRoleListeners and repaint when the role settles. So a card rendered before the role arrives can stay without its toggle. I have NOT reproduced it, and I do not know yet why a paused sandboxed agent would still lack the button after the role is known: reproduce first.
Expected
- Resume is always reachable on a paused agent. Reproduce why the reviewer card showed no
▶ resume/▶ start & resume(candidates: render before the role settled with no repaint;agentIsDisabled; thestate-restorepause path; sandbox agents with no tmux session) and fix the cause. - Role-gated agent controls repaint when the role settles (agent cards, detail view, collapsed rows): subscribe to the existing role-settled listeners and re-render, instead of leaving a stale card.
- Never hide silently. For a viewer below owner, or while the role is unknown, show the pause/resume control disabled with a tooltip ("Needs the owner role", or "Checking your access...") instead of an empty slot. Same for other owner-gated controls on the card if any.
- One clear paused chip. Show a single
pausedchip with its reason (for example "state-restore", with the explanation on hover) in the collapsed row, not the same chip repeated across columns.
Acceptance
- A test that renders a paused agent card (running and not running, sandboxed and not) before the role is known, then settles the role to
owner, and asserts the resume control appears without a manual reload; a test that roleread/read-writesees it disabled with the hint. - A test for the collapsed row: one paused chip.
- Dashboard tests for the new markup; changelog.d fragment;
src/docs/dashboard-sections.mdupdated if the card contract changes.
Related: #18797 / #18800 (agent Sandbox settings UI; different files), #18804.
Activity
clubanderson commentedon Nov 17, 2026
Claimed: an operator-dispatched agent is working on this now. Hive agents, please do not pick it up.
🐛 dashboard: update detail fingerprint pin for role gate (#18813)
🐛 Dashboard: paused agent always shows resume or why not, repaint on …