Quoting Andreas Kling
Ladybird browser now rejects public pull requests because AI-generated code blurs contributor responsibility, highlighting a trust crisis that open-source faces in the AI era.
- Large AI-generated patches undermine the traditional trust signal that code volume equals honest effort.
- Who takes responsibility for code matters more than how it was written, especially for user-facing projects.
- AI lowers the contribution barrier but raises the maintenance burden through increased review and accountability issues.
- Open-source governance may shift toward closed trust models or new contribution norms.
In June 2026, Ladybird browser founder Andreas Kling announced the project would no longer accept public pull requests. His reasoning struck at the heart of open-source trust: AI-generated code has broken the assumption that a large patch signals honest effort and good faith. With tools like Claude or ChatGPT, a novice can produce a polished, multi-thousand-line contribution without understanding the code or being willing to maintain it. Kling’s conclusion: “Whether code was typed by hand is beside the point. What matters is who is responsible for it once it enters the browser.” For a user-facing product, that responsibility vacuum is unacceptable.
The traditional open-source trust model relied on effort as a proxy for commitment. AI makes effort cheap, and the signal becomes noise. The result is a crisis where maintainers cannot distinguish sincere contributors from drive-by AI-generated patches that look good but hide subtle bugs. Ladybird’s response is drastic but logical: shut the door, rely on a trusted core team.
This trend extends beyond one project. AI is forcing open-source communities to rethink governance. The “radical openness” of the past may give way to more formal structures: contributor agreements with explicit maintenance obligations, mandatory AI disclosure, or technology-enforced code scrutiny. The era of informal trust-based collaboration is ending; more contractual, accountable models are rising.
For developers, the message is clear: know what you submit. AI can help, but you must stand behind your code. Maintainers should craft explicit AI policies and invest in verification. Enterprises depending on open-source must evaluate a project’s “AI resilience.”
Here’s the paradox: AI was supposed to supercharge open-source, but by decoupling contribution from responsibility, it may actually force projects to become more closed. Ladybird’s move is a warning that the real cost of AI-generated code is not technical, but social—the erosion of trust that made open-source work in the first place.
Analysis by BitByAI · Read original