AI is building me a web browser
Anthropic IPO'd the other day at a $1.5T valuation, in one of the largest IPOs ever. Here's the announcement, as shown by a web browser that Claude has been writing for me for the past seven weeks:

It's a good time to look back at how far we've come with AI. Just a few years ago, many of the things we now take for granted were science fiction.
About a year ago, I ran a small internal workshop on AI-assisted software engineering: the pros and cons, and what we can and can't do with AI in the context of coding. At the time, saying you can rely on AI for a lot of your coding was still a strange and unorthodox position. A year later, it's received wisdom. Most software developers have embraced AI for coding, some to a larger extent, some to a smaller one.
Vibe coding and dark factories
The bleeding edge is giving the AI ownership of the entire software product, and not caring about the code at all. This is (sometimes derisively) called vibe coding and can work great for smaller apps, non-developers, and low-risk use cases.
But what about large and complex products? Can AI do all of the technical work there on its own, or does it still need some hand-holding? This dark factory (or software factory) pattern, in which AI agents (or teams of agents) run the entire software development lifecycle without any human involvement, is slowly gaining traction.
The experiment
For about a year and a half, I've been doing vibe coding tests on new models. I give the AI agent a one-sentence description of a small game and let it build the game in HTML, CSS and JavaScript. For the newest models, this is now an easy task, and the differences are mainly in the interpretation and effort put in, not the “intelligence” of the model.
I wanted something much more complex. I'm less interested in what a model can do in one step, and more in how a completely autonomous AI system behaves over time, on a large project.
So in early October, I started an experiment: build a web browser from scratch.
A web browser is probably the most complex piece of software we use every day, possibly more complex than the operating system it runs on. It supports a huge number of features, it needs to be fast, and it runs untrusted code. It's a very specialized, but extremely powerful virtual machine.
That's why there are so few different browser engines in actual use. Chrome has Blink, Safari has WebKit, Firefox has Gecko. Edge uses Chrome's Blink, as do most other browsers. Ladybird, in the works for quite a while now, has its own engine. Building one from scratch is so hard that almost everyone reuses one of the big ones.
And a browser is also a JavaScript platform. If you also need to build a JavaScript engine from scratch, instead of reusing something like V8, you have double the work.
The setup
The project is called SWB: a web browser written from scratch in Rust by an AI agent, completely autonomously.
I only tell it which pages should work in the browser. For example: I need to be able to read BBC and Ars Technica, read and post to Hacker News, and use Wikipedia, OpenStreetMap and GitHub.
I don't care about benchmarks or synthetic tests (JavaScript tests, CSS tests, Web Platform Tests). I just want the pages on my list to work.
I don't care about the technical implementation either. The AI chose Rust, and it chooses which libraries and frameworks to use.
I gave the project a few ground rules:
- No copying code from existing browsers. It can't just copy-paste code from Chromium, Firefox or Ladybird.
- No reusing finished engines. It can't just use Servo or Blink, or the V8 JavaScript engine.
- General-purpose libraries (image decoding, showing stuff on screen and so on) are fine. Anything specific to browsers, it has to implement on its own.
- Keep track of licensing and provenance. I want to know which libraries it uses. If it read a blog post with an idea of how to approach a problem, it should reference it. Everything it uses in any way to figure out how to build the browser gets recorded.
Copy-paste is out of the question, but a clean-room implementation is fine. For example, to match some of the things Chromium does, it writes a test, runs it in Chromium, looks at how Chromium behaves, and implements the same behavior. It runs a lot of these tests and comparisons. On BBC, for example, all 2,745 elements on the page are within 2 pixels of where Chromium puts them.
After that, I just let it rip.
No technical input from me
Throughout the project, I haven't been involved in any technical decisions. I told it not to ask me about them. When it does ask anyway, it recommends an option, and my answer is always “do whatever you recommend”.
I intentionally removed all technical input from my side and let it control everything. I only look at it from the product side: what it should do and how it should work.
No money either
The other important constraint was that I didn't want to spend any money on this. Literally none.
I have a Claude Max subscription (the $100, or €90, per month one), and I usually don't use it up to the weekly limits. So Claude only works on SWB with my spare capacity, until I reach the weekly limit. It's a slower process, but it doesn't cost me anything. Had I used API tokens or bought extra credits for this, it would have cost me around $7,000–$10,000 so far.
Results
After less than two months, I have a browser that I use for regular browsing, in the sense of reading websites.
It's not great at complex JavaScript apps. It does run JavaScript, with its own JavaScript engine (an interpreter, not a JIT). But there's a huge number of platform APIs (the APIs the browser makes available to JavaScript), and supporting most of them will be a really long slog. Claude is chugging along on it, and many of the things most sites use already work.
SWB doesn't store anything on disk. Cookies and local storage live only in memory and are cleared when you close it. So I use it as an incognito (private mode) browser. I have an extension in my main browser that adds “Open in SWB” to the right-click menu. I use it to open random links, so they don't store cookies or try to track me across the web.
It runs on Linux, which is what I use, so I didn't build it for Windows or Mac. If you want to port it, point your agent at the repo and tell it to port it to your platform.
The codebase so far is around 400k lines of Rust code for the browser, an additional 500k lines of tests, 130k for tooling, and around 60k lines of documentation and specs. When compiled and stripped of debug symbols, the resulting binary is around 35MB—for a full browser.
Managing the process
There was one problem early on, in the first couple of days. Claude used sub-agents heavily and parallelized the work. The agents stepped on each other's toes: each worked on a different feature, but they edited the same files and went over the same parts of the codebase. Then it spent a lot of time resolving the conflicts. It burned through tokens incredibly fast, and it wasn't working. It looked like the project would collapse under its own weight.
So I made a project management decision: one thing at a time, one agent at a time. I don't care if it's much slower; I'm not in a rush. Working on one feature (or part of a feature) at a time avoids the conflicts. It implements it, reviews it, integrates it, tests it, and only when it's done moves to the next one.
It still uses sub-agents to keep the context of each part of the task under control, and it uses different models for different work. The main model, used for the most complex tasks, is Opus 5.5. Easier development goes to Sonnet. Elementary tasks, like parsing output or figuring out what to run in a shell, go to Haiku. This also helps with cost and speed.
After that change, the project has been going smoothly.
What about code quality?
I don't know. I never looked at the code, and I never will. I don't read or write Rust, so I couldn't possibly review it.
Looking at it as a black box, I haven't experienced a maintenance problem yet—at 400,000 lines, it still hasn't collapsed under its own weight and shows no signs of hitting a wall, or of spending too much time mucking around in its own code instead of making progress.
What's next
I don't have specific goals for SWB. It's a nice little browser that delights me when I use it, and I use it every day. Claude will keep working on it in my spare tokens.
It's an ongoing experiment to see how much AI can do on its own. So far, I'm really impressed that it can be done at all, and we'll see how it ends up.
One note on the models. I've been using Claude exclusively for this work, but I do believe other frontier models, such as GPT-6.x, would fare similarly. Opus 5.5 and its smaller brethren have performed exceptionally well, but I don't think such a feat is beyond the reach of other models, especially as new and more capable ones are coming online seemingly every week.
For now, I'll continue using Claude and continue adding capabilities to SWB in my spare time.
If you want to check it out, the code is on GitHub at senko/swb, MIT licensed. Point your agent at it and see what it can do.
Human-dictated; structured and edited by Claude.

