Bug fixing accuracy from observability data
A public benchmark for the question every debugging agent should answer: what caused the production failure?
We published a benchmark of 22 real production incidents, each with a human-written answer key. An agent reads the codebase, investigates, and writes a root cause. A GPT-4o judge marks it correct only if it names the same incident, the same precise cause, and would lead an engineer to the same fix.
This is not a log summarization task, and it is not a test of whether an agent can name a nearby service. The expected answer is one an engineer can act on: the failing behavior, the relevant signal, and the fault that explains both.
Measured against Cursor with no extra tools, Sentry MCP costs three incidents, Foam MCP gains two, and the Foam agent gains six. An update to the Foam agent on April 12 took it to 19 of 22.
Net numbers hide how much each setup changes. Sentry MCP solved three incidents Cursor alone missed but lost six it had solved. Foam MCP solved four new ones and lost two. The Foam agent solved seven new ones and lost one.
We use this benchmark as a product instrument. If Foam improves here, it means the system is getting better at the work customers actually ask it to do: isolate the fault, explain the evidence, and reduce the time between incident and fix.