The Linux kernel project just added official documentation on how contributors should use AI coding assistants - and it's more nuanced than a blanket ban or endorsement.
The new guidance, added to the kernel's official process documentation, doesn't name specific tools. Instead it focuses on accountability: if you submit code that was generated or assisted by an AI tool, you're fully responsible for every line. You're expected to understand the code, test it properly, and be able to defend it during code review.
The practical concern driving this policy is real. AI coding assistants - tools like Cursor, Aider, or Cody that suggest or write code based on natural-language descriptions - tend to produce code that looks correct at a glance but contains subtle bugs or ignores project-specific conventions. The Linux kernel has exceptionally strict coding standards, and maintainers (mostly volunteers) waste significant time reviewing patches that violate them.
A blanket ban would be unenforceable - there's no reliable way to detect AI-assisted code. The accountability-based approach is more honest: we don't care what tools you used, we care that you understand what you submitted.
This sets a clear precedent for how major open-source projects handle AI tools. Other projects with rigorous review processes - GCC, LLVM, CPython - are watching how the kernel handles this. The policy treats AI assistance the same way it treats any other tool: useful in the right hands, dangerous when it substitutes for understanding.
For developers who contribute to open-source work, the message is clear: AI can help you write the code, but it can't do your homework for you.