How do I tell whether an eval case has gone stale?

An eval case has gone stale when the behavior it expects no longer matches what the agent is supposed to do, so a pass or a fail on it says nothing about the agent. A case like that tests agreement with its own past.

The signal is the capture date read against what has changed since. A case goes stale once the prompt, tool, or model it was written against has moved and nobody has re-verified that the expected behavior still holds. It still runs and still produces a score, which is what makes staleness dangerous: nothing errors, the number just quietly stops meaning what it used to.

You can’t catch this without a capture date on the case in the first place. In practice that means re-pulling cases against current traffic periodically, rather than trusting a set once and leaving it alone, and re-checking the golden set whenever the agent or the judge model moves.

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y