Open Source Subreddit Bans AI: ‘Tokens Are Cheap’ Rationale

Open Source Subreddit Bans AI: 'Tokens Are Cheap' Rationale

I watched the r/opensource moderators publish a rule and the thread went quiet. You felt the room tilt—an old alliance fraying around a single sentence. The moderator closed the distance with: “AI, as it exists today, is incongruent to this Open Source community.”

I’m writing from inside that rupture. I’ve followed these communities long enough to know when a policy is a symptom, not just a rule. If you care about code and culture, this matters.

On Saturday a moderator posted a policy change and the subreddit shifted.

Wolvereness, a lead moderator on r/opensource, didn’t bury this decision in bureaucracy. The new rules are blunt: projects that use, are made by, or are intended for AI are unwelcome. That last clause reaches past models and into human work that shapes model prompts and model context protocols (MCPs).

The headline line—“Tokens are cheap, and we don’t care how many you spent to make your amazing project”—is deliberately provocative. It reduces a complex, shifting technical economy to a cultural judgment: cheap compute equals cheap craftsmanship. You can feel the authority in that voice; it’s both shield and faucet.

At 10 a.m. the moderation log showed more than an edit—it showed a schism.

This isn’t just a ban. It’s a declaration of identity: open source here is the pre-AI idea of openness. Moderators added other filters too—no projects under a year old, no accounts under a year old, and English-only posts. The rules read as if the community is building a moat.

Why did r/opensource ban AI?

Because for these moderators AI isn’t a tool; it’s a force that changes authorship, provenance, and trust. When models can rewrite binaries into readable code or generate entire projects from prompts, the old heuristics for “open source” provenance break down. You can call that protectionism, preservation, or panic—each reaction reveals what the community values.

On the developer timeline some of the most venerable projects now use AI in their workflow.

Linus Torvalds, for example, publicly said he used Claude Code to write a Linux kernel patch earlier this month. That’s not fringe: GitHub Copilot, VS Code extensions, and model-assisted patching are woven into many codebases. When a movement’s icons engage with a technology, a ban becomes an outlier stance.

Which projects are affected?

Anything that received AI-generated contributions or that was iteratively refined by models could be excluded. That includes code, prompts, and MCPs designed to make models behave. You can list names—Linux, Chromium, Firefox, Visual Studio Code, Python, Docker—but the practical effect is broader: if a repository contains traceable AI work, it risks being off-topic in r/opensource.

At a keyboard in a basement, hobbyists are using consumer AI to reverse engineer binaries.

Decompilation by prompting has become a new skill. Users feed models published machine-readable code and ask for a human-readable reconstruction. That process can produce projects like ArtCraft—a reimagined version of Adobe Creative Suite—hosted on GitHub and labeled open source. In the eyes of r/opensource moderators, those projects break the community’s norms, even if they claim legal clean-room status.

On the other side, a new subreddit appeared within hours.

r/TrueOpenSource was born as a refuge for those who want AI-friendly workflows. Wolvereness even gave a shout-out to that creator in an edit—acknowledging the split. That’s the modern internet: policy pushes people into new spaces and those spaces quickly crystallize around different values.

Can AI contributions be considered open source?

That’s the sticky question. If you write a patch with the help of a model, who is the author? If you design an MCP to coax a model into specific outputs, is that code or a prompt? Platforms like GitHub and projects like GitLab are still writing the social contracts that answer this. You and I will have to live inside those answers and contest them when they feel wrong.

The AI Brief
A daily briefing on the AI news you need to know to start your day. Written by humans. Envied by bots.
Subscribe Now

I’ve seen communities close ranks before and I’ve seen them remake themselves. This feels like both: a preservationist impulse and a cultural bet. If you’re in open source, you’ll choose a side, move your projects, or argue until the moderators change their minds—but how far will the split run before the movement redefines itself?