Godot bans AI coding agents from contributions

The clearest reading of Godot's decision is economic, not ideological. AI collapsed the cost of producing a pull request toward zero while the cost of reviewing one - and the number of humans qualified to do it - stayed fixed ^[1]. That asymmetry floods a system built for a slower era. Godot's GitHub already carries over 5,000 unresolved pull requests, described as the largest bottleneck in the engine ^[7]. The Foundation is explicit that PR review, not code-writing capacity, is where the project chokes, and that the pool of qualified reviewers is small and cannot keep pace ^[1]. Trade coverage reinforces that framing: AI lowered the effort to open a PR and therefore the volume, while review effort and reviewer headcount held constant ^[6]. Seen this way, the ban is a supply-side control on a resource - reviewer attention - that money cannot easily buy in a volunteer project.

Godot went out of its way to make this a targeted rule rather than a blanket rejection of AI. Menial assistance such as code completion, regex, and find-and-replace stays allowed, provided contributors disclose the AI use in the PR discussion ^[4]. What is banned is autonomous agent use, AI generating substantial pieces of code, and AI-generated text in human-to-human communication with maintainers ^[6]. The rationale is accountability: the Foundation argues AI cannot take responsibility for code and that heavy AI users often cannot understand or fix what they submit ^[3]. Community discussion surfaced a sharper version of the same principle - that maintainers 'do not want to talk to a machine' and treat human authorship as a matter of basic respect. This is what separates Godot's move from a fear-of-technology stance: the object being protected is the human review-and-mentoring loop, where feedback on a PR trains a future maintainer rather than a model ^[2].

Godot is exposed precisely because of what makes it different from its biggest rivals: it accepts external pull requests. Community observers noted that closed engines like Unity and Unreal do not take outside PRs, so they never feel the AI-submission flood - Godot is among the first to act because it is one of the most popular open-source engines. That makes it a leading indicator for open source broadly, and it is far from alone in responding. Hackaday cataloged a spectrum of reactions: Mesa now demands that submitters comprehend their code, NetBSD treats LLM-generated code as 'tainted' over licensing concerns, and the Linux kernel requires human submitters to declare AI tool usage ^[5]. Community threads added curl, which dropped bug bounties amid AI noise, and Zig as further examples of projects curbing AI submissions. The pattern suggests a converging norm - disclosure, comprehension, and human accountability - even as each project picks a different enforcement point along it.

The policy is not uncontested. Its hardest edge is enforcement: bans for autonomous-agent PRs are immediate and unappealable ^[1], yet the rule leans heavily on self-disclosure of AI use, which is difficult to verify at scale. The friction lands most on newcomers - contributors with three or fewer merged PRs now need explicit maintainer permission before submitting features or significant refactors ^[1], a barrier that curbs low-quality volume but also raises the cost of a first legitimate contribution. On substance, a notable dissent in developer forums argued that framing review of AI PRs as 'not rewarding enough' is a weak justification for a project whose goal should be building the best possible engine, not optimizing maintainer satisfaction. That objection cuts to the core tension: Godot is prioritizing the health and motivation of its human review pipeline over raw contribution throughput - a defensible trade for a volunteer project, but one that only works if disclosure norms hold and the mentoring payoff it is protecting actually materializes.