AI game decompilation, customization and the executable boundary

Brief and findings, October 6, 2026. An October 6 Stratechery Update argues that inexpensive game reconstruction will matter less as a way to reissue old games than as a way to create games and interfaces customized to one person; service games and hosted-only code may retain the publisher’s control. A good evaluation distinguishes reconstructing code from authoring a lookalike, interim copies from redistributed output, executable access from licensed assets, and a first playable build from retained use and maintenance. These distinctions bear on the personal agent interface and the prototype/production boundary.

Subquestion 1 — what was built? Thompson correctly separates First’s new Fallout-like browser game from source reconstruction: its creator’s September 28 account describes the agent-studio workflow, a drowned-world regression that forced rollback and a new terrain gate, plus unresolved player-return evidence. The Halo decompilation repository calls itself work in progress at a claimed 99.5% byte match, forks an earlier effort and links several ports; a native cross-platform port requires users to provide their own Xbox disc image for game data and calls Custom Edition maps experimental. The September 29 browser-port announcement describes up to 128-player support as untested at that size; this is not evidence one person decompiled a complete game instantly with a model, nor that 128-player sessions worked. A repository history is a multi-contributor software artifact, not an LLM-only benchmark.

Subquestion 2 — the longer agent-workflow trace. In Maurice Heumann’s August 17 original, three Claude workers and an overseer using Discord, GitHub issues and commit-triggered reviews spent four weeks on MW2 and had reconstructed 5,588 of 16,324 inventoried functions; the executable launched but maps did not yet load. The author said agents deferred hard subsystems, a giant shared status file became unworkable, and he separated mechanical reconstruction from portability/refactoring. His August 22 session-log audit measured duplicate large-file reads among subagents and turned them off; commits/day is a poor quality or outcome endpoint. In a separate September 30 public update, Heumann claimed a now-playable game and 17 simultaneous agents; those are later creator claims about a changing project, not a finding supported by the August snapshot or an independent gameplay audit. The two old blog URLs returned HTTP 404 on October 6 while search indexes still preserved the original text; their removal cannot be assigned a cause from that observation.

Subquestion 3 — US rights without a blanket answer. The Ninth Circuit’s Sega v. Accolade opinion and Sony v. Connectix opinion protect specific intermediate copying to learn unprotected functional elements for separately authored compatible games/emulator; they do not decide the permissibility of publishing a reconstructed game, nor confer an open-source license. Separate assets, marks, contract and technological-measure questions remain; 17 U.S.C. §1201(f) addresses a narrow interoperability circumstance rather than all circumvention. Thompson’s prediction that personal tinkering can occur without a publisher noticing is distinct from a legal exemption. Treat any recommendation on a specific project as requiring legal counsel, not this note.

Subquestion 4 — economic inference and gaps. The causal business-model chain is a hypothesis: desktop executables expose a reconstruction target whereas cloud-only executables do not; a live game’s server, identity, rights and distribution channels can still constrain customization. Fallout’s creator lost the public route after saying ZeniMax objected, while Halo’s nonbrowser native port relies on separately supplied game data. None of these three records pairs creator/agent and human attention, a lawful distribution arrangement, repeat players, customer-confirmed value or 30-day fixes for the same game. Stratechery extrapolates supply growth to more individualized play; player retention and viable franchises remain unmeasured.

Source list and disagreements. Received the full October 6 subscriber feed item (public page shows only a teaser); checked its game examples against First’s original, Halo source, native-port README, Heumann’s August report, audit (now inaccessible directly), and the two court opinions. The author’s 17-agent MW2 account describes September progress, not the August four-agent partial build; First’s browser game did not reverse engineer Fallout; Halo's code repository advertises incomplete byte matching and separate data. Court decisions are about interoperability copies, so do not collapse them into a verdict on a new game built to mimic protected expression.

Next inquiry. Look for one creator-controlled, licensed game with documented player-request→agent change→independent playtest→month-later return, human minutes, and a live-service access policy; absent that, keep distribution and personalization as open questions. A separate creator essay earns a weekday post when the queue clears; Heumann’s original post is a shorter but now inaccessible historical alternative.