Group a run's failing and non-scored cases by shared cause (Scorecard.clusters) — “the 18% that failed are all missing-citation cases,” not one flat number. A non-scored case is grouped by cause, never coerced to 0.0.
Extensions
Add the evaluation team when you need it.
Extensions deepen the same repo-native loop — bring behavior in, turn it into checks, review uncertainty, and send scorecards where your team works. Each is an optional, removable specialist move, not a hosted product suite, and none of them decides your scores.
Every add-on keeps the same promise.
Optional, removable, and never authoritative — an extension can bring behavior in or send a scorecard out, but it can never grant a gate or change a verdict. You say what counts.
Bring behavior in
Get your AI application’s real behavior into EvalGlass.
Turn behavior into checks
Shape project-specific checks around your product’s behavior — they land proposed, never authoritative.
Scaffold a proposed metric or judge for you to review — never an approved threshold.
A decided non-goal, not a backlog item — governed, not generated: no generator ships, by design. Any generated case would land proposed and could never enter as validated reference data.
The discovering-metrics skill reads your code, output schemas, prompts, and any traces — across any agentic framework — and proposes a typed MetricCatalog of what to measure. With no traces yet, your output schema alone drafts a contract-tier structural floor; everything lands proposed.
Review and improve truth
Bring human judgment in where uncertainty matters.
Route uncertain examples to human review; validated truth returns to your repo.
An LLM judge can’t gate your build until it’s calibrated to your labels.
An opt-in subprocess judge — the host provides a command EvalGlass invokes to score. It lands uncalibrated → informational and cannot gate until it is calibrated to your labels.
A generic OpenAI-compatible transport that imports no provider SDK; rubrics are host-injected, and the lane is authority-free and deletable. Opt-in, uncalibrated → informational.
See what regressed since your last run — only when the two runs are comparable.
Use results
Act on your scores — you decide what gates.
Fail the build only when an approved gate is breached — never on a fresh, informational run.
Send scorecards outward — local export now, a hosted view is next. No telemetry; the repo stays the source of truth.
A separate, still-planned view: browse deltas and distributions across runs by call identity — a different axis from the clusters above.
Send a copy of your scorecard to an optimizer — EvalGlass never edits your prompts.
Related