decomp.dev, the collaborative hub for game matching-decompilation projects, announced on October 16, 2026 that it will shut down its main index and new-project intake, leaving only historical project pages and read-only access to existing data. This was not a routine "project maintenance pause" — it was a farewell letter from the site's sole administrator, Encounter, to the idea of "open-source community doing reverse engineering by hand" after watching what GPT-6-Astra and its peers can do.

A retirement notice that took two years to write

In the statement, Encounter walks the timeline back to early 2026. Shortly after Opus 4.6 and GPT-5.4 shipped that year, the community noticed these models "appear to have been trained on matching decompilation — they knew how to use our toolchain without prompt engineering." Before that, the decomp circle had experimented with AI assistance using GPT-3.5 and Claude 1.x, with mixed results: it worked, but the per-task token cost was far higher than the human hours it saved, so it never really entered the community's workflow. Opus 4.6 and GPT-5.4 were the first models that made "AI-written decomp" economically plausible, but the output still required heavy human cleanup and fixes for obvious "cheating" code — code that compiles to the same machine code but could not reasonably be passed off as what the original developers wrote.

The real turning point came with GPT-6-Astra. Encounter's evaluation breaks into three layers.

The first layer is complex-instruction following and cross-source reference. Astra correctly understands what the decomp community wants from a permuter — write small scripts that enumerate many source forms and combinations, then match inlined helpers, signature changes, and operation ordering across files and headers, not just brute-force inside a single file. The second layer is long-horizon coherence. A decompilation project routinely spans hundreds of thousands of functions; the model can "stay on the rails" across that scale without drifting, something no previous AI-assisted decomp attempt had managed. The third layer is speed and cost. It works, and it is cheaper than the previous generation.

Stacking those three layers, Encounter writes the verdict: "It is now clear that, with the right guidance, human input, and code reviews, AI can expedite the decompilation process in a significant way. What is also now clear is that the community aspect of decompilation has been broken."

Three kinds of abuse, each dismantling a contract the open-source community depends on

The rest of the statement explains why the community can no longer hold together. Encounter lists three increasingly common forms of abuse, each one severing a basic contract that open-source collaboration relies on.

The first is hostile forks. The decomp community's open-source license allows anyone to fork existing projects, but Encounter points out that forks which then "finish" the project in one AI-fueled burst neither merge back upstream nor contribute anything to the original project — they just screenshot the progress number and post it on social media. "Some projects don't want AI used for legal or ethical reasons; others are fine with AI but don't want drive-by AI-spliced PRs." Either way, these forks do not constitute community contribution; they tear at the collaboration fabric.

The second is racing to PC ports. Decompilation is a research process about understanding how a game works, typically measured in years; building a PC port from already-decompiled source is a much smaller job. Encounter writes: "Now anyone with an AI subscription can manage to create a port or static recompilation that functions at a basic level." The problem is that these ports are mostly "half-baked, barely functional," but they ship much faster than the original decomp project. The result: "the people who actually spent years decompiling the game get beat to release by someone who AI-glued a port together in a month or two."

The third is conceptual conflation. For years the decomp community has tried to establish that "decompilation is not the same as porting" — decomp is research, port is consumption. Encounter directly calls out /r/decomps and the "sloptuber" crowd for long using "decomp" to mean "PC port," severely misleading newcomers about what decomp projects are, and making it harder and harder for upstream contributors to explain what they actually do.

Why Encounter chose "shut the index" rather than "ban AI"

One section of the statement directly answers the question "why not just forbid AI-assisted projects?" Encounter's answer is plain: he maintains the hobby project alone, has no energy to define what "good decompilation" means, and cannot enforce such a definition consistently across hundreds of projects. More importantly, he concedes that "AI itself is not the issue, and used correctly it helps tremendously." The issue is "slop," and slop comes in too many forms to enumerate; the definition keeps drifting.

This admission is the key to reading the whole statement. decomp.dev was not defeated by AI; it was crushed by AI on top of the contracts of community collaboration. Model capability is a neutral fact; whether a community can maintain the loop of "contribute → review → merge → attribution" under that capability is the real question. When "tokens burned into a number" starts replacing "real human contribution" as the metric of project progress, that loop breaks.

At the end of the statement Encounter also makes clear that decomp.dev's own code will not be open-sourced — any replica is forbidden from using it. He writes: "decomp.dev's repository has never had an open source license, and I continue to reserve all rights to the (entirely human written) code."

A boundary drawn for open-source collaboration

decomp.dev's shutdown should not be read as a simple "AI made one craft obsolete." A more accurate description: when a kind of work that originally relied on "slow + collaborative + attributed" to hold its value suddenly gets its cost compressed by "fast + solo + anonymous" capability, the open-source community built around it loses new contributors first, then loses its review mechanism, then loses its sense of belonging. Encounter shut down the main index early — in essence, stopping the already-warped "contribution game" before it rotted completely.

This is the first project in the 2026 open-source ecosystem to step down with an explicit "AI dismantled the community-collaboration model" rationale. The Linux kernel, AI bug bounty programs, and Hugging Face repositories have all shown early signals of the same pressure, but they are still responding by "adding people, adding review, adding process." decomp.dev went straight to the most drastic response — shutting down the site. That path will be copied by more projects; it is worth every maintainer thinking ahead about: when an abstract "collaboration" is replaced by a concrete "token count," which side are you trying to hold?

Key facts at a glance

  • decomp.dev launched in 2024, positioned as "a collaborative center + progress leaderboard for game matching decompilation."
  • Encounter says early 2026's Opus 4.6 and GPT-5.4 were the early signals of "being trained on decompilation specifically"; GPT-6-Astra was the final push that "ended" the community model.
  • The main index and new-project intake are closed; historical project pages and data continue to be served read-only.
  • decomp.dev's code carries no open-source license; all rights are reserved by Encounter; any replica is forbidden from using it.
  • Original statement: https://decomp.dev/ (Chinese summary via Solidot: https://www.solidot.org/story?sid=85638)