Anthropic has updated the Claude Code tool, specifically within the Opus 5.5 model, to block requests for recreating existing video games. This restriction is enforced via remote configuration, meaning developers may encounter refusals even if their local client remains unchanged. While the policy targets direct clones, even those renamed or disguised as original, it explicitly permits original projects, genre-based games, and technical tasks like decompilation or recompilation. Developers should focus on defining specific engineering requirements and original assets in their prompts to avoid triggering these intellectual property safeguards.
Anthropic confirmed on October 30, 2026, that it had added an instruction to Claude Code’s Opus 5.5 prompt discouraging recreations of specific existing games. Renaming the project or describing it as original does not remove that restriction.
Addy Osmani, a member of Anthropic’s technical staff, said the change reflects the company’s policy against using Claude to infringe intellectual property. Original games, games within established genres, and projects built from users’ own designs and assets are meant to remain supported, according to his statement, reported by Game Developer.
For developers, the important distinction is between making a game within a familiar genre and asking Claude to rebuild a particular title. The technical implementation also matters: this is prompt guidance delivered through Claude Code’s configuration mechanisms, so model behavior can change without a new game-development feature appearing in the interface.
What the New Game Rule Says
The restrictive sentence, reproduced by Game Developer, reads:
“Do not build a recreation of a specific existing game, even if it is renamed or called original.”
The accompanying instruction explicitly supports original games, genre games, and games based on users’ own designs and assets. Anthropic is therefore drawing a project-level boundary, not announcing a general ban on AI-assisted game development.
The renamed-game clause is consequential. It tells Claude to consider what the requested project recreates, even when its title or description changes. A request to reproduce a particular game under a different name falls within the instruction’s stated restriction.
Osmani framed the change as IP-policy enforcement. That is Anthropic’s explanation for the rule, not a legal finding that every recreation infringes someone’s rights. The published instruction does not spell out jurisdiction-specific copyright rules or a detailed process for assessing licenses and permissions.
Game Developer reported that an Anthropic spokesperson directed it to Osmani’s statement. The confirmation available here comes through that statement and reporting, rather than a standalone Anthropic technical changelog.
My reading is that developers should treat this as a change in what Claude is instructed to help build, not evidence that its underlying programming abilities have changed. A refusal can now reflect the model’s interpretation of the project’s identity.
How Claude Code Receives the Instruction
XDA’s examination of Claude Code provides the clearest published account of the implementation. The outlet reported finding the instruction inside version 2.1.314 of the Claude Code executable.
XDA identified two relevant delivery mechanisms:
tengu_heron_brook: A remote configuration field used for adjustable system instructions. XDA found evidence that Anthropic had previously used it for an unrelated instruction about reasoning effort, so the mechanism is not specific to games.
original_games_guidance and opus_5_5_prompt_bundle: A separate mechanism that, in XDA’s analysis, allows the game instruction to reach Opus 5.5 independently.
That distinction affects scope. XDA reported that accounts receiving the instruction through the first mechanism could have it applied across models used in Claude Code. The separate Opus 5.5 mechanism suggests that the model can receive the guidance without relying on that account-level route.
Finding text in an executable is not proof that every session receives it. XDA said the instruction was absent from its test account’s ~/.claude.json file despite being present in the installed binary. The report leaves the full rollout, application to other models, and permanence unresolved.
The practical implication is that a local configuration file is an incomplete picture of Claude Code’s behavior. Developers investigating a changed refusal should distinguish the installed client version, the selected model, and remotely supplied instructions. Those are separate variables, even when the visible symptom is simply that a previously accepted request gets turned down.
Reverse Engineering Is a Separate Question
XDA’s reported tests complicate the idea that this is a blanket prohibition on game ports or reverse engineering.
When asked to recreate Pokémon Diamond, Opus 5.5 refused and referred to session instructions against recreating specific existing games. But when XDA asked about a decompilation project for the same game, the model agreed to assist. It offered help translating disassembled functions into readable C, rebuilding a ROM from a user’s own copy, and developing project tools.
Those tasks differ technically:
Workflow
What It Involves
What XDA Reported
Recreation
Building a new implementation of a specific existing game
Opus 5.5 refused the Pokémon Diamond recreation request
Decompilation
Recovering higher-level code from compiled machine instructions
Opus 5.5 offered assistance with the requested project
Static recompilation
Translating existing executable instructions ahead of execution for another target
Opus 5.5 outlined a possible Windows implementation
For the static-recompilation request, XDA said the model proposed an Arm-to-C recompiler, support for Nintendo DS overlays, and a runtime handling graphics, audio, and other hardware functions. That is a different technical undertaking from asking a coding agent to reproduce a game’s design from scratch.
These were XDA’s request-level tests, not tests conducted for this article. They show willingness to discuss or assist with particular tasks, not completion of a working port, a legal assessment, or a measured false-refusal rate.
I would keep this distinction explicit in a development brief. If the task is translating a function, documenting a file format, or implementing a hardware interface, describe that actual engineering work. Precise scope helps separate a legitimate technical request from a broad request to rebuild a named game. It is not a guarantee of acceptance.
What Developers Should Put in Their Briefs
Anthropic’s stated allowances give developers a useful starting point, although they are not a detailed specification of every permitted project.
Project Type
How It Relates to the Stated Rule
An original game with a new design
Explicitly intended to remain supported
A game in an established genre
Explicitly intended to remain supported
A project using the developer’s own designs and assets
Explicitly intended to remain supported
A recreation of a named existing game with a new title
Explicitly targeted by the restriction
A decompilation or recompilation project
Not explicitly prohibited by the quoted rule; XDA reported assistance in limited tests
A useful brief should explain the game’s mechanics, progression, assets, and technical requirements in their own terms. If the project is yours, identifying the designs and assets you control provides relevant context. It also produces a clearer specification than asking for an existing title with cosmetic changes.
Genre references still have a role. A platformer, deck-building game, or turn-based strategy project can share broad conventions with other games while having its own rules, levels, presentation, and content. Anthropic explicitly says genre games are intended uses, but its short instruction leaves the boundary between genre inspiration and specific recreation open to interpretation.
That ambiguity is the main practical risk for original developers. Osmani invited users whose own projects were refused to send those cases to him, according to Game Developer. His invitation provides a route for reporting problems; it does not establish how frequently those problems occur.
The Rule’s Reach Stops at Claude Code
The change arrives amid documented concern about AI-assisted game copying. Dexerto reported that Alliance Arts canceled the public demo for Drunken Goddess Reflux over concerns that AI could be used to imitate its presentation and gameplay. That example shows why developers care about fast recreations, but it does not prove that this incident caused Anthropic’s decision.
A prompt instruction can steer a coding assistant’s responses. It cannot verify every ownership claim, inspect every competing tool, or enforce a distribution platform’s rules. The published material describes no ownership-verification procedure that would resolve those questions automatically.
Game Developer also noted that developers could turn to open-weight models without the same restrictions. That limits the reach of Anthropic’s intervention, although it says nothing about whether a particular alternative would successfully complete the work.
The clearest benefit is narrower: Claude Code now has an explicit instruction against helping recreate someone else’s specific game. For original developers, the useful next step is to keep project ownership and engineering scope clear, and to document refusals that conflict with Anthropic’s stated allowances.
Frequently Asked Questions
4 questions
1
Can Claude Code Still Help Make Original Games?
Yes. Anthropic says original games, genre games, and games built from users’ own designs and assets are intended to remain supported.
2
Does Renaming an Existing Game Avoid the Rule?
No. The instruction explicitly covers recreations that are renamed or described as original.
3
Are Decompilation and Game Ports Banned?
The quoted instruction does not explicitly prohibit all such work. XDA reported that Opus 5.5 offered assistance with specific decompilation and static-recompilation requests, but those exchanges did not demonstrate completed projects.
4
Does the Rule Apply to Every Claude Model?
The full rollout remains unclear. Anthropic confirmed the Opus 5.5 prompt change, while XDA identified a separate configuration route that could apply the instruction across models on accounts receiving it.
