Build a 14 KB HTTPS server that boots as its own operating system in assembly

A Redditor had Claude Code, mostly on Fable 5.2, write a 14 KB x86-64 assembly OS that serves static sites over TLS 1.3 in five days, then put a $200 bitcoin bounty on its key.

Done withClaude Code· Nov 20, 2026

What they did

The poster, u/JaguarMoe on r/ClaudeAI, wanted to test how well Claude handles sizecoding. Over five days Claude Code, mostly running Fable 5.2, wrote a static web server that is its own operating system: a boot sector, a network driver, TCP, TLS 1.3 and HTTP, all in x86-64 assembly. A build step takes a folder of files and turns it into a bootable image. The poster chose the scope and what to leave out and did not write the code. Every change was booted in QEMU, and the TLS code was checked against Wycheproof test vectors, tlsfuzzer and Valgrind.

How it went

The finished image is 14 KB. On a 2-vCPU cloud server the poster measured two to three times the new TLS connections and small pages per second of nginx. Code and benchmarks are public on GitHub. To test security, the server's TLS private key is the same number as the key to a bitcoin address holding $200, and the server stays online at 15kb.org until 18 February 2027 for anyone to try. No one had claimed it when the post went up.

Worth knowing

The poster credits the test harness, not the model, for keeping the code correct: boot every change, run known TLS vectors and a fuzzer. One commenter flagged a possible seed phrase in the repo; the poster explained it was only a comment, and the wallet words are generated in RAM and never committed. The post text itself was polished by Claude, which the poster said they regret.

Try it

With Claude Code· 8 parts to fill in

Write [a small static web server / the program I describe] in [x86-64 assembly] that boots directly as its own operating system, with no OS underneath. It must include [the boot sector, network driver, TCP, TLS 1.3 and HTTP] and stay under [size limit in KB]. Take [a folder of files] as input and produce a bootable image. After every change, boot the image in [QEMU] and run the test suite, including [Wycheproof vectors, tlsfuzzer and Valgrind] for any crypto code. Do not add features beyond [my scope list]. Report the image size and test results after each change, and stop when all tests pass within the size limit.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related