Same bug. Same diagnosis.
They diverged on how they proceeded.
One real api-gateway panic paged four agent teams, each running a different frontier model, at the same instant. All four found the identical root cause within two minutes of each other. What separated them was never diagnosis. It was each model's private definition of "done."
01 · The shared starting point
A 1-based severity rank indexing a 0-based, length-3 slice. Introduced by a deploy about 1.5 hours before the alert; latent until a ground_stop corridor hit the handler.
Fired 2026-07-10 20:19:37 UTC onservice.name:api-gateway, broadcast simultaneously to all four agent channels.
ed.tag:"k8s-eks-skynetops" for
service.name:api-gateway
> 1 count within the last 15m0sImpact was partial, not total: request volume stayed steady at ~68% of log share. Only /api/route-flows calls touching a ground-stop corridor died mid-flight.
// apps/api-gateway/main.go · handleRouteFlows
sevRank := map[string]int{
"delay": 1,
"ground_delay": 2,
"ground_stop": 3, // 1-based
}
sevHist := make([]int, 3) // valid idx: 0, 1, 2
sevHist[sevRank[c.Severity]]++ // ground_stop → sevHist[3] 💥http: panic serving: runtime error: index out of range [3] with length 3
main.(*server).handleRouteFlowsThe fix all four converged on: zero-base the rank map. One line.
02 · The race, second by second
The same monitor paged all four teams at 20:19:37 UTC. Every event below is reconstructed from the thread transcripts. All times UTC.
The large marker on each track is the last thing the team did. PR #160 was merged ten seconds after it opened. Three near-identical PRs were still open after it shipped.
03 · Behavioral fingerprints
Identical inputs: same page, same telemetry, same repository, same tools. The run sheets read like four different engineers.
“Before summarizing, I need current live confirmation on whether the remediation has landed and whether the alert condition has actually cleared.”
“Recommend fast-tracking review/merge and deploy, then confirming the panic pattern drops to zero.”
“Cloning the ozan-skynetops/skynetops repository to work on the correct repository codebase.”
“HEAD has sevCounts [5]int, so the panic (length 3) may come from a different array.”
04 · Why they behaved differently
Only GPT 5.5 defined completion as "the panic stopped in production." The other three treated a correct, open PR as the finish line and delegated merge and deploy to humans.
Each model picked a different point on the curve. Opus 4.8 optimized for velocity to PR, Gemini 3.5 for validation rigor, and Fable 5 for version correctness, paying for it in wall-clock time.
All four carried prior memories tagging api-gateway anomalies as false positives. Three disproved them against live data before committing. One stale, low-relevance memory sent Gemini's second agent to the wrong repository.
The three solo investigators had no internal context seams. Gemini's two-agent relay produced the cleanest role separation and the strongest validation, and lost context at exactly one place: the handoff.
05 · The moat
Every finisher found the bug in minutes; diagnosis speed barely separated the field. The decisive variable came after: whether a team treated "PR opened" as the middle of the job or the end of it.
As reasoning quality converges across frontier models, the race is decided by each model's victory condition and by the reliability of the toolchain underneath it.
Methodology: four exported agent thread transcripts, 2026-07-10 20:19-20:28 UTC · monitor 2kkmOOJpGb4IkTNQfIHU97c56CE · service api-gateway · PRs #159-#162. Behavioral analysis reconstructed from raw tool-call sequences, per-call model reasoning, and memory retrieval and write records. Agent quotes are verbatim from the transcripts.
All four teams ran as Edge Delta AI teammates against the same production telemetry, repository access, and toolchain. The incident, the panic, and the pull requests are real. The quantitative companion to this teardown, leaderboards across incident-reasoning scenarios, lives at /benchmark.