I remember the first time I saw an IBM XT. It was beige, bulky, and had a green monochrome monitor. The most exciting thing it could do was run Lotus 1-2-3. Now, 40 years later, that same machine can run a graphical operating system that looks like a Mac — and it was written by an AI.
You’ve probably never thought about real-mode assembly. It’s the kind of code that talks directly to the CPU, with no abstraction. It’s the language of memory addresses and register manipulation. It’s tedious, error-prone, and almost nobody does it anymore. Unless you’re an AI.
The real breakthrough isn’t that we can run a retro OS. It’s that Claude wrote the assembly.
The project is called os8088. It’s a Mac-like desktop for the Intel 8086, written entirely in real-mode assembly with help from Claude. It runs on actual IBM XT, 286, and 386 hardware. It supports FAT12 and FAT16 filesystems. It has apps, games, Sound Blaster audio. Hard drive support is coming. And it looks like something straight out of 1985 — but never existed.
You might think this is a nostalgia trip. A toy for retrocomputing enthusiasts. But you’d be wrong. This is a signal that the most important impact of AI might not be in chatbots or image generators — it’s in systems programming.
We’ve been told that AI will revolutionize software development by writing boilerplate code, generating unit tests, and summarizing pull requests. All true. But the real frontier is the low-level stuff: the code that runs on bare metal, the firmware, the drivers, the operating systems. The kind of code that humans have been writing for decades with painstaking attention to every byte.
Now an AI just wrote a complete graphical OS for a 40-year-old CPU. And it works.
Let’s be clear about what happened. The developer didn’t prompt Claude to “write an OS.” They guided it, iteratively, through the maze of real-mode assembly constraints. They provided the architecture, the vision, the debugging. But the AI did the heavy lifting — writing the assembly instructions, managing memory, handling interrupts. This is the first credible example of AI-generated systems code that runs on real hardware.
And it changes the calculus. Think about what this means for embedded systems, for legacy hardware, for space and defense applications where you need to squeeze every cycle out of a chip. The cost of writing low-level code just dropped dramatically. The barrier to entry for custom hardware just got lower.
But there’s a deeper lesson here. The project didn’t chase the latest GPU or the cloud. It went backward — to a machine with 640KB of RAM and a 4.77 MHz processor. It proves that the combination of human curiosity and AI capability can unlock creative potential anywhere, even in the most constrained environments.
I spoke with the creator (who prefers to remain anonymous). He said: “I wanted to see what the IBM XT could have been if someone had pushed its limits. With Claude, I could actually build it.” That’s the magic. Not the technology itself, but the permission it gives us to explore.
We’re used to thinking of AI as a tool for efficiency. But maybe it’s also a tool for imagination. The most important programming language of the future might not be Python or Rust — it might be whatever the AI decides to write in.
If you’re a developer, this should make you think. The skills you thought were safe — assembly, low-level optimization, hardware interfacing — are now on the table. The AI is coming for the metal. And that’s not a threat. It’s an invitation. To build things that were previously impossible. To resurrect forgotten platforms. To create new ones.
So yes, os8088 is a cool project. But it’s also a warning and a promise. Curiosity, constraint, and a little help from an AI can still produce magic. And the first place that magic happened was on a 40-year-old computer.
FAQ
Q: Is this just a gimmick? Can an AI really write reliable assembly?
A: It's not a gimmick. The OS runs on real hardware, with verified functionality. The AI wrote the assembly, but a human guided it. The quality is comparable to human-written assembly. It's a proof of concept that AI can handle low-level systems programming.
Q: What does this mean for developers working on modern systems?
A: It means AI can now assist with firmware, drivers, and embedded systems — areas that were previously resistant to automation. It lowers the barrier to writing optimized code for old and new hardware. Developers should start exploring AI-assisted systems programming now.
Q: Isn't it dangerous to let AI write assembly that runs on bare metal?
A: It's a tool, not a replacement. Human oversight is still required. But the risk is worth the reward: we can now explore architectures and platforms that were too costly to develop manually. The real danger is ignoring this capability and falling behind.