Godot’s AI Code Ban Is About People, Not Just Code
The Godot AI code ban is a new contribution policy for the Godot Engine that prohibits substantial AI-generated code in order to protect maintainers from an overwhelming review backlog while keeping code review focused on mentoring human contributors into future maintainers. Godot Engine, a popular open-source game engine, is rewriting its contribution rules to bar most AI-generated code from its repositories. Announced on June 30, the updated policy bans substantial AI-generated contributions and tightens the rules around who can submit complex changes. This is not a neutral stance on tooling; it is a value judgment about where limited volunteer effort should go. Godot is arguing that open source maintainability depends less on how fast code lands and more on whether review time grows capable humans who will still be around when the AI hype cycle moves on.
From Meme-Level Backlog to “AI Slop”: Why Maintainability Broke
Godot’s maintainers did not ban AI because they fear technology; they banned it because their review pipeline is collapsing under low-effort AI-generated contributions. The Foundation says it has become overwhelmed by the large number of pull requests, to the point where the open PR count has “become a meme in the community.” Many of those pull requests are “AI slop code” and “vibe-coded” submissions—autonomous agents or copy-pasted model output that dump nonsensical or poorly understood changes into the repo. According to the Foundation, “AI contributions have the added pain of being demoralizing,” because feedback on these pull requests neither improves the model nor reliably educates the human who pasted the code. PR review has become the largest bottleneck for the engine, and AI-generated content is turning that bottleneck into unpaid triage work instead of meaningful collaboration.
New Rules: Human-Authored Code and Contributor Vetting
To reclaim maintainability, Godot is tightening both what kind of code gets in and who is allowed to submit features. The new policy states there can be no autonomous AI agent use or vibe coding; this already leads to an auto-ban from the project’s GitHub and will continue to do so. There is also no use of AI to generate substantial pieces of code: all code must be human authored, with AI assistance limited to menial tasks such as code completion, regex, or find-and-replace, and any AI use must be disclosed in the pull request discussion. New contributors—anyone with three or fewer merged pull requests—must now get explicit sign-off before submitting new features or large refactors, and are steered toward bug fixes and documentation first. In short, Godot is raising the bar on AI-generated contributions and on contributor autonomy to keep review capacity aligned with real human growth.
The Real Risk: Losing the Mentoring Culture That Sustains Open Source
The most important part of Godot’s AI stance is not the technical policy but the philosophy behind it: reviewing a pull request is supposed to be an investment in a person. The Foundation writes that review work is tedious but rewarding when it helps educate a new contributor who may become a future maintainer or reviewer. 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.” This reframes open source maintainability as a talent pipeline problem, not merely a code quality problem. The same anxiety shows up elsewhere: other projects like Zig, Ghostty, and curl have restricted AI-generated contributions or parts of their pipelines because review burden and false bug reports turn volunteer work into unpaid support for automated tools rather than human communities. Godot is refusing to let AI hollow out its mentoring culture in the name of short-term throughput.
What Godot’s Conservative AI Stance Signals for Open Source
Godot’s AI code ban sits inside a broader tension: AI tools promise productivity, but open source sustainability depends on maintainers and apprentices, not bots. The Foundation says it needs to reduce the burden on maintainers while keeping a pipeline to mentor new contributors into future maintainers. It calls its approach to AI “conservative” and expects to revisit the policy as tools evolve. Things change every day with respect to the current suite of AI tools, and the project will re-evaluate as they do. Critics will argue this slows innovation or excludes contributors who rely on AI assistance. But the decision is a clear signal: where AI-generated contributions threaten human learning, Godot will side with people. For ordinary users, the practical impact is fewer chaotic features, a healthier code review backlog, and an engine whose quality rests on engaged maintainers instead of opaque models.
