Linux kernel formalizes AI coding tool rules for all contributors

a computer screen with a bunch of code on it

The Linux kernel project now has formal written rules for anyone using AI coding assistants in their contributions. The documentation is official, and compliance is not optional.

What the Policy Requires

Before touching a single line of kernel code with AI help, contributors must read the full development process, coding style, and submitting-patches documentation. From there, three hard requirements apply:

  • Human responsibility: The contributor is fully accountable for every line an AI generates. No offloading blame to the model.
  • Assisted-by tags: Any AI-assisted commit must include a proper attribution tag disclosing which tool was used.
  • GPL and DCO compliance: All AI-generated code must meet the same license and Developer Certificate of Origin standards as human-written code.

Real-World Use Inside the Kernel

The policy did not emerge in a vacuum. Linus Torvalds and maintainer Lorenzo Stoakes have both used AI tools in kernel work, with reported productivity gains. Both cases also required heavy human oversight to catch errors before submission, which is exactly the pattern the new rules are designed to enforce.

Submission volume from AI-assisted contributors has been rising, and the Assisted-by tag requirement gives maintainers like Sasha Levin visibility into which patches have AI involvement so they can calibrate their review depth accordingly.

Why This Matters Beyond Linux

This is one of the first major open source projects to codify AI tool governance at the policy level rather than leaving it to informal norms. For developers who contribute to any open source project, the Linux approach signals where the broader ecosystem is likely to move: disclose AI use, own the output, and keep the human in the loop on every merge.

Stay on top of AI & Automation with BizStack Newsletter
BizStack  —  Entrepreneur’s Business Stack
Logo