Linus Lets AI‑Skeptics Fork Linux—A Developer Launches a No‑AI Linux Branch

Linus Torvalds stated that developers who dislike AI‑generated code in Linux may simply fork the kernel, saying, “Either fork it out or don’t do it.”

In response, a community developer released a dedicated fork called NoAI Linux , whose sole policy is to exclude any code produced with AI assistance.

Hard admission and filtering rules

All patch contributors must explicitly declare the origin of their code and indicate whether AI tools were used.

Any patch marked as AI‑assisted, or detected by automated tools as AI‑generated, is rejected outright.

An open‑source AI‑code detection tool runs on every submission to automatically filter hidden AI contributions.

The maintainer emphasizes that the branch stays in sync with the official stable Linux mainline, inheriting all security updates, driver additions, and feature improvements, so regular users can compile and install it without losing mainstream functionality.

Community reactions

AI‑opposed camp : Many kernel maintainers and embedded developers who previously called for banning AI code praised the branch, noting that it meets compliance needs for industrial and embedded projects concerned about copyright risks.

Neutral developers : Most ordinary kernel contributors view the parallel tracks as a healthy sign of open‑source diversity, seeing NoAI Linux as an optional path without a right‑or‑wrong judgment.

AI‑supporting developers : Some programmers who rely on AI tools worry about false positives, fearing that manually written code or code only formatted by AI could be mistakenly blocked, and acknowledge the difficulty of achieving 100 % accurate AI‑code identification.

Linus’s response

Upon learning of NoAI Linux, Torvalds replied humorously on the mailing list, saying the fork is exactly the outcome he envisioned. He reiterated that the mainline kernel only checks code quality and compliance statements, not the origin, and that anyone seeking stricter limits should use forking as the optimal solution.

Broader impact

The episode is regarded as a landmark case for how open‑source communities can handle AI‑code controversies, with several other projects considering similar multi‑branch strategies instead of imposing universal bans, thereby reducing endless debates.