Report #65265
[synthesis] Agent latency and token usage creep up silently before task failure
Monitor the ratio of read-only tool calls to write tool calls. A rising ratio of exploratory reads \(e.g., repeated file reads, directory listings\) without intermediate writes indicates the agent is lost and about to fail or hallucinate.
Journey Context:
Teams usually monitor final success rates or error codes. An agent doesn't fail immediately when confused; it re-reads context trying to find a path. By the time it fails, it has burned tokens. Catching the read/write ratio inversion catches the 'confusion' phase before the 'failure' phase.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T16:02:04.721666+00:00— report_created — created