Tools

Godot Bans AI Code: What It Means for Open Source

2 July 2026 Mehdi 06:36
Godot interdit contributions code IA

The flood of AI-generated pull requests had become a real problem for Godot’s maintainers. In late June 2026, the Godot Foundation decided to put a formal end to it, announcing an explicit ban on AI-generated contributions. It’s one of the strictest policies ever adopted by a major open source project.

Godot Bans AI Code Contributions: What’s Covered

The announcement goes beyond source code. The Godot Foundation covers three distinct categories in its new policy:

  • Code written by an AI
  • Pull requests submitted by automated AI agents
  • AI-generated text in human-to-human exchanges within the project

This triple scope is unusual. Most open source projects that address the issue focus solely on code. Here, even communications between contributors are included. The Foundation does clarify that automatic translations remain acceptable, provided the original text was written by a human.

The Real Problem: Maintainability and Accountability

The Foundation’s reasoning is direct and unambiguous. Since February 2026, review teams had been reporting an exhausting increase in low-quality pull requests produced by generative tools, what the community calls “AI slop code.”

Code review is already a grind. When that work no longer serves to mentor a future contributor but instead responds to a machine, it loses much of its value. Volunteer maintainers can’t afford to burn through their time and motivation on contributions that nobody truly understands.

The Foundation’s wording is striking: “AI cannot take responsibility, and we can’t trust heavy users of AI to understand their code enough to fix it.” This isn’t an ideological stance. It’s a matter of concrete maintainability and a clear chain of accountability.

What This Policy Will Change in Practice

Godot’s contribution guidelines will be updated to reflect these new rules. The Foundation wants to focus efforts on four areas:

  • Adding barriers to low-effort contributions
  • Encouraging current maintainers to keep reviewing
  • Training new contributors so they can become future maintainers
  • Requiring that every contribution come from a human who understands their code and can take responsibility for it

Using AI for minor tasks is still tolerated, as long as it’s disclosed. The line drawn is one of accountability: a human contributor must be able to explain, defend, and fix what they submit.

The Foundation also acknowledges that the growing volume of contributions is a positive signal. Interest in Godot is rising. The problem isn’t the growth, it’s the quality and traceability of submissions.

Why This Decision Is Sparking Debate in Open Source

Godot enjoys a high level of goodwill in indie developer communities. The reaction seen across specialized forums has been largely positive. Many view this decision as an act of resistance against the gradual erosion of standards in collaborative projects.

But the real question remains open: how do you enforce such a policy reliably? Detecting AI-generated code is not an exact science. Detection tools are imperfect and easily bypassed. The Foundation itself acknowledges that the AI tools landscape is evolving rapidly and that it will reassess its policy accordingly.

In a context where AI assistants are integrated into virtually every developer’s IDE, maintaining such a line requires a genuine project culture and trust in contributors’ good faith. That will be the real test over time.

This decision positions Godot as a reference project on this topic. Other game engines and open source libraries will certainly watch closely how this policy plays out before considering similar rules of their own.

Key Takeaways

  • The Godot Foundation formally bans AI code, automated agent PRs, and AI-generated text in exchanges between human contributors.
  • The central justification is accountability: a contributor must understand their code well enough to fix it.
  • The policy responds to a real burnout among maintainers facing an influx of low-quality contributions.
  • Using AI for minor tasks is still tolerated, provided it is disclosed.
  • Whether this can realistically be enforced over time remains the real unknown.

This decision raises questions that go beyond Godot and concern the entire open source ecosystem. If you work on contribution policies or collaborative project governance, feel free to discuss it via the blog or on LinkedIn.

Sources

Read Also

Leave a comment

Your email address will not be published. Required fields are marked *