Anthropic Restricts Claude Code From Recreating Existing Games Amid Copyright Concerns

Anthropic has added instructions to Claude Code that steer Opus 5.5 away from recreating specific existing video games, while still permitting original games, genre-based projects, and user-owned designs and assets. The change was spotted by users in a Claude Code rule identified as “tengu_heron_brook,” which says the system should not build a recreation of a specific existing game even when the project is renamed or described as original.

The rule was reportedly added around October 27 and cannot be disabled through the user interface, according to user Chasm, whose post helped draw attention to the change. Anthropic’s intervention follows a recent surge in AI-assisted game clones and remakes, including projects created for experimentation, commercial purposes, and rapid prototyping.

Claude Code remains available for building games from scratch, designing projects within a genre, and implementing ideas based on a developer’s own concepts and assets. That distinction gives users room to create platformers, role-playing games, puzzle games, and other familiar formats without asking the model to reproduce a named title’s specific identity.

The boundary becomes harder to apply when a developer wants to recreate a game for compatibility testing, preservation, education, or work on a project they own. GameDev.net described the update as a clearer limit on rapid cloning of existing mechanics, layouts, or presentation styles. A separate account said developers have encountered refusals during reverse-engineering and troubleshooting tasks, including work involving the Reverse Engineer Anything tool.

Anthropic member of technical staff Addy Osmani said the company added 2 sentences to Claude Code’s Opus 5.5 prompt to steer it away from recreating someone else’s specific game. Osmani tied the change to Anthropic’s usage policy, saying the use of Claude to infringe intellectual property violates those rules.

That explanation frames the restriction as a policy enforcement measure rather than a general ban on game development. The wording targets a specific existing game, including attempts to disguise a remake by changing its name or calling it original. The approach places part of the copyright and authorization screening directly inside the coding assistant’s behavior, where the model must interpret a user’s intent before generating code.

The restriction has created friction because the same technical methods used for unauthorized cloning also serve legitimate development work. Reverse-engineering can support ports, interoperability, debugging, preservation, and analysis of software a developer has permission to inspect. A refusal based on the game’s identity or the wording of a request can block tasks that don't involve publishing an infringing remake.

Superpowerdaily highlighted the difficult distinction between owning a copy of a game, writing fresh code, and having permission to reproduce the game itself. User complaints described Claude refusing some work on developers’ own projects and basic troubleshooting tasks. Reports linking the rule to concerns about AI-cracked titles and threats to clone unfinished game demos add pressure to Anthropic’s decision, but the reported refusals also show how a broad model instruction can affect authorized users.

Anthropic’s change reflects a growing conflict between rapid AI development and established intellectual property boundaries in games. Coding assistants can generate large amounts of implementation work quickly, making it easier to reproduce recognizable mechanics, interfaces, levels, and visual structures before a rights holder can respond. Reports of threatened demo cloning have made that risk more immediate for small studios with limited legal and engineering resources.

The update also gives developers a clearer signal about how major AI providers are handling high-risk creative tasks. Anthropic is allowing broad category-level creation while drawing a line at direct recreation of a named work. That standard will still require judgment, since games often share mechanics and genres, and the rule does not by itself resolve questions about ownership, permission, fair use, or reverse-engineering rights.

Claude Code users will need to describe projects through original designs, owned assets, and general genre goals rather than requesting a direct remake of a particular game. Developers working on ports, compatibility, preservation, or authorized analysis may need to provide clearer context, use different tools, or seek a policy clarification from Anthropic.

The immediate question is how consistently the restriction will distinguish infringement from legitimate technical work. Anthropic has publicly explained the prompt change through Osmani’s statement, while user reports continue to describe broader refusals involving reverse-engineering and troubleshooting. Future revisions will determine whether the company keeps the rule narrowly focused on cloning or adds exceptions and verification paths for authorized developers.