One of the things I find really helpful about servo (as a casual user) is the breadth of pre-built releases they have. It makes it much more feasible to actually use on a day-to-day basis, especially on android
It was working a second ago (I made the parent comment from servo) but it looks like you get logged out pretty quickly. YMMV, plus probably best not to log into anything too important yet
> Contributions must not include content generated by large language models or other probabilistic tools, including but not limited to Copilot or ChatGPT. This policy covers code, documentation, pull requests, issues, comments, and any other contributions to the Servo project.
> For now, we’re taking a cautious approach to these tools due to their effects — both unknown and observed — on project health and maintenance burden. This field is evolving quickly, so we are open to revising this policy at a later date, given proposals for particular tools that mitigate these effects.
The references to ChatGPT and Copilot suggest it was authored before the Codex and Claude Code revolution. I wonder if they'll revise it at some point soon.
I think the sweet spot is not allowing vibe-coded contributions past a certain line count. At least, that's my policy. If you use an LLM to track down some bug that's a few lines to fix; that's fine. But if it's a new feature that needs 100s of lines; just make a feature request and if I agree, I can spin up my own clanker.
That was my thought as well. You'd imagine a known quantity like a browser should be easy to make now. I know it sounds ridiculous to anyone who hasn't tried the new models, but idk what to tell you. Photoshop used to be impossible to clone, too. I asked Opus 5.5 to add SSGI to an open source game and it did it in an afternoon. I don't know anything about graphics programming. This is nuts.
Photoshop was never impossible to clone, and people have written browser engines before. The issue was never implementation complexity, but rather the things that are actually hard: going past the 99% of required features, hunting down corner cases, and at the same time ensuring high test coverage and maintainability.
Ladybird seems to be embracing vibe coding, so I think there's a great opportunity to compare them. After a couple of months of vibe coding what do you people here think about Ladybird's progress?
>> With the advances in AI, I'd expect the Servo project to go a lot faster ...
>> Do they allow vibe-coded contributions?
With an official automated test suite that they aim to pass, someone could probably set Claude loose on closing out those bugs and feature gaps. Assuming AI can figure out why tests fail (it probably can) I'd give it about a day to finish. Actually maybe a week since it'd be compiling RUST. Would the resulting code be of the same quality? Probably not. Would it be good? Maybe.
IME, agents are generally capable of passing the tests autonomously. But not with code you'd actually ever want to use. Both because of the quality, and because it will have awful performance/memory/security issues.
The progress on Servo is impressive. UI polish is required in order to be more usable. Things like keyboard shortcuts to focus the address bar are required to make it feasible for more daily driving use
My understanding is that the main focus is on the engine and building a good embedding API so that folks can build browsers (and apps and web drivers etc...) with it.
That is my understanding too. In contrast Ladybird has really improved in the UI area and the recent addition of session restore, content blocking and performance makes it a very capable daily driver browser
> For now, we’re taking a cautious approach to these tools due to their effects — both unknown and observed — on project health and maintenance burden. This field is evolving quickly, so we are open to revising this policy at a later date, given proposals for particular tools that mitigate these effects.
seems entirely reasonable reason and approach, and I see no reason to force everyone approach LLM in the same way
my read is that with the right guidance, implementing the vast amount of the CSS spec for example, could be done easily with some AI assistance, the spec is incredibly well defined. just comparing the layouting and styling in blitz[0] (which does use agents), servo is lacking quite a bit, and the implementation of various features don't follow the spec exactly.
that being said, i entirely respect their decision of course, perhaps they will revisit at a later point in time!
My experience is that it varies greatly by feature.
Something like border styles, the agent was able to do pretty effectively. Although it still took a few hours iterating on it to get the performance characteristics and edge cases right.
More complex features like hoisting position absolute nodes and other layout features still take days to weeks of iterating to get something usable that isn't so fragile it'll blow up the next time you touch something.
Yes, this was how I did it in Azul[1], which is „reverse engineered from the W3C spec“. But it still took a lot of „agentic debugging“ to get the same visual layout as Chrome[2]. It wasn‘t „easily“ done however and it‘s not yet stable.
It’s kind of a wink wink situation. Language like this simply encourages developers to vet code written by AI thoroughly to avoid being caught with obvious slop.
But as maintainers we (I don’t work on servo, but other projects) know that obviously people use AI anyway.
The AI policy for Servo, which prohibits AI contributed code (but allows you to use AI to inspect and learn about the codebase), was written in mid-2024, which seems like an eternity ago.
But even in June 2026 they reiterated this ban and added CI checks to automatically reject AI-coauthored patches [1].
> For developers of Servo itself, please note that per project policy, you must not use the output of large language models or other generative AI tools in your contributions. To help us enforce that, we now have CI checks that reject AI agents as coauthors (@SimonSapin, @delan, #44723).
It's heartening to see a large group of people working (mostly) for free on a passion project. Makes me optimistic about the resilience of intrinsic human drive.
As an on-again off-again project, I've been building an incremental game that is pretty much just hundreds of progress bars - a little bit out of the norm for the browser.
Firefox everything renders smoothly and gently.
Chrome chugs, skips paints, delays animation frames, skips some events, and batches others.
Game uses a few features that aren't in Servo yet... But maybe I can tweak it...
Servo is really great: Rust seems like a no brainer choice for a modern web engine, and its clean, performance-focused design from the ground up is wonderful.
But it seems really hard for it to get anywhere just based on occasional contributions from volunteers. I was actually quite surprised that basic functionality like <progress> and the :checked attribute were not even supported prior to this release.
Servo got 527 commits, while Chromium has over 20,000 commits.
> Can I submit a PR that includes code generated by AI tools?
> No. This includes (but is not limited to) all generative AI tools like Claude, Codex, ChatGPT, Cursor, Gemini, and Windsurf.
For something like a browser, this de facto limits the set of people who can contribute to something that touches the layout engine (e.g. the ineffable but brilliant https://github.com/servo/servo/blob/main/components/layout/f...) to just those already familiar with the code.
A much better middle ground IMO would be to quarantine first-time committers behind an AI-generated-PRs-will-not-be-reviewed policy, but to allow those who understand and respect the cycle enough to get PRs accepted, to begin using AI to give the team leverage. Without some kind of policy like that, Servo's sadly going to fall behind literally any other open-source project that people could dedicate their time towards.
> > No. This includes (but is not limited to) all generative AI tools like Claude, Codex, ChatGPT, Cursor, Gemini, and Windsurf
Based on the tool listed here, you can probably know when this policy was first written. For instance, Windsurf is long gone and Cursor is not tier 1 anymore.
Crazy to think how much the space of AI coding agent has evolved in less than 2 years.
Yeah, it's a fun time capsule. The policy was written in July 2024 [1]. There's a contentious discussion in 2025 [2] where they discussed it and reaffirmed the ban. Then in June 2026 they reiterated the ban and added CI checks to reject AI coauthors [3]
They were right at each time for different reasons
In 2024 the tools were severely lacking. Today they work better (if subpar and verbose), but put an undue burden on reviewers (which are already in short supply)
You can see how Ladybird is "progressing" right now because of AI. I think it's a shame because now AI would just be using parts from chromium or Firefox, and they're going to encouter eventually an unmaintainable codebase. How a new browser engine helps here then?
It is not like they are fully vibe coding the browser. And Ladybird was not built with a prompt. They already had a more or less fully functioning browser before they introduced the use of AI.
The design of Ladybird follows the web standards closely as well. It is going to be quite different from older engines. And the code is quite organized, if your concern is AI slop from layers and layers of AI added features. I do not think that is how they are using it at all.
My biggest gripe with Ladybird is that they adopted some pretty large components written by Google. You cannot really use Skia and say that you do not rely on Google as an example.
Not relying on Google was their big selling point, since every other browser is Google-dependent.
Language choice has next to nothing to do with browser performance. Servo's "performance-focused" design currently suffers from a 10x gap between it and Chrome on the same platform.
I think the benchmark is for layout performance not JavaScript execution, but v8 is fast because it emits assembly more so than because of the language it is implemented in. That said, I would be very surprised if there is not hand tuned assembly routines for performance critical routines.
My point was that while you can implement any performant program (be it V8 or Spidermonkey, Blink or Servo) in any language, the effort required to reach a certain performance level differs between the languages.
>v8 is fast because it emits assembly
It emits machine code afaik. And secondly, do you _really_ want to implement the intermediate layers of a JIT in assembly?
> Rust seems like a no brainer choice for a modern web engine
Well, I mean Servo was the original catalyst and production use-case for Rust back in 2012. Both are products of the work of various folks at Mozilla around the time.
> Rust seems like a no brainer choice for a modern web engine,
Why? Beacuse of memory safety?
It's a shame that there aren't other memory safe low-level options that don't come with the rest of the baggage of rust, or try out different paradigms, for example: not defaulting to malloc (and having other allocator options that aren't painful), not using trait-based shared behavior, not using macros, no turbofish, object orientation (for those who partake), etc.
Weryj | a day ago
caminanteblanco | a day ago
npodbielski | a day ago
npodbielski | a day ago
caminanteblanco | a day ago
npodbielski | 20 hours ago
amelius | 23 hours ago
Do they allow vibe-coded contributions?
simonw | 23 hours ago
> Contributions must not include content generated by large language models or other probabilistic tools, including but not limited to Copilot or ChatGPT. This policy covers code, documentation, pull requests, issues, comments, and any other contributions to the Servo project.
> For now, we’re taking a cautious approach to these tools due to their effects — both unknown and observed — on project health and maintenance burden. This field is evolving quickly, so we are open to revising this policy at a later date, given proposals for particular tools that mitigate these effects.
The references to ChatGPT and Copilot suggest it was authored before the Codex and Claude Code revolution. I wonder if they'll revise it at some point soon.
Update: looks like that language was originally added in July 2024: https://github.com/servo/book/commit/5afb80d5b08b259ca359cfe...
I found a discussion about changing it in April 2025, but they decided to keep it the same at that point: https://github.com/servo/servo/discussions/36379
tcdent | 23 hours ago
Have been using it as the render backend on an experimental tablet OS and its quite capable once you fix the font rendering.
Would gladly upstream contributions but I dont type anymore.
pkulak | 23 hours ago
tormeh | 22 hours ago
samus | 15 hours ago
matkoniecz | 5 hours ago
feel free to make one
matkoniecz | 22 hours ago
are there serious projects welcoming vibe-coded PRs?
kykat | 22 hours ago
fabrice_d | 13 hours ago
phkahler | 22 hours ago
With an official automated test suite that they aim to pass, someone could probably set Claude loose on closing out those bugs and feature gaps. Assuming AI can figure out why tests fail (it probably can) I'd give it about a day to finish. Actually maybe a week since it'd be compiling RUST. Would the resulting code be of the same quality? Probably not. Would it be good? Maybe.
nicoburns | 21 hours ago
moderation | 23 hours ago
jszymborski | 23 hours ago
moderation | 23 hours ago
nerdypepper | 22 hours ago
nerdypepper | 18 hours ago
domenkozar | 22 hours ago
Feels like a missed opportunity where we could take a giant leap forward.
Y_Y | 22 hours ago
matkoniecz | 22 hours ago
seems entirely reasonable reason and approach, and I see no reason to force everyone approach LLM in the same way
nerdypepper | 22 hours ago
that being said, i entirely respect their decision of course, perhaps they will revisit at a later point in time!
[0]: https://github.com/dioxuslabs/blitz
nicoburns | 21 hours ago
My experience is that it varies greatly by feature.
Something like border styles, the agent was able to do pretty effectively. Although it still took a few hours iterating on it to get the performance characteristics and edge cases right.
More complex features like hoisting position absolute nodes and other layout features still take days to weeks of iterating to get something usable that isn't so fragile it'll blow up the next time you touch something.
fschuett | 18 hours ago
[1] https://azul.rs/ui
[2] https://azul.rs/ui/reftest
8NNTt8z3QvLT8tp | 16 hours ago
ravenstine | 21 hours ago
iknowstuff | 21 hours ago
But as maintainers we (I don’t work on servo, but other projects) know that obviously people use AI anyway.
lanyard-textile | 17 hours ago
samus | 15 hours ago
porphyra | 18 hours ago
But even in June 2026 they reiterated this ban and added CI checks to automatically reject AI-coauthored patches [1].
> For developers of Servo itself, please note that per project policy, you must not use the output of large language models or other generative AI tools in your contributions. To help us enforce that, we now have CI checks that reject AI agents as coauthors (@SimonSapin, @delan, #44723).
[1] https://servo.org/blog/2026/06/30/may-in-servo/
ericyd | 22 hours ago
robin_reala | 21 hours ago
shakna | 20 hours ago
As an on-again off-again project, I've been building an incremental game that is pretty much just hundreds of progress bars - a little bit out of the norm for the browser.
Firefox everything renders smoothly and gently.
Chrome chugs, skips paints, delays animation frames, skips some events, and batches others.
Game uses a few features that aren't in Servo yet... But maybe I can tweak it...
z3ratul163071 | 19 hours ago
how sad.
matkoniecz | 5 hours ago
porphyra | 18 hours ago
But it seems really hard for it to get anywhere just based on occasional contributions from volunteers. I was actually quite surprised that basic functionality like <progress> and the :checked attribute were not even supported prior to this release.
Servo got 527 commits, while Chromium has over 20,000 commits.
btown | 17 hours ago
> Can I submit a PR that includes code generated by AI tools?
> No. This includes (but is not limited to) all generative AI tools like Claude, Codex, ChatGPT, Cursor, Gemini, and Windsurf.
For something like a browser, this de facto limits the set of people who can contribute to something that touches the layout engine (e.g. the ineffable but brilliant https://github.com/servo/servo/blob/main/components/layout/f...) to just those already familiar with the code.
A much better middle ground IMO would be to quarantine first-time committers behind an AI-generated-PRs-will-not-be-reviewed policy, but to allow those who understand and respect the cycle enough to get PRs accepted, to begin using AI to give the team leverage. Without some kind of policy like that, Servo's sadly going to fall behind literally any other open-source project that people could dedicate their time towards.
darkamaul | 17 hours ago
Based on the tool listed here, you can probably know when this policy was first written. For instance, Windsurf is long gone and Cursor is not tier 1 anymore.
Crazy to think how much the space of AI coding agent has evolved in less than 2 years.
porphyra | 17 hours ago
[1] https://github.com/servo/book/commit/5afb80d5b08b259ca359cfe...
[2] https://github.com/servo/servo/discussions/36379
[3] https://servo.org/blog/2026/06/30/may-in-servo/
nextaccountic | 2 hours ago
In 2024 the tools were severely lacking. Today they work better (if subpar and verbose), but put an undue burden on reviewers (which are already in short supply)
fabrice_d | 17 hours ago
alfiedotwtf | 7 hours ago
Now, in 2026 I’m excited by LLMs because the combo of Rust+AI is literally an unstoppable force..
It’s a shame they’re building the Lamborghini of rendering engines but refuse to source parts unless it’s delivered on horseback
gspr | 56 minutes ago
matkoniecz | 34 minutes ago
cowlevel | 10 hours ago
By the time you understand it you shouldn't need AI to write changes. First-time committers are the ones most likely to use AI.
cleansy | 3 hours ago
Hendrikto | 6 hours ago
zarzavat | 4 hours ago
worldsavior | 3 hours ago
LeFantome | 14 minutes ago
The design of Ladybird follows the web standards closely as well. It is going to be quite different from older engines. And the code is quite organized, if your concern is AI slop from layers and layers of AI added features. I do not think that is how they are using it at all.
My biggest gripe with Ladybird is that they adopted some pretty large components written by Google. You cannot really use Skia and say that you do not rely on Google as an example.
Not relying on Google was their big selling point, since every other browser is Google-dependent.
fabrice_d | 17 hours ago
jeffbee | 15 hours ago
fabrice_d | 13 hours ago
jeffbee | 13 hours ago
fabrice_d | 8 hours ago
- Servo b88af263d11e12288ff3eca0848aaa675d6a52f0: 21.4
- Chrome 157: 60.9
- Safari 27.2: 59.2
- Firefox 159: 41.0
So between 2x and 3x slower than the current "big 3".
orangeboats | 9 hours ago
MobiusHorizons | 7 hours ago
orangeboats | 7 hours ago
>v8 is fast because it emits assembly
It emits machine code afaik. And secondly, do you _really_ want to implement the intermediate layers of a JIT in assembly?
nicoburns | an hour ago
eyjafjallajokul | 11 hours ago
Well, I mean Servo was the original catalyst and production use-case for Rust back in 2012. Both are products of the work of various folks at Mozilla around the time.
throwup238 | 11 hours ago
dnautics | an hour ago
Why? Beacuse of memory safety?
It's a shame that there aren't other memory safe low-level options that don't come with the rest of the baggage of rust, or try out different paradigms, for example: not defaulting to malloc (and having other allocator options that aren't painful), not using trait-based shared behavior, not using macros, no turbofish, object orientation (for those who partake), etc.
ivell | 39 minutes ago
https://mojolang.org/
wild_pointer | 17 hours ago
hn_submit | 10 hours ago
walski | 7 hours ago