Pop!_OS draws a line: COSMIC pull requests must contain no AI-generated content
LLM
A large AI system that can generate text or code.
pull request
A submitted change asking a project to review and merge it.
maintainer
A person who reviews and manages a software project.
What happened
System76, the company behind Pop!_OS, tightened contribution rules for COSMIC, its desktop project. A pull request merged on September 30, 2026, added a new check to the project template. Contributors must confirm that their pull requests contain no LLM-generated content. The rule covers code, comments, and descriptions. The same wording appears in the Pop!_OS repository template. PR #3911
Neowin, a technology news site, reported that many COSMIC codebases now reject AI-generated content. It identified the cosmic-flatpak repository as an exception. The public records do not provide a complete map of every repository covered. Neowin report
The background
The reported reason is review capacity. Neowin said the team was receiving too many AI-assisted changes. Many came from first-time contributors. The changes were often unplanned and showed little understanding of the project's architecture. That made them costly to evaluate, even when a patch appeared to solve a local problem.
A maintainer must do more than check whether code runs. The maintainer must understand why the change exists. They must see how it fits COSMIC and whether the contributor can explain and test it. The new checklist responds to that burden at the point of submission.
Why it matters
AI can reduce the time needed to produce a patch. It does not automatically reduce the time needed to understand that patch. A larger change can create a larger reading task. If the author cannot explain the design, reviewers must reconstruct the reasoning themselves.
System76 has therefore put human understanding ahead of raw generation speed for this contribution path. That does not prove that AI-generated code always fails. It shows one project choosing reviewability as a condition for participation. The policy also makes a hidden cost easier to see: someone must pay for the time spent checking every change.
What is confirmed
The official COSMIC template asks contributors to confirm that their pull request contains no LLM-generated code, comments, or descriptions. It also asks them to understand the changes, describe them accurately, test them, and follow the Developer Certificate of Origin. COSMIC pull request template
PR #3911 is merged. The rule is therefore part of the live submission process, not only a proposal. The story also drew attention on Hacker News. Its points and comment count measure community attention. They do not prove that the report or the policy is correct. Hacker News discussion
What remains unknown
The public checklist does not say whether contributors may use AI privately for search or bug analysis. It does not explain whether that use is allowed when no generated material enters the pull request. It also does not show whether every System76 repository will use the same rule. No before-and-after data shows whether the review queue became smaller. The scope of the cosmic-flatpak exception also needs clearer documentation.
What to watch next
The next useful evidence will come from repository templates, contribution guides, and actual pull request decisions. It will show whether the rule reduces review work or changes who contributes. Other projects may choose disclosure, human review, or a full ban instead. For now, the confirmed point is narrower: System76 has made human understanding the entrance requirement for much of COSMIC, even as AI makes code generation faster.
Why Pop!_OS says no to AI-written code
📰 Full story: Pop!_OS draws a line: COSMIC pull requests must contain no AI-generated content
System76 wants every submitted change to be understood by a person.
COSMIC
The desktop project connected to Pop!_OS.
pull request
A change sent to a project for checking.
code review
People read and test a change before accepting it.
💡 The gist
- System76 changed the rules for COSMIC contributions.
- Pull requests cannot contain AI-made code, comments, or descriptions.
- The goal is to reduce the team’s review burden.
System76 makes Pop!_OS, an operating system. It also develops COSMIC, its desktop project. People send changes through a pull request. A pull request asks the project to check a change.
The new template says contributors used no AI-made content. This includes code, comments, and descriptions. Contributors must also understand the change. They must describe it correctly. They must test it. Official template
Neowin, a technology news site, reported the reason. The team received too many AI-assisted changes. Many came from first-time contributors. Some changes were unplanned. They often showed little understanding of the project’s design. Neowin report
That is a code review problem. Reviewers read the change and test it. They also ask why the change belongs there. They check how it fits other parts. A change can work today but create work later. This is why understanding matters.
AI can make writing code faster. It cannot make more reviewers. If many changes arrive, people still need time to read them. System76 chose a strict rule for many COSMIC repositories. This rule puts human understanding before faster generation.
The rule does not prove that all AI code is bad. It also does not explain every private use of AI. The public report says cosmic-flatpak is an exception. The full list of covered repositories is still unclear.
Hacker News, a technology discussion website, also talked about the story. Attention is not proof. Many points and comments do not prove the rule is correct. Hacker News discussion
💬 The debate over Pop!_OS rejecting AI code
The comments were mainly about whether a project can review and maintain AI-assisted changes, not about AI being simply good or bad. People reported very different results depending on how carefully they used it.
- Supporters say the ban protects a small review team from many unplanned or hard-to-understand AI PRs. They want to prioritize the core team and regular contributors.
- Critics say a change should be judged by its design, tests, and human review, not only by whether AI helped write it. Closing an honest PR may drive people away, toward forks, or toward hiding AI use.
- User self-reports disagree: one person said two AI-started projects became messy; others say clear specifications, firm API boundaries, and small steps can work.
- One user self-reported building key parts of an SVG renderer in hours instead of at least a week of hand coding. That is one personal comparison, not a universal speed test.
- Hand-written code is not automatically good, and AI code is not automatically bad. AI may help find security bugs, but it can also raise false alarms, so people must check both bugs and fixes. Another user self-reported that Claude helped with a VPN password bug, but the carefully checked PR was still closed.
initial digest at 115 comments (revision 1). We fetched 100 comments and sampled 100 across the thread. These are HN users’ reports, not independently verified facts.
Why Pop!_OS says no to AI-written computer instructions
📰 Full story: Pop!_OS draws a line: COSMIC pull requests must contain no AI-generated content
Writing faster is not enough. Someone must still read the instructions.
COSMIC
The part of Pop!_OS that arranges windows and screens.
Hacker News
A website where people discuss technology news.
System76 makes Pop!_OS, a computer operating system. COSMIC arranges its windows and screens.
System76 changed the rules for COSMIC. AI-made code is not allowed in many submissions. Code means instructions for a computer. Comments and explanations cannot be AI-made either.
People must understand every change they send. People must test it too. AI can write quickly. It cannot add more readers. Too many changes can tire a small team.
Hacker News, a technology discussion website, talked about this story. Many comments do not prove the rule is correct. The public rule does not explain every private AI use.
Read the official template and the Hacker News post.
💬 Should Pop!_OS accept computer-written code?
The maintainers said they do not have enough time to check many AI-made changes. Some readers said good changes should not be rejected just because a computer helped.
- User self-reports differ: two AI projects became messy for one person, while another used plans and small steps successfully. That user said an SVG tool took hours with AI, versus at least a week of hand coding. Hand-written code is not always good either.
- A user self-reported that AI helped with a VPN password problem, but the change was closed. AI can help look for security problems, but it can also make mistakes. People must check the work.
initial digest at 115 comments (revision 1). We fetched 100 comments and sampled 100 across the thread. These are HN users’ reports, not independently verified facts.
💬 What HN commenters argued about Pop!_OS banning AI-generated code
The thread focused less on whether AI is inherently good or bad than on review capacity, maintainability, and how contributors should be treated. User self-reports split sharply: unstructured AI use was blamed for messy projects, while careful specifications, small tasks, and human verification were said to make AI useful.
initial digest at 115 comments (revision 1). We fetched 100 comments and sampled 100 across the thread. These are HN users’ reports, not independently verified facts.