We found an undocumented bug in the Apollo 11 guidance computer code

A tiny leak with big lore

It has been reported that researchers digging through the Apollo Guidance Computer (AGC) discovered a previously unnoticed bug: a resource lock in the gyroscope control code that can be left held on an error path, silently preventing the platform from realigning. Allegedly, two instructions — CAF ZERO and TS LGYRO, just four bytes — are absent on the “BADEND” exit path used when the IMU is physically caged. Once LGYRO is stuck, every subsequent torque attempt sleeps forever, waiting for a wake signal that will never come. Tiny, stubborn, and oddly human — a hiccup buried in one of computing’s most studied artifacts.

How they found it

The team used Claude and Allium, their open-source behavioural specification language, to distill roughly 130,000 lines of AGC assembly into some 12,500 lines of machine-derived specs, and it has been reported that that distilled model pointed straight at the defect. This wasn’t another pass of human reading or bit-for-bit emulation — long the habits of AGC caretakers — but a resource-lifecycle analysis that maps when locks must be acquired and released. The result: a code path that emulators and generations of curious developers had missed. Who would have guessed formal specs would out-snoop decades of human scrutiny?

Why it matters

The AGC is part codebase, part cultural relic: core rope memory woven by the “Little Old Ladies,” a 2K erasable RAM machine that helped send humans to the Moon. There’s no evidence this bug affected Apollo 11’s flight, and it has been reported that the discovery is retrospective, not a mission-critical failure report. Still, the emotional sting is real — Michael Collins orbiting alone while his crewmates walked on the surface is the human counterpoint: three billion people, and a four-byte omission could have mattered. The finding is a neat reminder that even the most pored-over software can hide surprises, and that modern formal methods can illuminate corners classical techniques never quite reached. Who knows what other ghosts are left in the codebase?

Sources: juxt.pro, Hacker News