Long-running Claude Fable 5 agents had become the backbone of Gene Kim's personal knowledge system, one built from thousands of screenshots, videos, and half-finished side projects, spanning 50 code repositories and tens of thousands of changes. He’d been warned that Fable might be pulled from his subscription and got to preparing for that eventuality. But it disappeared eight days earlier than he planned for, mid-session, when Anthropic suspended access over an export-control issue. As he put it, the ship was soon “on fire, tumbling in space.” Gene’s the coauthor of The Phoenix Project, The DevOps Handbook, Accelerate, and, most recently, Vibe Coding (with previous guest Steve Yegge) as well as founder of the Enterprise AI Summit, so he knows a thing or two about dealing with unplanned disasters. He joined Tim for an encore of the lightning talk he gave at O'Reilly's Foo Camp about how he recovered his system, followed by a Q&A on what the shutdown taught him. Gene described watching his systems fail once the less-capable Claude Opus took over from Fable mid-session. Commands that should have worked started breaking, the model argued with itself over which instance had done what, and every action risked making things worse. It took roughly three hours that night, and more the next morning, to stabilize things, largely by recovering documentation Fable had written along the way, and Gene took the audience through the process step-by-step. He and Tim also discussed the deeper lesson of dependency risk from AI providers. We hear a lot about pricing and availability changes, but export controls, shifting safety policy, and geopolitics can force the same kind of sudden cutoff. Gene helped us understand why the solution is the same preventive, rehearsed resilience DevOps engineers built over the last 15 years for large-scale outages, now applied to individuals running mission-critical agents of their own.
