Godot Restricts AI Code to Protect Volunteers

The Godot Foundation has stopped most AI-generated code submissions. This is to help their volunteer coders who were overwhelmed by low-quality AI code. Now, AI can only help with small tasks and must be declared.

The Godot Foundation has formally implemented a restrictive policy regarding AI-generated code in response to an overwhelming volume of low-quality submissions. Under the new guidelines, automated tools are barred from serving as the primary author of any contribution. While contributors may utilize AI for routine tasks—such as code completion, regular expression generation, or text replacement—they are now mandated to fully disclose such usage within their pull request threads.

Godot blocks automated code to protect governance - 1

The primary objective of this policy is the preservation of repository governance and the mitigation of review backlogs that have placed significant psychological strain on volunteer maintainers.

Godot blocks automated code to protect governance - 2

Current Policy Constraints

Restriction LevelPermitted ActivityMandated Action
Full AutomationProhibitedN/A
Assisted CodingCompletion, regex, bulk editingMandatory disclosure in PR
AccountabilityHuman-led logicFull verification of code

The "Slop" Dilemma and Maintainer Attrition

The influx of machine-authored content, often described by maintainers as "AI slop," has disrupted the collaborative nature of the Godot project. Primary maintainer Rémi Verschelde noted that the process of verifying machine-generated output is increasingly demoralizing, as it forces volunteers to spend finite resources vetting contributions from individuals who may not grasp the technical changes being submitted.

Read More: VALR integrates decentralized tech for new trading options from July 6th

Godot blocks automated code to protect governance - 3
  • The inability to definitively detect AI-authored code complicates these administrative efforts.

  • Projects are increasingly moving toward automatic rejection of unverified algorithmic submissions to maintain stability.

  • The sustainability of open-source models—historically predicated on distributed responsibility and human goodwill—is being tested by the high volume of machine-led output.

Contextual Shifts in Open Source

The decision reflects a broader, uneasy integration of autonomous agents into the software development lifecycle. While platforms like Ghostty and other open-source repositories are experimenting with "gated" AI use, the technical reality remains that current benchmarks often fail to mirror the nuanced requirements of senior engineering, such as navigating under-specified requests or complex, legacy codebase constraints.

As of April 2026, the Godot Foundation suggests that the fundamental problem is not the technology itself, but the lack of human accountability attached to the output. Without a "human on the hook" to accept liability for code performance and architectural integrity, the automated flood risks eroding the very collaborative foundation that sustains long-term development.

Frequently Asked Questions

Q: Why did the Godot Foundation start limiting AI code?
The Godot Foundation started limiting AI code because they received too much low-quality AI-generated code. This made it hard for their volunteer maintainers to review everything.
Q: Can I still use AI to help write code for Godot?
Yes, you can use AI for small tasks like code completion or text replacement. However, you must tell everyone in your code submission that you used AI.
Q: What happens if I don't declare AI code use?
If you don't declare AI code use, your contribution might be rejected. The main goal is to make sure a human is responsible for the code's quality and accuracy.
Q: How does this affect Godot developers?
This change helps protect the volunteer developers who review code. It means they can focus on good code and don't have to spend too much time checking bad AI code. This keeps the project healthy.