Does Tessary's frustration classifier see the whole conversation, or just the last few turns?

Just the last two turns before the one it’s scoring, not the whole thread. The classifier sends its decision model the scored message plus the four messages from the two turns right before it, using only each turn’s actual reply and skipping the tool calls inside those turns and any sub-agent’s own output. A fix this month closed a real gap in that: the old version scanned a fixed batch of recent spans instead of counting turns, so a turn packed with tool calls could push the real replies out of the window entirely and leave a message scored with too little context, or none at all.

The tradeoff is reach, not accuracy. Frustration that surfaced several turns back and hasn’t recurred since won’t feed into the current turn’s score, the same kind of context boundary that trips up an agent losing track of instructions given much earlier in a conversation. Each new turn gets scored again, though, so frustration that keeps recurring stays visible as the conversation continues.

sources

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