Why does a fixed agent bug come back weeks later?

A fixed bug comes back when nothing keeps checking for it after the fix ships. It’s easy to verify a fix against a hand-written test that describes the bug in general terms, merge, and move on, while the actual failing trace, the one with the specific message history and tool outputs that triggered it, never becomes a permanent check. Weeks later, a different change reintroduces the same condition, and nothing catches it, because no test was built from the original case. The fix that holds is the one where the replayed failure becomes a regression case: the exact trace, kept, and run against every future change. Keeping that case as a standing check is what stops the bug from coming back.

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