April 7, 2026
One small glitch, one giant comment fight
We found an undocumented bug in the Apollo 11 guidance computer code
A 57‑year‑old Moon code glitch sparks AI writing drama and “did anyone verify this” fights
TLDR: Researchers say they found a decades-old Apollo computer glitch that could freeze gyro realignment after an emergency, discovered with AI-assisted tools. The comments erupt into an AI-authorship brawl versus calls for proof, with readers demanding verification and even a “using Claude” label added to the headline.
A new claim says the Apollo Guidance Computer—the brains that helped land humans on the Moon—had a tiny, four‑byte mistake that could quietly freeze the ship’s “which way am I pointing?” system if an emergency switch was hit mid‑maneuver. The team says they used an AI helper (Claude) and an open‑source spec tool (Allium) to map the old assembly code and spot the slip. It’s the stuff of space‑nerd legend, with shout‑outs to the hand‑woven “LOL memory” and viral GitHub scans. But the real launch? The comments.
The top fight isn’t about the bug at all—it's about the writing. One camp calls the post “soulless and plastic” and insists it reads like AI slop. Another gushes, “literal chills,” blasting the cynics for dunking on good prose just because it’s polished. Meanwhile, a practical crowd piles in with, “Has anyone verified this?” asking for reproductions and test cases before everyone throws a parade. And then there’s the headline police: “Please add ‘using Claude code’ to the title,” because when AI touches anything, it must be labeled like a peanut allergy.
So yes, there’s a claimed Moon‑era bug that could lock up gyro realignment. But the community drama? It’s a three‑act play: suspicion of AI‑authored everything, defense of beautiful writing, and the eternal nerd refrain—pics or it didn’t happen. Space history, meet comment‑section chaos.
Key Points
- •Researchers report an undocumented bug in the Apollo Guidance Computer: a leaked LGYRO lock in the IMU gyro torque error path when the platform is caged.
- •They used Allium and Claude to derive behavioral specifications (12,500 lines) from 130,000 lines of AGC assembly, modeling shared resource lifecycles.
- •In normal completion (STRTGYR2), the lock is released; on the BADEND path triggered by caging mid‑torque, the lock is not cleared due to two missing instructions (four bytes).
- •Once LGYRO remains set, subsequent gyro torques hang indefinitely, blocking fine alignment, drift compensation, and manual torque operations.
- •Prior scrutiny focused on code reading, emulation, and transcription verification; no published formal verification or static analysis had addressed the flight code.