Godot’s AI Ban: An Open Source Project Choosing People Over Bots
Godot’s updated open source AI policy is a set of contribution rules that forbid autonomous AI agents and substantial AI-generated code, aiming to protect human-driven mentorship, reduce review backlogs, and maintain coherent code contribution quality across its game engine repositories. This is not a small tweak. Godot Engine, a widely used open-source alternative to commercial game engines, is rewriting its contribution policy to bar most AI-generated code from its repositories after months of internal debate at the Godot Foundation. The Foundation has already been auto-banning “autonomous AI agent use or vibe coding” from its GitHub, and now plans to formally require that “all code be human authored,” limiting AI assistance to minor tasks like completion or regex. Announced on June 30, 2026, the new rules also tighten expectations for new contributors and explicitly frame AI-generated code as a threat to sustainability, not an accelerator.
When ‘AI Slop’ Meets Limited Reviewers: The Burnout Math
Godot’s maintainers are not fighting AI because the code is always wrong; they are fighting the scale and cost of reviewing it. The Foundation admits that a large part of its backlog comes from having “a small number of qualified reviewers” and demanding pull request reviews they “can’t keep up with,” a situation that has grown to the point where the PR count has “become a meme in the community.” AI changes the equation in one direction: it makes submitting code easier, so more pull requests appear, including “low-effort slop” and nonsensical “AI slop code.” Review workload, however, stays the same or worsens. According to the Godot Foundation, “the amount of effort required to make a PR has gone down … while the amount of work to review PRs and the amount of people available to review has stayed the same.” That mismatch is classic maintainer burnout: rising volume, fixed capacity, and no way to say “no” without rewriting the rules.
Mentorship, Not Throughput: Why AI Contributions Feel Demoralizing
What makes AI-generated code uniquely painful for Godot’s maintainers is not only its quality but its absence of a learner on the other end. The Foundation is blunt: “AI contributions have the added pain of being demoralizing,” because feedback on those pull requests does not educate a person, and “LLMs can’t learn from specific feedback and thus can’t benefit from maintainers providing feedback.” Reviewers already find PRs tedious, but historically they have been rewarded by seeing contributors grow into future maintainers and reviewers. In their words, if feedback “is just being absorbed by a machine and not going towards mentoring a potential future maintainer, it becomes much harder to justify spending your free time on PR review.” The Foundation also warns that it “can’t trust heavy AI users to understand their own code well enough” to act on review comments, further eroding the mentoring pipeline. This is a direct challenge to the assumption that open source exists to consume free labor; here, contribution is supposed to be an apprenticeship, not just throughput.
New Rules: Human-Authored Features, Guardrails for New Contributors
To protect that mentorship model, Godot is redesigning its contribution flow around humans, not AI. The amended open source AI policy will include an explicit ban: “No autonomous AI agent use or vibe coding,” a rule that already triggers auto-bans from its GitHub repository. It will also insist on “No use of AI to generate substantial pieces of code,” requiring all code to be human authored and limiting AI assistance to small tasks like code completion, regex, or find-and-replace. AI-generated text in human-to-human communication is also off-limits, aside from machine translation of human-written text. On top of this, Godot now treats anyone with three or fewer merged pull requests as a new contributor, and they must receive explicit approval before submitting new features or major refactors, steering them toward bug fixes and documentation instead. These rules target both AI-generated code risks and feature creep, while trying to grow a maintainer pipeline instead of a queue of unread PRs.
The Bigger Picture: AI Acceleration vs. Sustainable Open Source
Godot’s stance fits a broader pattern: open source communities are starting to treat AI not only as a tool but as a threat to their social contracts. Other projects, like the systems programming language Zig, have adopted similarly strict open source AI policies, arguing that maintainers “bet on the contributor, not on the contents of their first PR” and that AI-generated pull requests break that calculation entirely. Across the industry, AI promises acceleration, but in open source the cost is paid in mentorship and maintainer burnout. The worry mirrors corporate fears about entry-level work: AI may do the tasks once assigned to juniors, but then there is nobody to train into senior roles. In open source, junior contributors may still show up—yet if AI writes their code, feedback “has nowhere to land,” and the informal pipeline from first-time contributor to future maintainer stops functioning as if they had never appeared. Godot hints it will keep a “conservative approach” but re-evaluate its AI rules as tools evolve. For now, it has chosen sustainability over speed, staking its future on human contributors who can learn, grow, and one day share the burden of review.
