Claude Code stops cloning existing games under new Opus 5.5 rule
Updated: 11 minutes ago

Claude Code now declines to build a recreation of a specific existing video game when it runs on Claude Opus 5.5, after Anthropic added a short instruction to the coding agent's prompt. The new text tells the model it should not build "a recreation of a specific existing game, even if it is renamed or called original," while original games, games in an established genre and games built from the user's own designs and assets remain in scope.
Anthropic confirmed the change on October 30, 2026, when Addy Osmani, a member of Anthropic's technical staff who works on Claude Code, said in a post on X that the company had "added two sentences to Claude Code's prompt on Opus 5.5 to steer it away from recreating someone else's specific game." He tied the decision to the company's rules, writing that "using Claude to infringe IP is against our usage policy," and said that original games, genre games and games built from a developer's own design "are meant to keep working."
The rule was first noticed by users around October 27, before Anthropic commented, and it carries the internal identifier tengu_heron_brook. Anthropic has not published a help-center article or a changelog entry about it: the official Claude Code changelog, which lists releases up to version 2.1.311 of October 26, contains no item about games, recreations or intellectual property.
··········
HOW THE CLAUDE CODE GAME RECREATION RULE WORKS.
The change sits in the instructions that Claude Code sends to the model, which is a different mechanism from a separate classifier or an account-level block. Anthropic described it as two sentences added to the prompt used when Claude Code runs on Opus 5.5. The first sentence keeps the door open for original work, genre work and projects based on the user's own material. The second sentence closes it for a recreation of one specific existing game, and the wording anticipates the most obvious workaround by covering projects that are "renamed or called original."
Because the rule lives in the prompt, it works by shaping how the model responds, and it does not act as a hard technical filter on inputs or outputs. In practice Claude Code is expected to decline, or to steer the conversation elsewhere, when a request clearly asks it to reproduce a named commercial game, its levels, its characters or its distinctive mechanics as a whole. Requests that borrow a genre, such as a side-scrolling platformer, a deck-building roguelike or a tower defense game, are explicitly allowed by Anthropic's own description of the change.
Developers have described the rule as delivered from Anthropic's side, with no user setting to switch it off, and as behaving the same way across installations. Anthropic has not documented the delivery mechanism, so the exact scope of the change is known only from the company's own description and from what users have observed.
........
Date | Event | Source of the information |
Oct 26, 2026 | Latest changelog entry (v2.1.311), no mention of games | Official Claude Code changelog |
Around Oct 27, 2026 | Users notice the new instruction in Claude Code | Developer posts on X |
Oct 30, 2026 | Anthropic confirms two added sentences on Opus 5.5 | Addy Osmani, post on X |
Nov 12, 2026 | Updated Anthropic Usage Policy takes effect | Anthropic Usage Policy |
........
··········
WHAT CLAUDE CODE STILL BUILDS AND WHAT IT NOW DECLINES.
The boundary drawn by Anthropic is narrower than a ban on game development, which remains one of the most popular uses of AI coding agents. The distinction is between making something new inside a familiar category and rebuilding a particular product that already exists. A request for a puzzle game with falling blocks and a new scoring system belongs to the first group; a request to rebuild a named commercial puzzle game with its exact rules, layout and branding under a different title belongs to the second.
........
Request type | Status under the Opus 5.5 rule |
Original game concept | Allowed |
Game in an established genre | Allowed |
Game from the user's own design documents and assets | Allowed |
Recreation of a specific existing game | Declined |
Renamed recreation presented as original | Declined |
Licensed remake or port by a rights holder | Not addressed by Anthropic |
........
The last row is the one that leaves the most room for confusion. Anthropic's statement covers games "built from your own design," which suggests that a studio porting or remastering its own title should be able to proceed, but the company has not said how Claude Code is supposed to recognize that situation. Claude cannot check whether the person at the keyboard owns the rights to the game being discussed, and Anthropic has not described any verification step.
··········
THE ANTHROPIC USAGE POLICY BEHIND THE CLAUDE CODE CHANGE.
Osmani's explanation points to Anthropic's Usage Policy, which already prohibited this kind of use before the prompt change. In the section titled "Do Not Violate Applicable Laws or Engage in Illegal Activity," the policy forbids using Anthropic's products to "infringe, misappropriate, or violate the intellectual property rights of a third party." A separate clause, under the heading on fraudulent, abusive or predatory practices, prohibits users from submitting "AI-assisted work without proper permission or attribution."
The current version of the policy published by Anthropic carries an effective date of November 12, 2026, and it applies uniformly to people using Claude.ai and Claude Code, to developers and businesses using the API, to customers who access Claude through cloud providers or resellers, and to end users of products built on Claude. It also makes users responsible for the actions of agents they build or deploy, including actions taken through tools, browsers or connected systems, which covers an agentic coding tool like Claude Code.
The prompt change therefore restates a prohibition that already existed, moving it from the terms of service into the model's working instructions, so that Claude Code applies it during a session instead of leaving enforcement entirely to after-the-fact review of accounts. The policy text does not use the words "copyright" or "trademark" and contains no clause specific to video games, so the game rule is Anthropic's own interpretation of the general intellectual property clause for one category of software.
··········
[[ADPLUS_300x250_1]]
WHY ANTHROPIC ADDED THE RULE AFTER STEAM CLONE COMPLAINTS.
The timing follows weeks of complaints from game developers about AI-built copies appearing on Steam. Agentic coding tools have made it possible for a single person to produce a playable imitation of a commercial game in hours, and smaller studios have argued that public demos give copyists everything they need to replicate a game before its release.
One studio, Alliance Arts, cancelled the public demo of its upcoming Steam game Drunken Goddess Reflux because it feared the game could be copied with AI before launch. Other developers have asked Valve how it intends to stop clones from flooding the store. Anthropic has not linked its decision to any specific case, and Osmani's statement frames the change around the company's intellectual property rules, with no reference to any particular storefront.
Anthropic has said it will continue to iterate on the rule. Osmani invited developers whose legitimate projects are refused to contact him directly, which suggests the company expects false positives in the first weeks and plans to tune the wording based on reports.
··········
WHAT CHANGES FOR CLAUDE CODE USERS AND GAME DEVELOPERS.
The people affected are Claude Code users who run sessions on Claude Opus 5.5, whatever their subscription, since Anthropic described the change as part of the Claude Code prompt for that model and did not tie it to a plan. Anthropic has not said whether the same instruction applies when Claude Code runs on other models, and it has not said that anything changed in the Claude apps or in direct API calls, where developers write their own system prompts. The Usage Policy clause applies on every surface regardless. Plan access and session budgets for the tool itself are unchanged, and they are covered in our guide to Claude Code pricing, plan access and usage limits.
For developers working on original projects, the most reliable way to keep Claude Code productive is to describe the game in its own terms. A design document that sets out the core loop, the rules, the art direction and the progression system gives the model a clear signal that the project is new, and assets supplied by the developer fall inside the category that Anthropic explicitly protects. Referring to a commercial title as a reference for feel or difficulty is common practice in game design, but a request phrased as "rebuild this game" is now the kind of instruction the rule targets.
Studios that own the rights to an older title and want to remake or port it face the least clarity. Anthropic's wording favors them, because the work is built from their own design and assets, but the company has not documented how such a request should be framed or whether Claude Code will accept a statement of ownership. Teams in that position can expect to explain the context in the session and, if the agent still declines, to use the contact route Osmani offered.
Teams that run Claude Code inside game studios should also keep in mind the separate supply-chain incident of late October, when a malicious extension posing as Claude Code appeared in Cursor's marketplace, described in our report on the malicious Claude Code extension 2.1.313. Version numbers and extension publishers deserve the same attention as prompt rules when a tool has access to source code and production assets.
··········
CLAUDE CODE GAME RULE: CONFIRMED FACTS AND OPEN QUESTIONS.
Several elements are established by Anthropic's own statements and documents. Claude Code's prompt on Opus 5.5 now contains two sentences that allow original, genre and user-designed games and exclude recreations of a specific existing game, including renamed ones. Anthropic confirmed the change on October 30, 2026, linked it to the intellectual property clause of its Usage Policy, and said original and genre work should keep functioning. The Usage Policy that takes effect on November 12, 2026 applies to Claude Code, the Claude apps and the API alike.
Other points remain undocumented. Anthropic has not published the change in the Claude Code changelog or in a support article, has not said whether models other than Opus 5.5 receive the same instruction, and has not explained how licensed remakes, ports by rights holders, parodies or homages are treated. The rule also has evident technical limits: it relies on the model's judgment inside a session, it cannot verify ownership, and it has no effect on locally run open-weight models, which carry no comparable instruction.
For developers using Claude Code, the change narrows one specific use while leaving game development itself available, and the practical result will depend on how often the model misreads legitimate projects as copies. Anthropic's promise to keep adjusting the wording, and the direct contact offered for blocked work, indicate that the current text is a first version that the company expects to revise.
··········
FOLLOW US FOR MORE.
·····
DATA STUDIOS
·····
datastudios.org




