We debugged 3 weeks of "the agent just did something weird" tickets. Here's what we found.

Every one of them had the same root cause, just dressed differently. It wasn't a bad prompt. It wasn't a bad model. It was almost always an agent acting correctly on stale or wrongly scoped context, pulling from a memory write that happened three steps earlier, in a different part of the flow, that nobody realized was still "live." The pattern: Agent A writes something to shared memory as a side effect of an unrelated task Agent B reads that memory scope for a completely different reason, weeks later Output looks "wrong," but the agent didn't hallucinate anything, it reasoned correctly off data that shouldn't have still been in scope Once we started tagging every memory write/read with why it happened (not just what happened), the "weird" tickets stopped being mysteries. Most resolved in minutes instead of hours of trace-diving. Curious if others are seeing the same pattern, is it mostly a memory scoping problem for you too, or is stale tool output/retrieval context the bigger offender in your stack? (We ended up building tooling around this at Cartha since it kept recurring across every agent system we touched, happy to go into more detail on the scoping approach if useful, but mainly curious what everyone else's failure mode actually looks like.)