moot✳
A little more connected.
Join Moot

I built a web browser from scratch in Rust with Claude Code — 90%+ WPT compliance, 97.8% ECMAScript, and 100% WebAssembly. No Chromium, no WebView.

So apparently I've spent the last few months building a web browser from scratch in Rust. With Claude Code helping me along the way, it's somehow turned into a real browser engine.

Meet T.A.B. (Tiny Ass Browser), powered by my Kingmaker engine.

And by browser, I don't mean another Chromium fork, Electron app, or WebView wrapper. I mean the whole ridiculous thing.

It's got its own JavaScript engine, bytecode VM, JIT compiler, DOM implementation, CSS layout and painting pipeline, WebAssembly runtime, and rendering stack. It's also designed to be headless-first, because I wanted something agents could actually operate without dragging an entire Chromium instance around.

Current conformance results:

  • WPT Testharness: 91.42%

  • ECMAScript / Test262: 97.83%

  • WebAssembly: 100%

  • Combined conformance: 92.21%

  • 1,763,775 passing test results across five suites

The combined dashboard includes results inherited from previous runs, so not all five suites were freshly remeasured together.

The screenshots are actual pages running in my engine. Google, HEY, 37signals, and a couple of my own projects (cass.tools and kosmos.tools). There's also my animated new-tab page and the conformance dashboard I've been using to torture myself.

A few things I've been focusing on:

  • Keeping memory usage low, including on machines with older GPUs.

  • A small dependency footprint, with a statically linked Rust build.

  • Minimizing unnecessary Arc, Mutex, and unsafe usage.

  • Making the engine useful for both humans and autonomous agents.

  • Getting real web compatibility rather than making a handful of demo pages look pretty.

Claude Code has been a huge part of the development workflow. I handle the architecture and direction, and use agents heavily for implementation, debugging, and testing. The Rust compiler and upstream conformance suites get the final say on whether something actually works.

It's definitely not finished. Some websites still break spectacularly, and the remaining WPT failures are a special kind of psychological warfare. Every time I fix one rendering issue, I discover another obscure browser behaviour that somebody apparently standardized in 2008.

But it runs real websites, executes real JavaScript, and I'm getting increasingly close to having something genuinely usable.

I'm building this solo, largely because I wanted to see whether a modern browser engine could be built differently, with less memory overhead and without inheriting decades of architectural baggage.

Turns out browsers are complicated. Who knew?

Happy to answer technical questions about the engine, architecture, conformance testing, or how I've been using Claude Code to build it.

0
1 comments
1 comments

I'm sure there's absolutely no security issues with this browser at all.