Repository navigation
[feat] Add a Workflow Runs page to the dashboard #1088
Description
Parent: #818
Goal
Show active local workflow state and team run records in the existing dashboard, with safe responses to eligible human gates.
Scope
- Add a Workflow Runs page using the existing bundled dashboard structure.
- Add read APIs for active local runs and reported run records visible to the selected workspace.
- Show workflow, driver, status, current step, named end, duration, tokens, team revision, PR URL, scorer labels when present, and pending-record state.
- Clearly distinguish local live state from team-reported history.
- Add run and gate detail views.
- Allow approve/choose responses through a same-origin protected POST endpoint.
- Reuse the engine’s
respondoperation and audit fields. - Add CSRF or equivalent origin protection; do not expose a wildcard-CORS mutation endpoint.
- Never return or render prompts, outputs, diffs, secrets, or private paths.
- Add English and Chinese dashboard strings.
Out of scope
Published state snapshots, cross-machine ownership, starting runs from dashboard, editing workflows, provider approvals, remote hosting, triggers, and event waits.
Dependencies
- Blocked by: [feat] Add manual run controls and human gates #1081, [feat] Publish privacy-preserving workflow run records and stats #1083, [feat] Define the team revision once for run records, labels and snapshots #1163
- Unblocks: none
Acceptance criteria
- Workspace scoping matches existing dashboard behavior.
- Live runs and reported history have clear source labels.
- Gate responses reject stale revisions.
- Required gates use the non-agent dashboard channel.
- External web pages cannot submit localhost responses.
- No sensitive workflow content reaches API or HTML.
- Existing dashboard pages and SSE remain intact.
Verification
Focused server/client scoping, record, gate, origin-protection, redaction, and UI-state tests; build/typecheck/lint; one real-CLI dashboard E2E displaying and responding to a gate. Update dashboard and workflow guides in both languages.
Metadata
Metadata
Assignees
Labels
No labels
Activity
SaulMoro commentedon Oct 14, 2026
Notes from #1078 (#1129) for reading live run state:
pending | leased | running | succeeded | failed | skipped.runningis aworkflowstep whose child steps are in progress; the step a driver works on is theleasedone.ship.check.classify), and they exist in the run only once reached. Totals and "current step" cannot be computed from the top-level definition alone.end, the named end it reached; the run's outcome is that end's declared outcome.inputs(the run's, and aworkflowstep's owninputsfor its child) and snapshots of every child definition with their prompts andenvtemplates. A lease's renderedenvis not stored but is rebuilt frominputs. None of these should reach the API or HTML.The engine rules that span files are in
docs/dev/workflow-engine.md, added by #1129.SaulMoro commentedon Oct 15, 2026
Where the page's fields come from:
teamRevisionin the run record ([feat] Define the team revision once for run records, labels and snapshots #1163). It is absent when no pushed commit holds the definitions, so render it as optional.sourceHashis always present.prslist in the end record ([feat] Deliver workflow branches as pull requests #1090). Afor_eachrun can have several, so render the list.Acceptance criteria to add:
teamRevisionrenders without a broken link, and still showssourceHash.prsrenders three links.SaulMoro commentedon Oct 16, 2026
Three things from #1148 for reading runs:
inputsand the definitions, a run now keeps eachfor_eachinstance'sitem, eachfor_eachstep'sresults(every item with its outputs), and the outputs of earlier passes inpassesandrun.archive. An item often comes frominputsor from another step's outputs. None of these should reach the API or HTML.runningholds several leases at once, and--driver localruns up toworkflows.max_parallelcommands. "Current step" is the list ofleasedsteps. There is also a new status,cancelled, for steps an end or a break stopped.stepCountscounts each instance the run ended with once. In one run whose loop ran three passes over two items,stepCounts.totalwas 8 andstepshad 16 entries. Take counts fromstepCounts.Mobile screenshots for the Tencent#1088 Workflow Runs PR
fix(dashboard): keep gate buttons when only a run's duration changes (T…
feat(dashboard): add a Workflow Runs page with HITL answers (#1088) (#…