vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

swarm-ui: a review runs page lists the review classifier's recent runs

Browse source 
One card per run, newest first, from GET /api/review-classifier/runs: repo,
PR, head commit, trigger, when, how long, how many classifications and the
outcome as a badge. A card opens to the try-out's result table, the overall
verdict, the reason and the posted review's link. TryOutResult takes the
answer it shows rather than a whole try-out result, and its styles move to
their own file.
This commit is contained in:
iris 2026-10-12 18:53:06 +02:00 • committed by mara
commit 5193a101a6
9 changed files with 355 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

28
docs/swarm/ui.md
View file

@ -16,6 +16,7 @@ domain, covers host-level detail for one hive.
| `/jobs` | the controller's job graph — where agent creation and credential mints show progress |
| `/schedules` | the scheduled prompts: add, edit, pause, resume and remove |
| `/issues` | a cross-repo issue report |
| `/review-runs` | the review classifier's recent runs: which PRs, what it answered, which failed |
| `/review-tryout` | try a review classification against a real PR |
Everything it shows comes from [`swarm-controller`](../../swarm-controller/README.md).
@ -53,6 +54,33 @@ page. Selecting outside it, or Escape, closes it. You can stop or pause the
agent, or link an account, without leaving the terminal. A subagent's tab opens
its agent's details.
### Review runs
`/review-runs` lists what the [review classifier](review-classifier.md) has
run, newest first, one card per run. A card shows the repo and PR, the head
commit, whether the run was a try-out or a requested review, how long ago it
started, how long it took, how many classifications ran, and the outcome as a
badge. Select a card to open it: it shows the same result table as the
[try-out](#review-try-out), the overall verdict, the reason when the outcome
has one, and a link to the posted review when there is one.
An outcome can be more than approve or request changes:
| badge | what happened |
| ------------------- | -------------------------------------------------- |
| `approved` | the run posted an approval |
| `changes requested` | the run posted a request for changes |
| `comment only` | there was no clean verdict, so it posted a comment |
| `queue full` | the queue was full, so it turned the run away |
| `post failed` | the run finished but posting the review failed |
| `done` | a try-out finished |
| `failed` | the run failed; the card says why |
The page refreshes every 30 seconds, and a card you opened stays open when it
does. An empty list says there are no runs yet, and a failed load shows the reason the
controller gave. The page shows no token counts, cache counts or cost, and
stores and posts nothing.
### Review try-out
`/review-tryout` shows how the [review classifier](review-classifier.md)