Extensions that deepen your project-fitted loop.

Import exported OpenTelemetry / OpenInference / local-JSON traces today — no SDK, no network. A live pull from Langfuse, Phoenix, and LangSmith is an opt-in lane reachable with the connect --live verb experimental — off the required path, a pull is proposed and cannot gate.

Scaffold a proposed metric or judge for you to review — never an approved threshold.

Planned and opt-in — governed before it is built. No generator ships today; a Core scenario generator is planned, and Intelligence offers commercial targeted scenario search. Whichever runs, every generated case lands proposed and can never enter as validated reference data or self-approve a gate. Recorded in a public ADR.

Not a Core extension: application-specific metric discovery — deep-reading your code, output schemas, prompts and any traces to propose a typed MetricCatalog of what to measure — is EvalGlass Discovery, a separate product (private preview). Core executes what you define; every proposal lands proposed.

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.

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.

Send a copy of your scorecard to an optimizer — EvalGlass never edits your prompts.