OK, this is big. The Linux kernel's official documentation has received an entirely new file: coding-assistants.rst. It's not a recommendation to use AI — it's a clear message about what is not acceptable when contributing to the world's most important open source project.
A Hacker News thread that is exploding right now shows that people at the core of the AI and open source underground are genuinely surprised. Not because the rules exist, but because they have actually been written down and included in the kernel repo itself. It's a signal.
What do they actually say? In short: contributors who use AI tools to generate code for the Linux kernel have a personal responsibility to verify everything — line by line. No «AI said it, so it's fine.» Maintainers like Greg Kroah-Hartman have long complained about an increase in low-quality patches that smell of AI, and now patience has clearly run out.
Why does this matter beyond Linux? Because the Linux kernel is the reference point for how serious open source projects are run. When they introduce formal rules, others will follow — Python, Apache, GNOME, all the big ones. Research supports the concern: a Veracode study found security flaws in 45% of AI-generated coding tasks, and Black Duck reported in 2026 that two-thirds of commercial codebases had license conflicts, partly thanks to what is called «license laundering» via AI tools.
This is not anti-AI hysteria. Kroah-Hartman himself has admitted that the tools have gotten much better. But it's a clear message that «vibe coding» and unreflected AI-paste do not belong in code running on billions of devices.
In the HN thread, it's interesting that many experienced kernel developers actually support the measure — not to stop AI, but to stop the wave of half-finished patches that kill maintainer energy. Seth Larson from the Python Software Foundation has described the same problem: an explosion of LLM-hallucinated security reports that no one bothers to read.
What happens next? Keep an eye on whether other large projects copy this RST file or create their own variants. That's where the next signal will come from.
NB: This is an early signal based on community activity on Hacker News and publicly available kernel documentation — not a confirmed news article from official sources.