Adds a way to exclude specific models from the /ui scoreboard and keep it persistent across reloads — for retired models (e.g. m1) you don't want cluttering the view.
What it does
Per-row × on each model in the scoreboard hides that model.
Hidden models drop out of the table, the totals line, and the findings drill-down.
A hidden (N): … bar shows them as click-to-restore chips, plus a show all button.
Persisted in localStorage (grt-hidden) — survives reloads, same convention as the existing token/curve.
Deliberately not rescoring
Solo-ness is still computed against all models (the global reporter set), so hiding a model is a pure view filter — it never turns another model's shared finding into a fake "solo" find.
All client-side (the daemon stays a pure fact store). go build clean; the dashboard JS passes node --check; README Dashboard section updated. Ships on the next image rebuild (//go:embed ui.html).
Adds a way to exclude specific models from the `/ui` scoreboard and keep it persistent across reloads — for retired models (e.g. `m1`) you don't want cluttering the view.
### What it does
- **Per-row `×`** on each model in the scoreboard hides that model.
- Hidden models drop out of the **table, the totals line, and the findings drill-down**.
- A **`hidden (N): …`** bar shows them as **click-to-restore** chips, plus a **show all** button.
- Persisted in **`localStorage`** (`grt-hidden`) — survives reloads, same convention as the existing token/curve.
### Deliberately *not* rescoring
Solo-ness is still computed against **all** models (the global reporter set), so hiding a model is a pure *view* filter — it never turns another model's shared finding into a fake "solo" find.
All client-side (the daemon stays a pure fact store). `go build` clean; the dashboard JS passes `node --check`; README Dashboard section updated. Ships on the next image rebuild (`//go:embed ui.html`).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Each scoreboard row gets a × to hide that model — for retired ones (m1
etc.) you no longer want in the view. Hidden models drop out of the
table, totals, and the findings drill-down; the set persists in
localStorage (grt-hidden) across reloads, with a "hidden (N): …" bar of
click-to-restore chips + a "show all".
Solo-ness is still computed against ALL models (hiding is a view filter,
not a rescoring), so hiding one model never fakes another's solo finds.
README Dashboard section updated.
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
steve
merged commit 2f003dd132 into main2026-06-28 00:39:33 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds a way to exclude specific models from the
/uiscoreboard and keep it persistent across reloads — for retired models (e.g.m1) you don't want cluttering the view.What it does
×on each model in the scoreboard hides that model.hidden (N): …bar shows them as click-to-restore chips, plus a show all button.localStorage(grt-hidden) — survives reloads, same convention as the existing token/curve.Deliberately not rescoring
Solo-ness is still computed against all models (the global reporter set), so hiding a model is a pure view filter — it never turns another model's shared finding into a fake "solo" find.
All client-side (the daemon stays a pure fact store).
go buildclean; the dashboard JS passesnode --check; README Dashboard section updated. Ships on the next image rebuild (//go:embed ui.html).🤖 Generated with Claude Code