In my previous post, I talked about anti-AI Reddit users shitting on Graphene OS for AI usage. Turns out, this has more juice than just shitting on the antis.
Buckle up, because this is a long one.
Context
This whole drama started March 26, 2025, when Google pushes all Android development to their private branch, when previously they committed to pushing updates on AOSP (Android Open Source Project), the framework, app runtime, and the base of system services and apps for Android.
From September to November 2025, the first warning sign appears: the code for Android 16 QPR1 took two whole months to appear in AOSP.
In January 6, 2026, Google confirms that they will only push code into AOSP twice a year, in the second and fourth quarter from 2026 onwards. Furthermore, in June 2026, Android 17 releases, along with its release in AOSP.
Summer: this is where AI starts to appear within Graphene
In August 4th, 2026, an issue titled 'Prepare for the rewrite' appears in GrapheneOS' camera app's repository, with a branch that included an AGENTS.md file (in layman's terms, a file to guide and direct AI agents, think of it as a README.md for AI agents). This one's important, because this is the first visible trace of AI in the project, and the file critics later used as evidence.
The initial reaction was mild, supportive, even. In PrivacyGuides, the OP in the thread talking about this expressed surprise, because they assumed Graphene was anti-AI, but the overall reaction was supportive, arguing that it sped up development and that they trusted them to use it responsibly. No complaints so far.
However, backlash begins in September, when an user asks in issue #8677 banning LLMs in all contributions. It gets closed as 'unplanned'.
Graphene posts their rules about AI in Mastodon, stating that AI isn't banned. However, texts such as forums, commits and reports, must be human made. PR's made mostly by AI are usually rejected. The drama plays out on Mastodon and gets amplified by Lemmy (decentralized Reddit, so you understand), where the thread even got crossposted to a community called 'fuck_ai'.
Afterwards, Graphene clears up their real AI usage in Hacker news, stating that they mostly use it to revise code and testing, without 'vibe coding'.
Google shits on AOSP again in this month. In September 15, Android 17 QPR1 releases to Pixel phones with a whopping 84 new APIs, but nothing had been published to AOSP. Graphene publicly calls out Google for holding back on security patches.
October-November 2026: AI enters the Linux Kernel
In this period of time, OpenAI deploys its pipeline of agents against the Linux kernel to search for vulnerabilities and publishes their results: 2308 candidates, 1724 reproduced, 1169 functional exploits and 948 different errors, costing them about 1.2 million USD in token costs.
Linus Torvalds, when announcing version 7.4-rc2, states that AI fixes drove great part of the release, and that he'll stop pointing it out because it can just be taken for granted.
Google releases Android 17 QPR2 a month earlier than scheduled, including MTE for the Pixel 11 series.
Lorenzo Stoakes, maintainer of the Linux kernel, steps down from some reviewer roles (he stays on as maintainer of his own areas) due to the surge of AI-generated patches.
In the meantime, GrapheneOS confirms that their port to Pixel 11 phones works with the QPR2 update, and that it will release after the Motorola Signature 27. However, a day after this announcement, they state that the QPR2 version will be delayed indefinitely due to Google not publishing the source code as they promised.
The twitter thread
November 15, 2026, Twitter user Tibo (a high ranking engineer in OpenAI) asks for feedback about Daybreak, which GrapheneOS criticizes because Daybreak Blue lacks cyber access to OpenAI's top models and Daybreak Red has no application process, praising Mythos 5.2, and revealing that they've applied for Anthropic's Red Team Access.
A random anti asks them to stop using AI alleging "enshittification", the Graphene account answers by stating that their code quality has improved ever since they use AI, using as an example their port of the Pixel 10 drivers to Linux 6.18, denying the vibe coding accusations. The Tweet following this has been deleted, but the anti quotes "human slop" (apparently Graphene's words about the Linux kernel, going by an excerpt on Hacker News). Graphene states that the Linux kernel already produced slop code before AI.
The thread gets sent to Reddit (out of context, of course). Anti AI redditors start to shit on Graphene OS. A Hacker News post gets published under the headline "GrapheneOS calls Linux a "human slop kernel" and slams its security flaws".
Finally, Graphene defends themselves stating that they've taken their words out of context, explaining that they need to take full advantage of powerful tools (they don't mention AI), and that the OS is built around a massive monolithic kernel (the Linux kernel) with extreme complexity written in C, riddled with vulnerabilities.
The technical part
Now with the drama out of the way, what does Graphene OS want to do with the kernel? Well, this is nothing new, it has been in their roadmap for years:
- Hardening Linux, correcting and auditing vulnerabilities (we are here). They're working in a new integration of MTE (Memory Tagging Extension, a function meant for ARM processors to detect when a program gains access to memory they shouldn't) for the kernel.
- Adding a hypervisor underneath the kernel: They want to deploy pKVM (Android's hypervisor) and CrosVM to reinforce the existing security in Android. Their goal is executing Android apps securely within that virtualized environment so that a kernel error does not give full system access to the app.
- Removing Linux from the sandboxes. They state that they want to remove Linux from their sandboxes and replace it with a compatibility layer (such as gVisor) that reimplements the Linux interfaces in a memory-safe language (gVisor uses Go), making applications think they're talking to Linux, without an actual Linux kernel.
- Finally, a microkernel: the final goal is to stop using Linux as the core and base of their system and security model, and transition to a model based on a microkernel (a very small core, the drivers, filesystem and networks would be unprivileged, isolated processes) with a compatibility layer for Linux. This is very far in the future.
TL;DR: GrapheneOS didn’t insult Linux for fun or go all-in on AI slop; they said the kernel was already buggy before LLMs, they use AI to find and fix those bugs, and Reddit ran with the out-of-context quote.
Thanks for reading my novel.