Godot bans AI-authored contributions, and the distinction matters
Earlier this month, the Godot Foundation published an update to its contribution policies, dated June 30, that draws the hardest line any major engine has drawn on AI. All code contributed to the engine must be human authored. AI assistance is allowed only for menial work like code completion, regex, or find-and-replace, and if you used AI in any capacity to author code, you have to say so in the PR discussion. The same rule covers communication: issue descriptions, PR messages, and proposals must be written by a person, not generated by a model. Autonomous agents and vibe-coded submissions were already grounds for an automatic ban from the repository, and they stay that way.
Community coverage of the Godot contribution policy update
The policy, in plain terms
The reasoning the Foundation gives is about responsibility, not ideology. A contribution to Godot isn't a one-time transaction. Whoever writes the code needs to understand it well enough to defend it in review, fix it when it breaks, and answer questions about it years later. The post puts it bluntly:
"We can't trust heavy users of AI to understand their code enough to fix it."
Godot Foundation, contribution policy update
AI can't take responsibility for a line of code, so a human has to, and a human who didn't write the code usually can't. The communication rule follows the same logic. Maintainers volunteer their time to review your work, and the Foundation calls it a basic principle of respect that they get to talk to a person rather than a machine. Machine translation still passes, as long as a human wrote the original. There's also a new brake on ambition: contributors with three or fewer merged PRs can't open new features or significant refactors without a maintainer's go-ahead.
Four months from complaint to policy
None of this arrived out of nowhere. Back in March we covered Rémi Verschelde describing the flood of AI slop PRs as draining and demoralizing for maintainers, with the open PR queue sitting at 4,681. By the time the policy landed, coverage put the queue above 5,000. The economics haven't changed since March. AI dropped the cost of generating a plausible-looking PR to near zero while the cost of reviewing one stayed exactly where it was. What changed is that Godot stopped treating that as a moderation problem and started treating it as a policy problem. The update came less than two weeks after Godot 4.7 shipped, which tells you the maintainers' scarce resource isn't the ability to ship, it's review attention.
Contribution isn't creation
We build an AI game-creation platform, so let's be direct about the tension instead of pretending it isn't there. The most-used open-source indie engine just said AI-written code isn't welcome, and AI is the whole way games get made on Cinevva. Those two things sound opposed. They aren't, and the difference is who carries the code afterward.
When you merge a PR into Godot, hundreds of thousands of developers inherit that code, and a small group of volunteers becomes responsible for it indefinitely. The author's understanding is the only warranty the project gets, which is exactly what heavy AI use removes. When you build your own game with AI, you own the result. If it breaks, it's your game that breaks. Nobody else inherits your code, and no volunteer has to review it.
Godot didn't ban making games with AI, and couldn't if it wanted to. It banned outsourcing your half of a shared responsibility to a model. That's a defensible line, and honestly, it's the same one we'd draw. The tools can write the code. Someone still has to stand behind it.