AI-Built Web Browser: Claude Writes One in Rust

Screenshot of the AI-built web browser SWB written in Rust

A developer has spent about seven weeks letting an AI agent write a web browser from scratch in Rust, and the AI-built web browser is now good enough for daily reading. The project is called SWB. Its creator gave Claude no technical direction at all and paid nothing beyond a Claude Max subscription they already had.

The result runs on Linux, handles ordinary websites and comes to roughly 400,000 lines of code.

The experiment

The developer has run vibe coding tests on new models for about a year and a half, usually asking an agent to build a small game from a one-sentence description. Newer models handle that easily, so the test moved to something harder: how an autonomous system behaves over time on a big project.

In early October, they started building a browser. It’s among the most complex software people use, supports a huge number of features, has to be fast and runs untrusted code. That is why few browser engines exist. Chrome uses Blink, Safari uses WebKit and Firefox uses Gecko, while Edge and most others reuse Blink. Ladybird is building its own. A new browser also needs a JavaScript engine, which doubles the work if you skip V8.

The ground rules

The developer only says which pages must work: BBC, Ars Technica, Hacker News (reading and posting), Wikipedia, OpenStreetMap and GitHub. Benchmarks and test suites don’t matter. The AI picked Rust and chooses its own libraries.

  • No copying code from Chromium, Firefox or Ladybird.
  • No reusing finished engines such as Servo, Blink or V8.
  • General-purpose libraries for things like image decoding are allowed. Anything browser-specific must be written from scratch.
  • Every library and idea must be tracked for licensing and provenance.

Clean-room work is allowed. The agent writes a test, runs it in Chromium, watches the behavior and implements the same thing. On the BBC page, all 2,745 elements land within 2 pixels of where Chromium puts them.

No technical input, no spending

The developer doesn’t read or write Rust and hasn’t taken part in technical decisions. When the agent asks anyway, it recommends an option, and the answer is always to do what it recommends.

The other constraint was cost. The project runs on spare capacity from a Claude Max plan ($100, or €90, a month), only until the weekly limit. It’s slower, but free. On API tokens or extra credits, the developer estimates the bill so far would be $7,000 to $10,000.

What works today

After less than two months, the browser is used for regular reading. Complex JavaScript apps are still weak. It runs JavaScript through its own interpreter, not a JIT, and supporting the long tail of platform APIs will take a while, though many that most sites need already work.

SWB stores nothing on disk. Cookies and local storage live in memory and vanish on close, so it works like an incognito browser. The developer added an “Open in SWB” right-click option in their main browser for random links.

The codebase has about 400,000 lines of Rust, 500,000 lines of tests, 130,000 lines of tooling and 60,000 lines of documentation and specs. The stripped binary is around 35MB. It targets Linux only.

Fixing the process

The first few days went badly. Claude ran many sub-agents in parallel, and they edited the same files, creating conflicts that ate tokens. The project looked like it would collapse.

The fix was one agent and one task at a time: implement, review, integrate, test, then move on. Sub-agents still keep each task’s context manageable. Opus 5.5 takes the hardest work, Sonnet the easier development, and Haiku the elementary jobs such as parsing output or deciding what to run in a shell. That also helps cost and speed.

Code quality and what comes next

The developer admits not knowing the code quality, since they never look at it. Treated as a black box, it hasn’t hit a wall at 400,000 lines.

There are no specific goals. Claude keeps working on SWB with spare tokens, and the developer believes other frontier models such as GPT-6.x could manage something similar. The code is on GitHub as senko/swb under the MIT license, and anyone can point their own agent at it, for example to port it to another platform.

Source: Senko Rašić

Written by

Saksham Bhargava

Saksham Bhargava runs Alteroid and has been writing about consumer technology for over five years, covering iPhone, Android, Windows, AI tools and gaming. With an MCA and six years of hands-on web development experience, he tests the features he writes about on his own devices and focuses on clear, practical guides that solve real problems. Away from the screen, he enjoys travelling to places most tourists skip.