Godot bans AI-generated code as maintainers fight flood of vibe-coded pull requests

Godot Cracks Down on AI-Generated Contributions

The Godot open-source game engine announced Tuesday it's rewriting its contribution policy to implement an AI ban on nearly all AI-generated contributions, marking a decisive shift in how one of the most popular indie game development platforms handles automated code submissions. The decision comes after maintainers faced an overwhelming flood of AI-generated pull requests that proved both time-consuming and demoralizing to review.

"AI cannot take responsibility, and we can't trust heavy users of AI to understand their code enough to fix it," the Godot maintainers stated in their announcement. The blunt assessment reflects growing frustration with vibe coding practices, where developers rely heavily on AI tools to generate code they don't fully comprehend. Maintainer Rémi Verschelde had previously described AI pull requests as "increasingly draining and demoralizing wastes of time," while one game studio using Godot characterized them as "largely garbage" from users who "don't understand what they're proposing".

New Policy Targets Low-Quality AI-Generated Contributions

The updated guidelines will require new contributors—defined as anyone with three or fewer merged pull requests—to obtain explicit permission from maintainers before submitting new features or significant refactoring to the Godot codebase. This measure aims to exclude vibe coders and AI agents while nurturing contributors who genuinely understand the platform and engage meaningfully with the team. Any autonomous agent-authored contributions will result in an automatic ban from the GitHub repository.

The Godot Foundation emphasized that AI assistance should be "limited to menial things (like code completion, regex, or find and replace)". Contributors who use AI in any capacity must disclose it in pull request discussions. The policy extends beyond AI-authored code to ban AI-generated text in human-to-human communication, which the foundation describes as "a basic principle of respect"2

2

. Machine translations will remain acceptable if the original text was human-authored2

2

.

Maintainer Burnout Drives Policy Change

The decision addresses a critical issue in open-source development: maintainer burnout caused by reviewing code that contributors cannot adequately explain or fix. While AI coding tools like Cursor, Copilot, and Claude Code lower barriers to entry and enable faster prototyping, they create a review bottleneck when submissions arrive from users lacking deep knowledge of Godot's GDScript2

2

. The problem intensifies when AI agents themselves submit code, creating a scenario where maintainers "end up playing telephone with bots that don't understand their feedback"2

2

.

The Godot Foundation noted that reviewing pull requests traditionally offered the satisfaction of mentorship, helping educate new contributors who might become future maintainers. "If your feedback on PRs 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 explained2

2

. This loss of meaningful engagement threatens the sustainability of volunteer-driven software development.

Broader Implications for Open-Source Projects

Godot becomes one of the first major open-source projects to explicitly prohibit substantial use of AI-generated code2

2

, setting a potential precedent for other platforms grappling with similar challenges. The decision has earned goodwill among many indie developers, with some hoping other projects adopt similar policies to protect volunteer maintainers. On Reddit, reviewers have even called for major open-source projects to halt all pull requests from unknown users2

2

.

The move aligns with recent skepticism about vibe coding's role in professional software development. Infosys chairman Nandan Nilekani stated last week that "there is much more to do in the software development life cycle" beyond coding, emphasizing that context remains paramount. Horror stories about deleted databases and wiped drives from AI-generated code continue accumulating, suggesting the technology hasn't yet grasped the contextual understanding essential to quality software development. For the Godot team, protecting reviewer time and maintaining code quality now takes precedence over accessibility gains from AI tools.