System76 Turns COSMIC's PR Checkbox Into an AI Ban While the Linux Kernel Asks for Disclosure

System76's COSMIC desktop no longer accepts pull requests that contain LLM-generated content. The change is a single checkbox in the pull request template at pop-os/cosmic-epoch, where contributors must now confirm they have not included "AI generated content in this PR, including code, comments, and descriptions."

The change was reported on October 2, 2026 by XDA Developers, via an aggregator summary, and by Linuxiac. Neowin's version, "Pop!_OS bans AI-generated code from much of its codebase," reached 110 points on Hacker News on October 4.

What the template now requires

The template lists five commitments. The contributor has no AI-generated content in the PR, understands the changes in full and can respond to review comments, has described the change accurately in the commit message, has tested it, and certifies it under the Developer Certificate of Origin.

Its preamble says incomplete submissions will be closed. Per Linuxiac, the policy replaces a rule that asked contributors to disclose AI assistance.

Linuxiac names pop-os/cosmic-epoch as the repository the policy applies to. It also says cosmic-flatpak is an exception, because upstream projects maintain their own Flatpak manifests and COSMIC developers review those mainly for sandboxing.

The ban is narrower than the Hacker News headline suggests. The template itself never mentions Pop!_OS, and the summaries we read say COSMIC still allows non-generative AI uses such as tools that help find bugs.

Why System76 says it did this

Linuxiac attributes the reasoning to Jeremy Soller of System76, who it quotes as citing "the extra review work for the COSMIC team." Maintainers had seen more first-time contributors submit LLM-assisted work, Linuxiac reports, and little of it was accepted.

The XDA summary gives the same reason: maintainers were "getting swamped with low-quality or unreviewable contributions." We found no statement from System76 itself beyond the template. Both accounts are secondhand.

How the policies compare

The kernel took a different route. Its documentation on tool-generated content tells contributors to be "transparent about the origin of content in cover letters and changelogs," and to state which tools they used, the inputs, which parts the tools affected and how the result was tested.

Project	Rule	Source
COSMIC (cosmic-epoch)	No AI-generated code, comments or descriptions; certify in the PR	PR template
Linux kernel	Allowed with disclosure of tools, prompts and affected parts	docs.kernel.org

The kernel text puts the burden in one sentence: "You are expected to understand and to be able to defend everything you submit." COSMIC's template carries the same demand, that the contributor understand the changes in full and answer review comments, and then adds the ban on top.

According to the XDA summary, Ubuntu has also chosen to allow high-quality AI content, which would put System76 at the strict end of the Linux desktop world. We did not fetch an Ubuntu policy document, so treat that as the summary's claim.

What the checkbox cannot do

A checkbox is an honour system. Nothing in the template describes a detector, and none of the sources we read says how a maintainer would tell a hand-written patch from an LLM-assisted one. The rule works because a maintainer can close a PR that reads wrong, not because it can prove a negative.

That puts the cost on the people System76 says it wants to protect. A contributor who used an autocomplete suggestion has to decide whether it counts, and the template gives no threshold.

The next thing to watch is whether the exception for cosmic-flatpak holds, and whether COSMIC's other repositories adopt the same template. Related reading on the kernel side: Greg Kroah-Hartman on LLM-found kernel CVEs, and on the other end of the agent boom, Agent-Reach.