Linux Kernel Implements AI-Assisted Code Contribution Policy with Disclosure Requirements

This policy formalizes the role of AI in software development, balancing innovation with accountability in a rapidly evolving tech landscape.

• In April 2026, Linux kernel maintainers, led by Linus Torvalds, finalized a policy allowing AI-assisted code contributions with mandatory disclosure.
• Developers must use an 'Assisted-by' tag to indicate AI tool usage and cannot let AI add 'Signed-off-by' tags, ensuring human accountability.
• This decision follows months of debate over undisclosed AI-generated patches and concerns about quality control in open-source projects.

• AI-generated code submissions have surged, raising concerns about quality and accountability, particularly after an undisclosed AI patch caused issues in Linux 6.15.
• Initial discussions on AI policy began in July 2025, evolving through various summits and community feedback, highlighting the need for transparency and legal clarity.
• Other open-source projects have faced similar challenges, with some implementing outright bans on AI contributions, contrasting with Linux's more nuanced approach.

The Linux kernel's new policy on AI-assisted code contributions represents a significant shift in how open-source projects can leverage AI tools while maintaining accountability. The decision comes after a series of incidents where undisclosed AI-generated patches led to performance regressions, notably an incident involving Nvidia engineer Sasha Levin's submission. This highlighted the risks of integrating AI into development without proper oversight.

The policy introduces the 'Assisted-by' tag, which developers must use to disclose AI tool usage, such as GitHub Copilot or Claude. This tag serves as a clear marker that AI was involved in the code generation process, ensuring that human developers remain accountable for the final output. By prohibiting AI from adding 'Signed-off-by' tags, the policy reinforces the principle that human oversight is essential in the development process.

This formalization of AI's role in the Linux kernel is not just about compliance; it reflects a broader trend in the tech industry where AI tools are becoming standard in software development. The Linux community's approach contrasts with other open-source projects that have opted for stricter bans on AI contributions, such as Gentoo and NetBSD. By allowing AI tools while enforcing transparency, Linux aims to strike a balance between innovation and quality control.

The policy also addresses the growing phenomenon of 'AI slop,' where poorly generated code floods projects, undermining their integrity. By mandating human review and compliance with licensing, the Linux kernel maintainers are setting a precedent that could influence other open-source communities. This move is likely to enhance the utility of AI tools in generating security reports and other contributions, although the challenge of managing AI-generated content remains.

As the tech landscape evolves, this policy could serve as a model for other organizations looking to integrate AI responsibly. The Linux kernel's decision reflects a recognition that while AI can enhance productivity, it must be managed carefully to avoid compromising the quality and reliability of open-source software.

• Software developers using AI tools for coding will need to adapt to new disclosure requirements.
• Open-source project maintainers will have to implement and enforce these policies, impacting their workflow and review processes.
• Tech companies leveraging Linux in their infrastructure may need to adjust their development practices to align with this new standard.

• Adoption rates of the 'Assisted-by' tag: Monitoring how quickly developers integrate this tag will indicate the policy's acceptance and effectiveness.
• Impact on code quality: Observing changes in the quality of contributions and the frequency of 'AI slop' incidents will reveal the policy's real-world implications.
• Responses from other open-source communities: How other projects react—whether they adopt similar policies or maintain bans—will shape the future landscape of AI in software development.