The Prague gathering pushed Linux's contribution threshold back a step. On October 8, 2026, at the Linux Maintainers Summit held in the Czech capital, kernel maintainers formally decided that submissions to the kernel no longer need to carry an Assisted-by tag. In plain terms: code written with help from large language models can now flow into the kernel exactly like code written with an IDE, with no special marker attached. The decision first surfaced through Sasha Levin's announcement to the kernel mailing list and was picked up by outlets including XDA Developers. The ruling itself was not a surprise — Linux's posture toward AI has long skewed pragmatic. What turned the discussion heated was Linus Torvalds's own reply on the list, combined with a patch series he had just submitted. ## Torvalds: a Ban on AI Is an Utterly Stupid Rule After the Maintainers Summit, contributors raised concerns about dropping the Assisted-by tag. Torvalds's reply was characteristically blunt: comparing a ban on AI use to a ban on text editors is itself an 'UTTERLY STUPID' rule. His core argument was that kernel developers already have the professional judgment required — code quality should be judged by the code itself, not by where it came from. He closed his message with: 'Quite honestly, in my experience, the people I respect and call intelligent are not the ones that shy away from using new and interesting tools.' That line has been read by many as Linux's formal AI posture — trust the developer, not the disclosure form. This stance is not isolated. Days earlier, the NetBSD project — which publicly rejected AI-generated code in 2024 — received over 20,000 in directed donations last month, more than double its 0,000 goal. Two open-source philosophies are now visibly diverging in 2026: Linux betting on 'the developer knows what they're doing,' NetBSD betting on 'keep the codebase clean.' ## His Own Claude Code Patches Just Got Flagged Had it been a pure principles statement, the ruling would not have drawn this much attention. The awkward point is that Torvalds happened to submit a kernel patch series this week that he authored himself using Anthropic's Claude Code — and reviewers have already found problems. The 10-patch series targets a long-standing bottleneck in the folio lookup mechanism. The core idea is to identify folios in a hot-data state, set a deferred-release flag, and release them only after an RCU grace period ends, while performing lookups and data accesses under RCU protection. Torvalds reported a 23x improvement on a synthetic benchmark, though he himself notes that real workloads will see far less. The trouble surfaced quickly: reviewers identified a race condition, and the memory reclamation path drew further scrutiny. The result was that Torvalds handed further development of the series to Kiryl Shutsemau — a kernel developer who had previously worked on the same bottleneck. That handoff is itself a telling signal: Linux's AI policy has loosened, but the code-review bar clearly has not. ## What This Means for Open-Source Governance Pulling the camera back from a single decision, the summit's conclusion touches at least three deeper tensions. The first is the boundary of disclosure obligations. Assisted-by was a lightweight disclosure mechanism rolled out across 2024–2025, designed to let reviewers know that a piece of code had been processed by an AI. Dropping it means AI traces become untrackable, raising the difficulty of assigning responsibility when something goes wrong. Some commenters have likened this directly to 'a cryptocurrency tumbler for intellectual property' — hard to trace inputs, with legal risk amplified. The second is the practical load of code review. Recent research suggests that productivity gains from LLM-authored code are frequently offset — or even reversed — by the extra review load. If removing disclosure results in a flood of AI-assisted patches, maintainers will not just be reviewing code, but also guessing at unseen conversations behind the diff. The third is copyright uncertainty. Linux uses GPLv2, but the copyright status of LLM-generated output is unsettled across jurisdictions. If a Claude Code output turns out to be substantially similar to something in its training data, the consequences could cascade. ## Linux Kernel's Next Move In the short term, the Linux 6.x development cadence will not change overnight because of this ruling — AI-assisted submissions were already happening, and the disclosure was a formality. The real test comes 12–18 months from now, when the kernel patch pipeline must absorb whatever new volume arrives without the Assisted-by filter. Torvalds handing his 10 Claude Code patches to a human developer offers a useful compromise template: AI can write, code can land, but review and landing stay human. This time he bet correctly that 'the developers know what they are doing.' The next time a maintainer faces an unlabeled AI-assisted patch and still has to identify the bug — that is the real cost of this loosening. Open-source governance has never been black and white. The Prague meeting's decision to prioritize 'trust the developer' over 'compliance form' is essentially a bet on responsibility allocation. The bill will not arrive on Linux 6.x; it will arrive with some future incident.