Godot Bans AI-Generated Code Contributions: 'We Can't Trust Heavy Users of AI'

The Godot open source game engine has officially stopped accepting AI-authored code contributions. In a decision announced today, maintainers stated they cannot trust heavy users of AI to understand their code well enough to fix it. The move follows months of debate within the community about the rising tide of low-quality AI-generated pull requests, which maintainers had previously described as 'increasingly draining and demoralizing' for code reviewers.
Background
In February, the Godot team acknowledged the problem of AI slop PRs flooding the project. They deliberated on how to address the issue, weighing the potential benefits of AI assistance against the significant costs to reviewer morale and project quality. Now, after months of internal discussion, the ban is official.
Key Points
- Ban effective immediately: All AI-generated contributions are no longer accepted.
- Rationale: Heavy AI users often cannot explain or fix their own code, making reviews unsustainable.
- Impact on community: The ban aims to reduce the burden on volunteer reviewers and maintain code quality.
Godot powers notable games such as Slay the Spire 2 and The Case of the Golden Idol. The decision sets a precedent for other open source projects grappling with similar issues. AI coding tools, while useful for prototyping and boilerplate, often produce code that is hard to maintain, debug, or integrate into a complex codebase without human expertise.
📖 Read the full source: HN AI Agents
👀 See Also
Abandoning Claude for Hand Coding: A Developer's Reckoning
A developer explains why they abandoned Claude-generated code for their side project, preferring hand coding for its clarity and satisfaction. Includes community reactions on AI-assisted workflow.

Nvidia reportedly developing open-source NemoClaw to compete with OpenClaw
Recent reports suggest Nvidia is working on an open-source project called NemoClaw aimed at directly competing with OpenClaw in AI development tools. The project is expected to focus on improving performance, scalability, and developer flexibility while maintaining compatibility with modern AI workflows.

OpenClaw's Frequent Breaking Changes: Update Procedures and Current Issues
OpenClaw has released 13 point versions in March 2026 alone, with breaking changes occurring every 2-3 weeks. The source provides specific update procedures and details current issues in version 3.28, including localhost authentication changes and regression bugs.

OpenClaw Agent Auto-Edits HEARTBEAT.md, Adds 10 Self-Assigned Tasks
In a default HEARTBEAT.md execution, an OpenClaw agent added 10 self-assigned tasks including system review, memory maintenance, and weather checks — raising token burn concerns.