Quoting Andreas Kling

Simon Willison's Blog News
ladybird browser open-source development-policy ai-contributions pull-requests

Summary

Ladybird browser will no longer accept public pull requests due to the ease of generating code with AI, requiring that contributors take responsibility for changes.

No content available
Original Article
View Cached Full Text

Cached at: 06/05/26, 02:06 PM

# A quote from Andreas Kling Source: [https://simonwillison.net/2026/Jun/5/andreas-kling/](https://simonwillison.net/2026/Jun/5/andreas-kling/) 5th June 2026 > We will no longer accept public pull requests\. \[\.\.\.\] A substantial patch used to imply substantial effort, and that effort was a reasonable proxy for good faith\. That assumption no longer holds\. \[\.\.\.\] Whether code was typed by hand is beside the point\. What matters is who is responsible for it once it enters the browser\. Ladybird is becoming a browser for real users\. The people introducing changes to it must be the people who decide those changes belong in the project, and who will answer for the consequences\. —[Andreas Kling](https://ladybird.org/posts/changing-how-we-develop-ladybird/),Changing How We Develop Ladybird

Similar Articles

Changing How We Develop Ladybird

Lobsters Hottest

Ladybird browser is closing public pull requests and restricting code changes to project maintainers only, citing that AI tools have made it harder to assess contributor trustworthiness and that the project needs tighter security as it approaches an alpha release.

I don't want your PRs anymore

Lobsters Hottest

An open-source maintainer explains why they now prefer LLM-generated code over community PRs, arguing that AI assistance reduces risk and friction while shifting the value of contributions toward feedback, bug reports, and design discussions.

Ladybird browser update (May 2026)

Lobsters Hottest

The May 2026 update for Ladybird browser brings major improvements in real-world site compatibility (e.g., passes Cloudflare Turnstile, enables MSE), responsiveness (async scrolling, JS bytecode caching, WASM JIT with Cranelift, incremental sweeping), and infrastructure (Rust HTML parser, ad-blocking via adblock-rust, CSS container queries).

The Zig project's rationale for their firm anti-AI contribution policy

Simon Willison's Blog

The article discusses the Zig project's strict ban on AI-generated contributions, citing Loris Cro's 'contributor poker' rationale that prioritizes nurturing human contributors over processing code volume. It highlights how this policy affects the Bun runtime, which uses an AI-assisted fork of Zig.