Does Tessary store images from my agent's traces?

Yes. When a span’s input or output includes an image, a screenshot, a diagram, whatever your agent passed to or received from a model, Tessary stores it alongside the rest of that span’s content instead of dropping it. Media is deduplicated: the same image showing up across multiple traces, which happens often with a repeated screenshot or a shared reference document, is stored once and referenced from every span that used it rather than copied per trace.

The reference lives in the span’s payload the same way a tool call or a retrieved document does, so when you open a trace, the image is part of what you see, not a separate lookup. This applies to any span carrying media, not just LLM calls, so a tool that returns an image is captured the same way a model call that received one is.

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