Godot contribution policy changes (2026)

First-party announcement (Godot Foundation, 30 June 2026) tightening how contributions are accepted into Godot, primarily to restrict AI-generated code and relieve reviewer burnout. Tier T1 — the project’s own governance statement on godotengine.org. The Foundation calls it a deliberately “conservative approach” open to revision as AI tooling matures godot-contribution-policy-2026.

What changed

AI-generated code is restricted, human authorship required. Substantial AI-generated code is banned — a human must author every contribution. Autonomous AI agents and “vibe coding” are prohibited outright (auto-banned from the GitHub org). AI is allowed only for menial help — code completion, regex, find-and-replace — and any AI assistance must be disclosed. AI-generated text is also forbidden in maintainer communications.
New-contributor gates. A “new contributor” is anyone with ≤3 merged PRs. New contributors must get explicit maintainer permission before proposing a new feature or a significant refactor, and are expected to start with bug fixes and documentation to build trust.
Human review reaffirmed. A human reviewer must approve every PR before merge.

Why (the Foundation’s stated reasons)

A mounting backlog of open PRs against too few qualified reviewers, worsened by reviewer burnout from low-effort AI submissions. Two further rationales are about people, not throughput: machines can’t learn from review feedback, so low-effort AI PRs drain the mentorship value that grows future maintainers; and contributors must understand and be able to maintain the code they submit.

Why it’s here

This is a Godot Foundation governance artifact, and the clearest sequel to the Vision Statement: where the Vision Statement wrote down the engine’s values, this writes down the rules for getting code in. Both are the same move — formalizing what used to be tacit as the contributor pool outgrew learning it by osmosis — and both are governance-as-legibility-at-scale. So Godot’s “vision-as-governance” axis now has a second, sharper-edged instance: the Foundation governs not just direction but contribution intake, and it is the first engine in this wiki to take an explicit, enforced stance on AI-generated contributions — a concrete data point on how the “AI tooling reshaping [engine] development” thread is being resisted at the community layer, not just adopted in the editor.

Cross-spoke

../agentic-tooling-wiki — the ban on autonomous agents / vibe coding is a notable counter-current to that spoke’s autonomous-coding thread: a major FOSS project drawing a hard line against exactly the agent-authored-PR workflow those tools enable. The mentorship rationale (“machines can’t learn from feedback”) is a human-side argument the tooling spoke’s efficiency framing doesn’t capture. Noted there as context, subject stays here (Godot governance).
../ai-governance-wiki — an organizational AI-use policy (disclosure, prohibited uses, human-in-the-loop), the community-project analog of the enterprise AI governance that spoke tracks — but a project contribution policy, not law/standard/national strategy, so cross-linked not routed.

Where the line actually falls (2026-07-27)

The policy governs contributing to the engine, not using it. Three weeks after it landed, the Godot Asset Library listed godot-mcp-toolkit — a community plugin handing an AI agent 112 tools to build scenes, write scripts and run playtests inside the editor. Both are Godot, and they don’t conflict: agents may drive your project, and may not author the engine’s own source. The plugin’s own listing keeps the distance explicit, stating it is an independent add-on not affiliated with or endorsed by the Foundation.

That makes the line legible in a way the policy alone didn’t. What the Foundation is protecting is the mentorship pipeline that produces maintainers, not the codebase’s purity, and nothing about that argument extends to how a user builds a game. See engine-agent-surface for the surface the plugin provides.

godot-foundation · godot-vision-statement · godot-engine · godot-mcp-toolkit · engine-agent-surface · juan-linietsky · ariel-manzur