Godot says bye bye AI, bans vibe-coded contributions

2026-07-01 · Source: The Register: Enterprise Technology News and Analysis · Field: Technology & Digital — Software Development & Engineering, Artificial Intelligence & Machine Learning, Emerging Technologies & Innovation · Depth: Fundamental Awareness, short

Summary

The Godot open-source game engine announced on Wednesday, July 1, 2026, a new policy to prohibit almost all AI-generated contributions, citing an overwhelming number of "vibe-coded" pull requests that are difficult to review and fix. Maintainers described these contributions as "demoralizing" and stated they "can't trust heavy users of AI to understand their code enough to fix it." The updated policy will require new contributors (those with three or fewer merged pull requests) to seek explicit permission for new features or significant refactoring. It also mandates human-to-human contribution discussions and bans substantial AI-authored code, limiting AI assistance to "menial things" like code completion, with disclosure required. This move reflects a broader trend of "vibe coding" falling out of favor due to incidents like deleted databases and wiped drives, with industry leaders emphasizing context in software development.

Key takeaway

For open-source project maintainers evaluating contribution policies, Godot's experience highlights the critical need to proactively address AI-generated "vibe code." You should consider implementing clear guidelines that prioritize human understanding and accountability, such as requiring disclosure for AI assistance and restricting substantial AI-authored code. This approach can prevent reviewer burnout, maintain code quality, and foster a more engaged, knowledgeable contributor community, safeguarding your project's long-term health.

Key insights

AI-generated code often lacks human understanding, burdening maintainers and degrading contribution quality.

Principles

• Code quality requires human context and accountability.
• Untrustworthy contributions demoralize open-source teams.
• AI assistance should be limited to menial tasks.

Method

Godot's policy updates include requiring explicit permission for new contributors, mandating human-to-human discussions, and banning substantial AI-generated code, with disclosure for minor AI assistance.

In practice

• Implement strict AI contribution policies.
• Require disclosure for AI-assisted code.
• Prioritize human understanding in code reviews.

Topics

• Open-Source Contribution
• AI Code Generation
• Godot Engine
• Code Quality
• Developer Experience
• Policy Updates

Best for: CTO, VP of Engineering/Data, AI Engineer, Software Engineer, Director of AI/ML, Tech Journalist

Related on AIssential

• The End of Vibe Coding — Ambiguous instructions, or "vibe coding," lead to AI agent failures; precise specifications are key.
• Linus Torvalds on the AI claim that makes him angry, and what security researchers should never do — AI tools boost developer productivity and contribution volume but introduce social and security challenges in open-source projects.
• Bluesky users are mastering the fine art of blaming everything on "vibe coding" — User perception of AI-assisted coding as inherently flawed creates a default blame for tech issues.
• How Sustainable is Vibe Coding? — AI's true value in coding lies in augmenting experienced developers, not replacing foundational understanding for novices.
• A new worst coder has entered the chat: vibe coding without code knowledge — Vibe coding tools enable rapid app creation but often produce insecure, unmaintainable code without developer oversight.
• Breaking the Spell of Vibe Coding — Vibe coding can induce a "dark flow" state, similar to gambling, leading to misperceptions of productivity and skill development.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by The Register: Enterprise Technology News and Analysis.