Every hobby a compiler can grade is about to go the way of decomp.dev

On 15 October 2026, decomp.dev stopped accepting new projects. The site tracked volunteer efforts to turn commercial video games back into readable, compilable source code. Its pseudonymous admin, Encounter, whom Aftermath identifies as Luke Street, wrote that the community side of decompilation had been broken by AI. Existing project pages and historical data stay online. The main directory and new registrations are blocked. I first filed this as a niche story about retro gaming. Then I read his timeline of which models changed what, and I now think it is the clearest early example of what agentic tooling does to expert hobbies.

Start with how matching decompilation works, because the mechanism explains everything. The goal is C code that, run through the game’s original compiler, reproduces the shipped machine code byte for byte. Every attempt gets a pass or fail from the compiler. For humans this made the work a grind measured, in Encounter’s words, on the scale of years for a moderately sized game. For an agent it is close to ideal: a loop with a perfect, tireless referee. The Gran Turismo 4 project on GitHub, maintained by Gustavo Canepa, says outright that Anthropic’s Claude does the bulk of the matching, and that each function is verified by the compiler and the judge, never by eye.

The timing in Encounter’s statement is specific. Before this year, AI output needed heavy human cleanup and fixes for cheating, and the cost per task was prohibitive for what it produced. Earlier in 2026, Opus 4.6 and GPT-5.4 started handling matching decompilation tools without separate explanations. GPT-6-Astra, public since 4 September, follows complex instructions and cross-references symbol and debug information on its own. Six weeks after that release, the site closed its index. Time Extension reports AI decomp projects have blown up tremendously over the past 12 months.

The sceptical reading deserves a fair hearing, and the evidence for it is good. The practitioner macabeus spent a year studying the problem and building tooling, and his headline result was 51% of Klonoa: Empire of Dreams, a 2001 Game Boy Advance game. Retro Reversing describes the leading N64 decomp agent as working against an existing decompilation project, without discovering the layout of an arbitrary ROM by itself. Encounter himself said the site had no quarrel with AI or porting. He blamed hostile forks: people who clone a long-running human-led project, finish it with AI, and ship ports without engaging the community.

I think every one of those points makes the hobbyists’ position worse. The hostile fork is what dependence on human scaffolding looks like in practice. Volunteers spend years mapping a game’s structure, naming symbols and building tools. Someone copies the repository, points an agent at the remaining functions, and releases the result. The expertise was needed, once, as input. Its holders lose the leverage that came from being the only people who could finish the job. Macabeus’s year of tooling work is the same story at a slower pace: the hard part is building the harness, and a harness gets reused.

The community also measured itself in a way that rewarded exactly what agents do best. Matrix News reports that the leaderboard became a hollow numbers game, with people chasing percentages over quality. A completion percentage is the compiler’s verdict summed up. Once a model can raise it overnight, ranking projects by it stops telling you who did the work, and Encounter said he could no longer tell which projects were human-led.

So which hobbies are next? My guess is any volunteer craft where a machine can check the output: emulator accuracy work tested against known results, translation patches that must assemble and boot, ports that must pass the original’s behaviour. Work judged by taste, such as level design or pixel art, has no automatic referee for an agent to loop against, so I expect it to hold out longer. I cannot tell you decomp.dev was the first community to fold this way; nobody I have read has checked.

If you maintain a long-running reverse-engineering repository, open its fork list this week, sort by most recently updated, and look for forks with a sudden burst of commits from one account. That is what an agent finishing your work looks like, and if your licence and credit requirements are not written into the repository yet, the person running it owes you nothing.

Prompted by Video Game Reverse Engineering Community Shuts Down Because AI Has Made It Too Easy, 404media.co.