What is drift in an AI agent?

Drift is any change in an agent’s behavior or output quality that happens without anyone deliberately changing what it’s supposed to do, whether the cause is a model provider updating a model version underneath you, a prompt someone tweaked, or the world the agent describes moving on without it. It’s borrowed from two older machine learning terms, data drift, where the inputs a model sees start to look different, and concept drift, where the correct answer for the same input changes, but an agent can drift for reasons neither term was built for, like a tool’s API changing shape.

The practical difference from a regression is timing. A regression traces to one change you can point at; drift is what you call the same kind of quality drop when nothing in your own history explains it, which usually means the cause is upstream, in the model or the world, not in your code.

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