Skip to content

feat(studio): scores grouped by eval - #747

Merged
LinuxDevil merged 2 commits into
mainfrom
revamp/f19-scores
Oct 24, 2026
Merged

LinuxDevil merged 2 commits into
mainfrom
revamp/f19-scores

Conversation

@LinuxDevil

Copy link
Copy Markdown
Owner

Scores get their own screen (#/evals/scores?eval=&agent=&source=&range=): one row per eval with expandable per-check results, a run pass-rate trend and links to each trace.

Ticket: F19 (Forge Observe vs LangSmith evaluation follow-up)

Changes

  • fix(studio): label eval aggregate figures per score; load a newly opened eval
  • feat(studio): scores grouped by eval

Verification: focused vitest, tsc --noEmit, eslint on changed files (details in the review package); full suite and fallow run in CI.

🤖 Generated with Claude Code

LinuxDevil and others added 2 commits October 25, 2026 02:14
#/evals/scores is its own screen now: one row per eval from
?aggregate=eval (pass rate, scores, mean, last seen); expanding a row
(open=) loads that eval's rows and shows the pass-rate trend from the
eval-level scores (one mean point per bucket), per-check pass rates and
the newest failures, each linking to #/traces/<id>?obs=<obs>. Filters
eval/agent/source/range live in the query string, defaults unwritten.

The daemon-down verdict + retry-while-down is a shared useDaemonDown
hook, now used by the Trace, Monitoring and Scores screens.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ned eval

The aggregate=eval columns span every check score of an eval, so they
read "Score pass rate" / "Mean score" with a tooltip saying so; the
expanded panel's per-run figure is labelled "Run pass rate". Switching
the expanded eval shows Loading until its own rows land instead of the
previous eval's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@LinuxDevil
LinuxDevil merged commit 4a9993e into main Oct 24, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant