Does a calm bug report count as frustration?

No, a calm bug report reads as neutral: the frustration classifier only flags messages that carry annoyance, anger, or disappointment in the words themselves, and a flat, matter-of-fact description of a problem doesn’t.

The neutral label explicitly covers calm, curious, or positive messages, including a bug report with no emotional charge in it. “My export button returns a 500” and “why does your export button still not work” describe the same failure, but only the second carries the tone the classifier is built to catch.

This is deliberate, not a blind spot. Frustration and severity are different signals: a calm bug report can point at a critical failure, and a furious message can be about something trivial. Conflating the two would make the classifier redundant with error-rate monitoring, which already catches thrown exceptions and failed tool calls. What it adds is visibility into agents that are technically working but making people miserable anyway, and that only shows up in how people write, not in what broke.

keep reading

More on this.

Can the frustration classifier tell why a user is upset, or just that they are?Just that they are. It scores the tone of what someone wrote, not the reason behind it, so it can't say what the user is actually upset about.answer →Does one frustrated message trigger an alert?No. One message writes a finding, not an alert. It only becomes a case if triage rules it a real, recurring problem rather than one bad moment.answer →What is Tessary's frustration classifier?A built-in classifier that reads every user message in a trace and flags annoyance, anger, or disappointment at the situation or the assistant.answer →Everything on tessary frustrationThe definition, and every question answered under tessary frustration.concept →

Send us the traces you already emit.

book a demo