COSMIC Bans AI-Written Code While GNOME Debates Letting AI Bug Reports In
Two of Linux's most-used desktop projects are pulling in opposite directions on artificial intelligence. One has drawn a hard line; the other is being nudged toward opening a door that's hard to close.
Key points
- System76's COSMIC desktop now requires every contributor to declare they used no AI-generated code, comments or submission notes, making it one of the strictest such policies among major open-source projects.
- GNOME, the default graphical interface on Red Hat Enterprise Linux and millions of other computers, bans AI contributions in several sub-projects but has no blanket rule.
- GNOME developer Michael Catanzaro published a post in September 2026 arguing GNOME must accept AI-generated bug reports because its codebase, partly written in a memory-unsafe language called C, produces too many security holes for humans to catch alone.
- Debian and the Linux kernel already allow AI-assisted contributions, with developers held accountable for what they ship.
System76, the American PC maker behind Pop!_OS, has updated the rules for anyone contributing to its COSMIC desktop environment. A desktop environment is the visual layer users actually see and click: windows, menus, icons, the taskbar. COSMIC is System76's own, built from scratch in Rust and shipped with Pop!_OS in late 2025.
The new rule is blunt. Every contributor must sign off: "I have not included any LLM (also known as AI) generated content in this PR, including code, comments, and descriptions." An LLM, or large language model, is the technology behind chatbots like ChatGPT. A PR, or pull request, is the package of changes a developer submits for review. The ban covers everything: the code itself, the surrounding documentation, even the cover note explaining what a change does.
Using AI to learn is still fine. Hunting for bugs with it is fine too. Pasting what it writes into a submission is not.
Why does it matter which language software is written in?
This is where the GNOME side of the story gets interesting, and uncomfortable.
GNOME, the desktop that's shipped by default with Red Hat's commercial Linux product since 1999, is largely written in C. C is a fast, powerful language that doesn't automatically stop programmers from making certain classes of memory mistakes. Those mistakes, left undetected, become security vulnerabilities.
Catanzaro argued in a September 2026 blog post that no matter how skilled the humans involved, writing secure C at scale is simply too hard. His exact words: "No matter how much we try, GNOME developers will fail [to] write secure code when using unsafe languages like C, C++, or Vala: it's just too hard for even experienced developers to do properly." AI tools are already finding bugs in large codebases faster than human reviewers can keep up, and blocking AI-generated bug reports means turning away a tool that's actively making software safer.
His argument lands against a specific backdrop. Red Hat employs many GNOME developers and is the project's biggest financial backer, and it's been openly enthusiastic about AI adoption. That institutional weight sits behind any push to soften GNOME's restrictions, even without a formal policy change yet.
Watching this beat, the most important thing to track isn't today's policy statements but the sequence Catanzaro's proposal sets in motion. We reported on Debian's move to allow AI tools on 31 August 2026, and our earlier story on KDE's AI desktop proposal from 18 September shows the same pressure building across the ecosystem. Once AI-generated bug reports are accepted, AI-assisted triage is a short step. After that, AI-assisted fixes. The door Catanzaro wants to open a crack tends not to stay there.
It's also worth placing COSMIC's ban in context: the project is young enough that a clean rule is still enforceable. GNOME's situation is messier by every measure of scale and history.
What does this mean for ordinary Linux users?
For most people running a Linux desktop right now, nothing changes today. The policy fight is between contributors, not users. But if AI-assisted code flows into major projects, users will feel it downstream: faster bug fixes on one side, harder-to-audit software on the other. This debate, first reported by The Register AI, is only getting louder.
