Godot Bans AI-Authored Code Contributions - What It Means for Open Source

The Godot Foundation announced a new contribution policy on June 30, 2026 that explicitly bans autonomous AI agent use and substantial AI-generated code in pull requests. The policy drew immediate attention on Hacker News, sparking debate about how open source projects should adapt to AI-assisted development.

What the Policy Actually Says

The official policy draws clear lines:

Prohibited:

• Autonomous AI agent use or "vibe coding" (results in automatic repository ban)
• AI-generated substantial pieces of code
• AI-generated text in human communication with maintainers

Allowed:

• Menial tasks like code completion, regex, or find-and-replace
• Machine translations (if original content was human-written)

Contributors who use AI assistance must disclose it in the PR discussion. Non-compliance with the agent prohibition triggers automatic GitHub repository suspension.

The Foundation's Reasoning

The policy cites three concerns:

1. AI cannot learn from feedback. When maintainers provide review comments, those insights go toward mentoring future contributors. With AI slop, that feedback disappears into a model that learns nothing and cannot become a maintainer.

2. Machines cannot take responsibility. When code breaks, someone needs to debug it. The Foundation argues that heavy AI users often do not understand their generated code well enough to fix it.

3. Reviewer demoralization. The Foundation stated: "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."

What HN Is Saying

The Hacker News thread generated 160+ comments with a range of reactions.

Support for the policy:

Several commenters endorsed the approach. One noted that AI-authored PRs feel like "a denial-of-service attack on the human mind" - verbose walls of text that require thorough review but provide no mentorship value.

Another pointed out the self-correcting nature of open source: "If someone thinks they're building better open source with their AI, let them fork; their AI can maintain downstream. If it's really better, people will join the fork."

Skepticism about enforcement:

Others questioned the practicality. One commenter asked: "Why base the decision on what tools are used by the author and not on the quality of their past contributions?" The concern is that this polices process rather than outcomes.

Another pointed out a logical gap: "The idea that you can't trust code that was generated by heavy users of AI, because they don't understand it enough to fix it, is false, because they can use AI to fix it." Whether that fixes the mentorship concern is a different question.

Wait-and-see takes:

Multiple commenters expressed support for the experiment even if they disagreed with the policy: "I'm glad we are seeing different projects experimenting with different policies. So after a while we can probably see how things shake out in the end."

One predicted the policy would need revision: "AI tooling and quality are changing quite fast. In a year I'd expect a modification of this as AI agents get better in virtually every possible way."

Project-specific criticism:

A few commenters used the moment to criticize Godot's pace of development, though this is tangential to the AI policy itself.

The Broader Context

Godot is not the first project to wrestle with AI contributions. Multiple curated lists now track "slop-free" software projects:

• Codeberg's slopfree-software-index
• Starlightnet's NoAI list

The concern is not unique to Godot. As AI coding tools become more capable, open source maintainers face a scaling problem: more contributions, but potentially lower average quality and no path to mentoring the next generation of maintainers.

What This Means for AI-Assisted Development

The Godot policy sits at one end of a spectrum. Other projects may take different approaches:

1. Ban AI entirely (Godot's approach for substantial code)
2. Require disclosure (already common in many projects)
3. Judge by output quality (ignore tooling, focus on results)
4. Require test coverage (AI code is fine if it comes with passing tests)

For individual developers, the takeaway is to check contribution guidelines before submitting AI-assisted PRs. For maintainers, the Godot policy provides a template - but not the only template.

The Foundation acknowledged this is a conservative approach and said they will "continue taking a conservative approach" while re-evaluating as tools evolve.

A Practical Note

If you use AI coding tools and want to contribute to projects with strict policies, the Godot guidelines still allow AI for:

• Code completion (copilot-style suggestions)
• Regex generation
• Find-and-replace automation
• Translation of human-written content

The ban targets autonomous agents that generate substantial code blocks or entire files without human authorship of the underlying logic.

Sources

• Godot Foundation Contribution Policy 2026 - Official policy announcement
• Hacker News Discussion - Community discussion with 160+ comments
• PC Gamer Coverage - Initial reporting

---

Last updated: July 1, 2026