In 38 minutes of active model work, Anthropic’s Claude Fable 5 wrote a complete, bootable NT-compatible Windows kernel in Rust from scratch. The kernel, named ntoskrnl-rs, booted in QEMU, passed all 14 in-kernel self-tests, and raises profound questions about the future of trust in AI-authored critical infrastructure.

What Happened

Security researcher Matt Suiche and Tolmo’s threat research agent “Twinkle” documented the experiment on June 22, 2026. They asked Fable 5 to rewrite the Windows NT kernel (ntoskrnl) in Rust, starting from an empty directory. In a single contiguous session, the model generated approximately 5,100 lines of code across 27 files. The output covered every critical subsystem: scheduler, memory manager, trap and interrupt machinery, object manager, and I/O manager—organized to mirror the original ntoskrnl’s subsystem layout.

The kernel booted successfully in the QEMU emulator and exited with the project’s standing pass contract: exit code 33. The total wall-clock time was about four and a half hours, but most of that was the human operator away from the keyboard; the actual model-active work took just 38 minutes. The feat goes beyond simple code generation—Fable 5 demonstrated the ability to autonomously architect, structure, and debug a complex systems project with no human guidance during generation.

Read the full announcement →

My Take

This is a watershed moment. We’ve seen AI write small utilities, games, and even web apps—but a bootable operating system kernel is an entirely different league. The Windows NT kernel is one of the most battle-tested pieces of software ever written, refined over decades by thousands of engineers. To have an AI replicate its core functionality in under an hour—and have it pass self-tests—is both awe-inspiring and terrifying.

The security implications are enormous. If AI can generate functional kernel code this easily, we have to assume adversaries can do the same. Imagine a threat actor generating a custom malicious kernel that looks legitimate, complete with backdoors woven into the very fabric of the OS. The traditional approach of “trust the source, audit the code” becomes meaningless when the author is an opaque neural network. The community needs new verification methods—perhaps formal verification or hardware-anchored attestation—before we can safely deploy AI-generated system software.

What to Watch

  • Supply chain trust: How will operating system vendors (Microsoft, Linux distros) handle contributions that may be AI-generated? Expect new provenance requirements.
  • AI safety and alignment: Fable 5 produced correct code this time, but a subtle error in memory management or security policy could be catastrophic. We need rigorous testing frameworks for AI-authored systems.
  • Adversarial uses: Cybercriminals will exploit this capability. Watch for custom malicious kernels that evade traditional antivirus by implementing stealth mechanisms at the kernel level.