Developers asking Claude Code to recreate an existing game now face an explicit restriction from Anthropic, even as the company says original games should remain supported. The difficult question is where the assistant draws that boundary when someone is adapting a game they already own.
Addy Osmani, a member of Anthropic’s technical staff, confirmed on October 30 that the company had added two sentences to Claude Code’s prompt on Opus 5.5. He said the aim was to steer it away from recreating someone else’s specific game because using Claude to infringe intellectual property breaches the company’s usage policy.
Original games, genre games and projects built from a user’s own designs and assets are meant to keep working, Osmani said. His explanation describes a restriction on a particular coding workflow, not evidence that every Claude product now rejects every game-related task.
The change, covered by Engadget on November 1, leaves developers with a practical distinction: asking for a new game within a genre is supposed to remain possible, while recreating a particular existing title is not. Calling the result original or changing its name does not, according to the reported instruction, remove the restriction.
A complaint in Anthropic’s own Claude Code issue tracker shows why that distinction matters. The reporter, posting as lerugray and identifying themselves as the operator of Conflict Simulations LLC, said the tool had refused commissioned work on personalized digital modules of board wargames. The account said clients owned the physical games and supplied the materials, while the software code was written from scratch.
That account also contains an important correction. The reporter initially described the work as licensed, then withdrew that description and stated that the modules were not publisher-licensed. Ownership of a physical game and permission from its publisher are different facts. The complaint therefore should not be presented as proof that Anthropic blocked an officially authorized adaptation.
The reporter said existing sessions continued working after the instruction reportedly arrived around October 27, but began refusing the projects after being asked whether the new rule applied. Those are the user’s observations, not an independently reproduced test. They illustrate a disputed workflow rather than establish how often the restriction misfires across Claude Code.
The requested remedies were specific: narrow the instruction to actual infringement, offer a verification route for commissioned professional work, and document substantial server-delivered changes in the changelog. The account said the builds were for clients’ own use rather than public distribution. Anthropic’s short public explanation does not resolve that particular case.
The distinction between a product refusal and a legal finding remains essential. Claude rejecting a request does not establish that a court would find the proposed project unlawful. Equally, a user’s claim that a project is private or uses newly written code does not, on its own, establish permission to reproduce someone else’s game.
Nor does the confirmed game-cloning instruction establish a blanket prohibition on reverse engineering, security research or modding. Those are broader categories than the specific-game recreation Osmani described. Claims about them require separate evidence rather than being folded into the announcement.
For developers, the immediate uncertainty is operational: a project can be interrupted by a provider’s instruction without a change to the developer’s own files. For Anthropic, the stated objective is to prevent infringement while preserving original development. The unresolved case is the customer who says the work is theirs, but whose request still resembles a recreation to the assistant.
