Ask HN: Why all the sudden people are writing browsers with AI?
There is something going on with people, like why do you want to write a browser with the help of AI?
57 comments
Because it's an extremely large and complex project that is also very clearly specified, to the point that the three word prompt "build a browser" encapsulates a huge amount of detail.
Similar to "build space invaders", another useful test prompt for seeing how well an LLM can do at a medium complexity task without having to give it a great deal of instruction.
I called building a browser the "hello world" of complex parallel agent coding harnesses the other day: https://simonwillison.net/2026/Jan/23/fastrender/#a-single-e...
Similar to "build space invaders", another useful test prompt for seeing how well an LLM can do at a medium complexity task without having to give it a great deal of instruction.
I called building a browser the "hello world" of complex parallel agent coding harnesses the other day: https://simonwillison.net/2026/Jan/23/fastrender/#a-single-e...
I am not convinced either of these are good test prompts for generic complexity tasks. Many solutions have already been included in the training data!
You can trivially produce a web browser by copying and compiling the code for firefox, no transformer needed.
You can trivially produce a web browser by copying and compiling the code for firefox, no transformer needed.
But that would produce Firefox.
The goal with these tests is to see if the models can make something new, not just copy an existing solution.
That is the goal, at least.
The goal with these tests is to see if the models can make something new, not just copy an existing solution.
That is the goal, at least.
But how do you define, or indeed assess, novelty?
It's not that difficult to take an existing mature codebase and morph it such that it looks quite different but is functionally unchanged.
This is a very different task than building something that's not been built before.
It's not that difficult to take an existing mature codebase and morph it such that it looks quite different but is functionally unchanged.
This is a very different task than building something that's not been built before.
Obviously Microsoft felt bad when they had to kill the old Edge browser that was based on their own HTML rendering engine. Must feel like a second-rate tech company when you can't write some code to render HTML with sufficient quality.
Now they can get back in the game with a 3-word prompt!
And then every time there's some change to web standards, it's just one more prompt where you say "Hey Copilot, take a look at this page that describes the change, and update our browser code to add this!"
/s
Now they can get back in the game with a 3-word prompt!
And then every time there's some change to web standards, it's just one more prompt where you say "Hey Copilot, take a look at this page that describes the change, and update our browser code to add this!"
/s
I think a lot of people here are kind of concerned that there's only three browsers now, and overwhelmingly really only two: Google Chrome and Safari for iOS. Internet Explorer is just Chrome now and while I use Firefox it is still pretty tiny in usage stats. I do not consider things like Epiphany/Gnome Web as serious contenders, and even if I did that would still be only one more niche browser. Things without JS support like NetSurf, in my opinion, don't count at all.
It's a little scary when a single megacorp has so much power over something ostensibly open like the internet, but it also has historically taken an incredible amount of resources in order to make a browser making it hard for new players to break in. A modern web browser is arguably more complicated than an operating system...hell, it arguably is an operating system. It touches a ton of aspects of computer science, and requires lots of dedicated workers to keep up with web standards.
Because it has been such an intractable problem for so long, it's an extremely tempting target when the circumstances have changed. Anyone here can basically have a metaphorical intern working as many hours as they want for ~$20-$100/month. A problem that would be impossible for a single person five years ago suddenly seems "almost possible" when you can work at a higher level and have the pesky "code" details taken care of for you.
It's a little scary when a single megacorp has so much power over something ostensibly open like the internet, but it also has historically taken an incredible amount of resources in order to make a browser making it hard for new players to break in. A modern web browser is arguably more complicated than an operating system...hell, it arguably is an operating system. It touches a ton of aspects of computer science, and requires lots of dedicated workers to keep up with web standards.
Because it has been such an intractable problem for so long, it's an extremely tempting target when the circumstances have changed. Anyone here can basically have a metaphorical intern working as many hours as they want for ~$20-$100/month. A problem that would be impossible for a single person five years ago suddenly seems "almost possible" when you can work at a higher level and have the pesky "code" details taken care of for you.
> A problem that would be impossible for a single person five years ago suddenly seems "almost possible" when you can work at a higher level and have the pesky "code" details taken care of for you.
It was already possible - The Ladybird browser started with one person and then a team of experts in maintaining browsers joined in. It makes a lot of sense for them to try to build one from scratch; with / without AI.
The problem which applies to all non mainstream browsers: Is anyone going to use your browser over the established ones because of some technical detail such as, who wrote it or what it is written in?
99.999% of people only care about whether if it just works and disappears away from the user whilst they're using it as a daily driver for browsing or doing work.
How is AI surely going to make this better the other than inexperienced folks throwing PRs they have not read? In fact, it helps the experts rather than the vibe coders.
It was already possible - The Ladybird browser started with one person and then a team of experts in maintaining browsers joined in. It makes a lot of sense for them to try to build one from scratch; with / without AI.
The problem which applies to all non mainstream browsers: Is anyone going to use your browser over the established ones because of some technical detail such as, who wrote it or what it is written in?
99.999% of people only care about whether if it just works and disappears away from the user whilst they're using it as a daily driver for browsing or doing work.
How is AI surely going to make this better the other than inexperienced folks throwing PRs they have not read? In fact, it helps the experts rather than the vibe coders.
> It was already possible - The Ladybird browser started with one person and then a team of experts in maintaining browsers joined in. It makes a lot of sense for them to try to build one from scratch; with / without AI.
Yes, by a person with prior browser-making experience and who was also building his own operating system. It's not that weird that people who know how to make browsers started making browsers.
Most people don't know how to make browsers, but doing so is still tempting. LLMs lower the barrier to entry tremendously.
To be clear, I'm not giving a value judgement to this; I'm not saying this is "good", just the why of it.
Yes, by a person with prior browser-making experience and who was also building his own operating system. It's not that weird that people who know how to make browsers started making browsers.
Most people don't know how to make browsers, but doing so is still tempting. LLMs lower the barrier to entry tremendously.
To be clear, I'm not giving a value judgement to this; I'm not saying this is "good", just the why of it.
How does your custom AI-built browser challenge the current browser triopoly?
The LLMs are trained on the code of existing browsers. This is essentially a massive process of turning code you don't understand into code you don't understand.
The code details are pretty much all of the details, other than the protocols and standards.
If you understood the codebase of existing browsers (or at least could be confident in making arbitrary changes to existing browsers, perhaps with AI assistance?) then the triopoly wouldn't be threatening because you could just patch out manifestv3 whenever you want.
There is also the problem of people not testing their websites to be compatible with your custom browser. But I would say this is a problem on the protocol level.
The LLMs are trained on the code of existing browsers. This is essentially a massive process of turning code you don't understand into code you don't understand.
The code details are pretty much all of the details, other than the protocols and standards.
If you understood the codebase of existing browsers (or at least could be confident in making arbitrary changes to existing browsers, perhaps with AI assistance?) then the triopoly wouldn't be threatening because you could just patch out manifestv3 whenever you want.
There is also the problem of people not testing their websites to be compatible with your custom browser. But I would say this is a problem on the protocol level.
someone might build enough hype around it to challenge the oligopoly.
As for training on existing browsers: they are trained on the whole corpus of the human thought process and can take many insights from other fields into the browser, they can write a browser in a completely new language without just transpiring but building it from first principles or as karparthy calls it spec based programming.
As for training on existing browsers: they are trained on the whole corpus of the human thought process and can take many insights from other fields into the browser, they can write a browser in a completely new language without just transpiring but building it from first principles or as karparthy calls it spec based programming.
I didn't say that they would be successful, just why it's tempting.
Prior to LLMs, creating a browser from scratch seemed like an insurmountable task for a single person. LLMs lower the barrier to entry, and it's a space that is tempting because it would be cool to be the one to create a new browser that people use.
Prior to LLMs, creating a browser from scratch seemed like an insurmountable task for a single person. LLMs lower the barrier to entry, and it's a space that is tempting because it would be cool to be the one to create a new browser that people use.
Blame Simon Willison ;)
“A common complaint today from AI coding skeptics is that LLMs are fine for toy projects but can’t be used for anything large and serious.
I think within 3 years that will be comprehensively proven incorrect, to the point that it won’t even be controversial anymore.
I picked a web browser here because so much of the work building a browser involves writing code that has to conform to an enormous and daunting selection of both formal tests and informal websites-in-the-wild.
Coding agents are really good at tasks where you can define a concrete goal and then set them to work iterating in that direction.
A web browser is the most ambitious project I can think of that leans into those capabilities.”
https://simonwillison.net/2026/Jan/8/llm-predictions-for-202...
“The browser and this project were co-developed and very symbiotic, only because the browser was a very useful objective for us to measure and iterate the progress of the harness. The goal was to iterate on and research the multi-agent harness—the browser was just the research example or objective.”
https://simonwillison.net/2026/Jan/23/fastrender/
“A common complaint today from AI coding skeptics is that LLMs are fine for toy projects but can’t be used for anything large and serious.
I think within 3 years that will be comprehensively proven incorrect, to the point that it won’t even be controversial anymore.
I picked a web browser here because so much of the work building a browser involves writing code that has to conform to an enormous and daunting selection of both formal tests and informal websites-in-the-wild.
Coding agents are really good at tasks where you can define a concrete goal and then set them to work iterating in that direction.
A web browser is the most ambitious project I can think of that leans into those capabilities.”
https://simonwillison.net/2026/Jan/8/llm-predictions-for-202...
“The browser and this project were co-developed and very symbiotic, only because the browser was a very useful objective for us to measure and iterate the progress of the harness. The goal was to iterate on and research the multi-agent harness—the browser was just the research example or objective.”
https://simonwillison.net/2026/Jan/23/fastrender/
The Cursor FastRender project started in December, so it wasn't influenced by my prediction in January.
> Coding agents are really good at tasks where you can define a concrete goal and then set them to work iterating in that direction.
Wholly based on other people's work. Which is OK.
Wholly based on other people's work. Which is OK.
> Coding agents are really good at tasks where you can define a concrete goal and then set them to work iterating in that direction.
Specifically ones that are in the training data.
> A web browser is the most ambitious project I can think of that leans into those capabilities.”
I assume Linux and gcc are in the training data, so additional options may be OSes and compilers..
Specifically ones that are in the training data.
> A web browser is the most ambitious project I can think of that leans into those capabilities.”
I assume Linux and gcc are in the training data, so additional options may be OSes and compilers..
I'd really like a pure RSS browser. Just nice articles in a standard format, no ads, no clickbait.
RSS readers are cool but the discovery is still tedious - looking for feeds isn't much fun.
I did just discover feedle though, which looks like halfway toward what I want! https://feedle.world/
I want feedle in a nice native app.
RSS readers are cool but the discovery is still tedious - looking for feeds isn't much fun.
I did just discover feedle though, which looks like halfway toward what I want! https://feedle.world/
I want feedle in a nice native app.
Feedle looks useful, I've already found one blog I wasn't aware of. Thanks for recommending it!
I wonder if Feedle will provide an API (even a paid API)? Could be nice to plug this into a metasearch engine as an additional data source. And I guess that might be necessary to add Feedle search to an RSS reader or native app as well.
I wonder if Feedle will provide an API (even a paid API)? Could be nice to plug this into a metasearch engine as an additional data source. And I guess that might be necessary to add Feedle search to an RSS reader or native app as well.
This made me think of this popular RSS reader that Google had that they shutdown. I bet you could just vibe the same RSS reader back into existence.
If you use the regression-suite I already setup (https://github.com/embedding-shapes/one-agent-one-browser/bl...) for my tiny toy browser experiment, I bet you could build it by just adding more and more "HTML > .png" examples and prompt something like "Make regression suite pass by fixing the implementation, refactor as needed", and end up with something usable.
I guess Google Reader had done it's job, take over the RSS industry then kill it:
https://www.zdnet.com/article/embrace-extend-extinguish-how-...
https://www.zdnet.com/article/embrace-extend-extinguish-how-...
RSS could still be less token heavy alternative for agents as the alternative to parsing full html websites.
IMO it’s a pretty verifiably correct and complex piece of software. There are all sorts of test suites but no greater one than comparing a page rendered to how it renders in chrome.
Also, and maybe more importantly, a browser is the kind of the perfect entry point for a lot of businesses.
If you’re for example hoping to build an agent that people rely on to manage their calendars, emails, book them vacations, etc.. a browser is probably the perfect form factor for that.
Or if you’re a AI lab and want to tap into training data behind logged in websites - a browser everyone uses is the ultimately what you need.
If you can build and maintain a browser from scratch with just agents then there’s no need to pay millions of dollars to hire away chromium engineers from Google.
The list goes on!
Also, and maybe more importantly, a browser is the kind of the perfect entry point for a lot of businesses.
If you’re for example hoping to build an agent that people rely on to manage their calendars, emails, book them vacations, etc.. a browser is probably the perfect form factor for that.
Or if you’re a AI lab and want to tap into training data behind logged in websites - a browser everyone uses is the ultimately what you need.
If you can build and maintain a browser from scratch with just agents then there’s no need to pay millions of dollars to hire away chromium engineers from Google.
The list goes on!
Because someone tried and it vaguely worked.
And browsers are one of those products where if it was simple to alter everyone would like different setups and features. Like the Notes app of before.
Naturally they are all incomplete implementations because the AI agent is mostly reusing open source components and for the stuff it decides to write itself, doesn't have the training data to implement a full rendering engine in a one-shot.
And browsers are one of those products where if it was simple to alter everyone would like different setups and features. Like the Notes app of before.
Naturally they are all incomplete implementations because the AI agent is mostly reusing open source components and for the stuff it decides to write itself, doesn't have the training data to implement a full rendering engine in a one-shot.
It’s a demonstrably difficult problem that, aside from lady bird, has not been easy for independent devs to accomplish.
It would be very useful if AI could do it (though I kind of doubt something high-performance can be created this way). It's economically unfeasible for humans to develop a browser engine from scratch anymore. Microsoft and Opera gave up. Apple probably will too someday.
It's the most complex piece of software on your computer (it's basically an entire sandboxed operating system, at this point), the standards it has to adhere to are expanding every day, its performance optimization is critical yet adversarial (i.e. website owners have no incentive to make their sites efficient - the browser will be blamed for slowness, not them), and it costs the user nothing. No company can afford to maintain that, unless it's serving some broader strategy that's earning billions.
It's the most complex piece of software on your computer (it's basically an entire sandboxed operating system, at this point), the standards it has to adhere to are expanding every day, its performance optimization is critical yet adversarial (i.e. website owners have no incentive to make their sites efficient - the browser will be blamed for slowness, not them), and it costs the user nothing. No company can afford to maintain that, unless it's serving some broader strategy that's earning billions.
> There is something going on with people, like why do you want to write a browser with the help of AI?
Is there? Who else? I thought I was the only one, besides Cursor's half-hearted attempt :P Where are the rest of the AI-made browsers? Now I want to see them.
In my case, I saw Cursor's blog post bragging about using hundreds of agents producing millions of lines of code, and the results were underwhelming (not to mention broken until a human stepped in). Initially I tried to dig into their codebase to understand how it got to where it was, but gave up.
Instead, I changed my approach, and decided to build a browser using only OS libraries in order to show that millions of LOC for what they got, is very underwhelming.
Is there? Who else? I thought I was the only one, besides Cursor's half-hearted attempt :P Where are the rest of the AI-made browsers? Now I want to see them.
In my case, I saw Cursor's blog post bragging about using hundreds of agents producing millions of lines of code, and the results were underwhelming (not to mention broken until a human stepped in). Initially I tried to dig into their codebase to understand how it got to where it was, but gave up.
Instead, I changed my approach, and decided to build a browser using only OS libraries in order to show that millions of LOC for what they got, is very underwhelming.
Several years ago, I did write that every programmer should attempt to write a browser: https://austinhenley.com/blog/morechallengingprojects.html
:)
:)
Because they can. It's fun.
AI makes it possible to do things you'd never have been able to do before, perhaps due to skill level or perhaps due to the time investment required.
It is a lot of fun to make software that you'd only been able to dream about making before AI.
AI makes it possible to do things you'd never have been able to do before, perhaps due to skill level or perhaps due to the time investment required.
It is a lot of fun to make software that you'd only been able to dream about making before AI.
It's a difficult, large problem - but one with very extensive tests available and that LLMs have a good understanding of. You can also look up the earlier automated ports of the JustHTML parser. A rendering engine is the next (admittedly large) step.
I say this as someone who also took on this task, about a week before I saw Cursor's attempt.
I say this as someone who also took on this task, about a week before I saw Cursor's attempt.
> I say this as someone who also took on this task, about a week before I saw Cursor's attempt.
What was the results? As far as I can tell, less agents work better, paired together with someone who knows solid engineering.
What was the results? As far as I can tell, less agents work better, paired together with someone who knows solid engineering.
I didn't use my skills really to guide it, beyond knowing what test suite exists, and knowing it could reliably port a good HTML/CSS parser (to golang).
I burned through a week of codex max subscription quota with it making slow progress. Slower than I wanted, but consistent slow progress. Not long after though it hit a brick wall and the second week+ of quota did not really make much progress. It can churn for hours and get one test working, or churn for hours and fail.
I might give it a go with more guidance, because I actually really would like an html/css renderer with some specific properties about how I interact with it from code.
I burned through a week of codex max subscription quota with it making slow progress. Slower than I wanted, but consistent slow progress. Not long after though it hit a brick wall and the second week+ of quota did not really make much progress. It can churn for hours and get one test working, or churn for hours and fail.
I might give it a go with more guidance, because I actually really would like an html/css renderer with some specific properties about how I interact with it from code.
The same reason why all of a sudden people are rolling their own sandboxes using AI (without even looking at the code!):
Hype (for VCs), not invented here syndrome (NIH), performative reasons for the impression of progress or just because they can.
Because the traditional web is dying due to AI. Search is now turning into read the AI summary. So, what does the future look like? I mean, how do we bridge the gap between where we are now and that future. I don't like it...
Because they want to sell AI and browsers are stuff users spend a lot of time in.
I don't really see the added value there though. I do see it for search and deep research but much less for regular browsing.
I don't really see the added value there though. I do see it for search and deep research but much less for regular browsing.
There's a lot of "if AI is so good then why can't it do X", and depending on who you ask "writing a browser" is somewhere on the frontier of X values.
this doesn't really matter, but, normal english would be either "Why are people all (of) the sudden writing browsers with AI?" or (slightly less normal) "Why all (of) the sudden are people writing browsers with AI?", with the (of) being more 'correct' but often omitted. Regardless, it should be "are people" instead of "people are" in a question.
(In edited writing, “all of a sudden” is far more common than “all of the sudden”. https://www.merriam-webster.com/grammar/usage-of-all-of-a-su...)
oops you're right. some grammar policer i am
(I didn't know that, actually)
(I didn't know that, actually)
It is a stepping stone to writing an entire feature rich operating system thereafter, if only a virtual one.
I have just barely noticed this but I think this shows a really interesting trend that is long overdue. Recently many things were hard and now they are 'easy' (ish) which means we are likely to see an explosion of choices. This is good from an ecosystem point of view. Diversity will, initially, cause a lot of issues but in the long term it will lead to many new things.
Why did Alex Honnold climb Taipei 101 when he could just take the elevator?
I know the analogy is not perfect but it's the kind of project that wasn't feasible for a single dev before LLMs so now it just seems like a fun thing to try for some people.
I know the analogy is not perfect but it's the kind of project that wasn't feasible for a single dev before LLMs so now it just seems like a fun thing to try for some people.
Something about a solution in search of a problem methinks.
Because the most used, high value target for exploitation application, is a perfect candidate for autocoded slop wrangled by incompetent developers who don't understand the code enough to write it from scratch.
Who? Where? I’m blissfully unplugged from this bubble (despite lurking on HN). Show me a usable browser that was “written with AI”. Such claims are likely PR.
It remains an open challenge. I've seen three credible initial attempts so far, though none of them have got further than being able to render static HTML and CSS:
- https://github.com/hiwavebrowser/hiwave
- https://github.com/wilsonzlin/fastrender
- https://github.com/embedding-shapes/one-agent-one-browser
I've started tracking them on this tag on my blog: https://simonwillison.net/tags/browser-challenge/
- https://github.com/hiwavebrowser/hiwave
- https://github.com/wilsonzlin/fastrender
- https://github.com/embedding-shapes/one-agent-one-browser
I've started tracking them on this tag on my blog: https://simonwillison.net/tags/browser-challenge/
> though none of them have got further than being able to render static HTML and CSS
Ehh, really pushing my buttons to continue now huh? I have other things to do! twitching
Guess I'll start sketching out some lame JS engine from scratch too...
Ehh, really pushing my buttons to continue now huh? I have other things to do! twitching
Guess I'll start sketching out some lame JS engine from scratch too...
its just a meme
I've noticed a lot of desperation to validate the usefulness of AI. I guess partly from those who are trying to make money from it and partly from others who need the cognitive shortcut of offloading work and creativity to it.
> I've noticed a lot of desperation to validate the usefulness of AI. I guess partly from those who are trying to make money from it and partly from others who need the cognitive shortcut of offloading work and creativity to it.
I've noticed a lot of desperation to deny the usefulness of AI. I guess partly from those who feel threatened by it and partly from others who aren't curious enough to figure out how to use it effectively.
(Sorry, couldn't resist.)
I've noticed a lot of desperation to deny the usefulness of AI. I guess partly from those who feel threatened by it and partly from others who aren't curious enough to figure out how to use it effectively.
(Sorry, couldn't resist.)