Banned Twice, Shipped Anyway: PewDiePie's Ajax Puts a 9B Uncensored Agent on Home PCs

Felix Kjellberg — the Swedish creator known to over 110 million subscribers as PewDiePie — has unveiled Ajax, a small language model built to run entirely on a home computer as an “always-on” personal AI agent. The launch, rolled out through his channel over the past few days and still trending across social platforms on October 4, comes with one of the stranger backstories in recent AI memory: Kjellberg says OpenAI suspended his account twice while he was building it, with an email displayed in his launch video citing “distillation” as the reason.

Ajax is a fine-tune of Alibaba’s open-weight Qwen3.5-9B, purpose-built for Odysseus, the free, open-source, self-hosted AI workspace Kjellberg launched in May 2026. Where frontier labs chase ever-larger trillion-parameter systems running in hyperscale datacenters, Ajax goes the other way: roughly nine billion parameters, tuned for agentic chores — web search, browsing, email, calendars, to-do lists — with all processing staying on the user’s own hardware.

What Ajax actually is

Strip away the celebrity and the controversy, and Ajax is a straightforward technical artifact: a fine-tuned Qwen3.5-9B checkpoint adapted to the tool-calling rhythms of the Odysseus environment. Odysseus itself has become one of the most-starred self-hosted AI projects on GitHub — a viral video this summer claimed it had crossed 80,000 stars — and it lets users wire local models into everyday workflows without routing data through a cloud provider.

The pitch is privacy plus control. An always-on agent that reads your inbox, watches your calendar, and browses on your behalf is exactly the kind of assistant people say they want — and exactly the kind most hesitate to hand a cloud API key to. Kjellberg’s argument, echoed across the r/singularity and r/technology threads where the launch went viral, is that everyday agentic tasks simply don’t need a frontier-sized model. A competent 9B model on a gaming PC can do the job, and the data never leaves the house.

One caveat worth stating plainly: at announcement time, the final hardware requirements, downloadable weights, and independent benchmark results for Ajax were not yet publicly available. The model is real and demonstrated on video, but third parties haven’t yet verified how it stacks up against the open-weights it derives from.

The two OpenAI bans

The backstory is what pushed Ajax beyond tech media into mainstream coverage. Kjellberg says that while developing the model, he wanted to use outputs from a larger AI model — OpenAI’s — to generate training material, a technique called knowledge distillation, where a small “student” model learns to reproduce capabilities of a larger “teacher.”

Distillation itself is a bog-standard machine learning method; OpenAI’s own documentation describes it as a legitimate way to build training data for smaller models. The friction is contractual. OpenAI’s Terms of Use prohibit using its outputs to develop competing models and bar automated or programmatic extraction from its services. According to Tom’s Hardware, Kjellberg showed an OpenAI email stating his account had been deactivated over “distillation”-related activity. He says the account was restored on appeal — then suspended a second time after he used the model to generate what he described as seed data for Ajax. OpenAI has not publicly commented on either action, so the record here rests on Kjellberg’s account and the email he displayed.

He has been blunt about the intent, joking publicly that he only wanted to “distill just a little bit.” Whether that confession triggers further action from OpenAI remains an open question.

“Abliterated,” not lawless

The other headline word — “uncensored” — deserves unpacking. The Ajax project describes its refusal behavior as having been “ablated.” Per Tom’s Hardware, Kjellberg used Heretic, an open-source tool that performs what the community calls “abliteration”: surgically suppressing a model’s refusal pathways while trying to leave its other capabilities intact.

This is not a blank check. Kjellberg says he retained boundaries around requests involving harm to oneself or others, and that on legal advice Ajax is not intended to dispense genuinely dangerous content. The goal, as he frames it, is a model that doesn’t lecture users or refuse benign-but-edgy requests — a common frustration with heavily aligned consumer chatbots — rather than one with no guardrails at all. Critics will note the line between “less preachy” and “genuinely risky” is exactly what independent testing should probe, once weights are actually released.

Why this matters more than the meme

It would be easy to file Ajax under internet spectacle — a YouTuber cosplaying as an AI lab. That would miss the point. Three currents converge here that the industry has been circling for a while:

First, small models are having a moment. As agent workloads exploded through 2026, the cost math of routing every email summary and calendar check through a frontier API stopped adding up. Sub-10B models — Aleph Alpha’s Kolibri, Ant’s Ling-3.1-flash, now Ajax — keep demonstrating that specialized, open-weight small models are often the right tool for agentic glue work.

Second, creators are becoming distribution channels for infrastructure. When Kjellberg launched Odysseus in May, he introduced self-hosted AI to an audience that would never read a Hacker News thread about llama.cpp. Ajax extends that funnel from “run someone else’s model” to “run this model, tuned for the job.” No lab marketing budget buys that reach.

Third, the distillation wars are heating up. OpenAI’s terms are clear, but enforcement against a high-profile individual — over a 9B fine-tune, not a frontier competitor — illustrates how fuzzy “competing model” has become in a world where everyone fine-tunes everyone’s open weights. If teachers’ outputs are off-limits, the open ecosystem’s favorite data strategy lives in a legal gray zone that every startup, researcher, and now creator, is navigating by trial and error.

The bottom line

Ajax is not a GPT-6.1-class event, and it isn’t meant to be. It’s a signal flare for where consumer AI sentiment is drifting: local, private, plausibly deniable, and owned by the person running it. The weights aren’t public yet, the benchmarks don’t exist yet, and “uncensored” is doing a lot of work in the coverage. But a creator with one of the largest audiences on the internet now has a working, self-hosted agent stack with his name on it — and two OpenAI ban notices as a marketing asset nobody could have scripted.

Watch what happens when the weights actually drop.