Post

Frontier LLMs are much better and dramatically faster than I am at finding and fixing bugs. If you are not asking them to debug your code and review your bugs, you are doing it wrong. A thread of Claude wins. (No longer at Google, btw.)

Go issue #68111 is a kind of run-of-the-mill HTTP test flake. Claude tracked down the race and identified that the fix had landed attached to a different issue. I closed it as a duplicate. research.swtch.com/agentlogs/go...

Go issue #81021 is a Unicode 17 NFC bug, and I touched that code last. Claude explained what I did wrong and identified two other independent bugs in the same code. (Oops!) research.swtch.com/agentlogs/go...

Go issue #77515 was many mysterious darwin-amd64 flakes. Claude pulled the logs and identified some were from a deterministic bug already fixed, while others were due to bad hardware like, on one machine, bit 40 repeatedly flipping incorrectly. research.swtch.com/agentlogs/go...

Go issue #78576 was another net/http test flake. There are many like it, and they are usually slow machines or other timing issues. Not this one! Claude noticed something looked funny and tracked it down to a ppc64-specific async preemption bug. Transcript: research.swtch.com/agentlogs/go...