What does replay show that a trace viewer does not?

Replay shows what would happen if you changed one thing, the prompt, a tool result, or a config setting, and re-ran the rest of the turn against the original context, so you can watch whether the model’s decision changes. A trace viewer only shows what happened: the messages, the tool calls, the outputs, laid out for reading, not what a different input would have produced. That’s the test a fix actually needs, not “does this look better” but “does the agent behave differently on the exact case that failed.” A viewer can tell you a tool returned a stale price; only replay tells you whether fixing that field would have stopped the bad response, on the same case, not a similar one.

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