Linux Declares It Won’t Reject AI, as Linus Torvalds Sets Terms for Accepting Automated Review
Linux Declares It Won’t Reject AI, as Linus Torvalds Sets Terms for Accepting Automated Review
https://xenospectrum.com/en/linux-ai-sashiko-review-policy/
Publish Date: 2026-07-16 17:49:00
Source Domain: xenospectrum.com
On July 15, 2026, Linus Torvalds declared in an email concerning Linux kernel development policy that Linux “will not be an anti-AI project.” He stated flatly that participants who cannot accept the use of AI have the option, in the open-source tradition, to fork the project or leave it.
Taken at face value, the strong wording looks like an ultimatum from the pro-AI camp against dissenters. But the debate didn’t start from a proposal to fully open the door to AI-generated code. The real question was: to whom should the findings from the AI review system “Sashiko” be sent, and who should confirm the false positives? What Linux ran into was the allocation of human time that remains even after generation speed increases.
Torvalds’s answer isn’t to hand judgment over to AI either. Linux’s current rules require that a human read AI-generated code, verify its licensing, and take it on under their own signature. The entry point stays open. But the exit point for responsibility doesn’t move from the human.
- 01.The Spark: Whose Inbox Should Sashiko Connect To?
- 02.How to Read That 53.6% Self-Assessment
- 03.Humans Sign Off, and Take on the Responsibility
- 04.Reconciling Individual Refusal with a Shared Workflow
- 05.Not Pushing the Cost of False Positives Outside the Workflow
The Spark: Whose Inbox Should Sashiko Connect To?
The originating thread, “Linking Patchwork with Sashiko?”, began on the Linux Media Mailing List on May 30. Patchwork is a system that tracks patches arriving via email; linking it to Sashiko’s review results would let authors and maintainers process findings within the same workflow. But when it came to deciding who the automated emails should be addressed to, efficiency and consent collided.
Longtime kernel developer Laurent Pinchart argued that before Sashiko’s findings are sent to an author, any maintainer who wants to use it should first screen the content and confirm its correctness—also respecting the wishes of authors who don’t want to receive…
