Anthropic Updates Claude to Stop It Recreating Specific Video Games
Anthropic has updated Claude's instructions so that the model will not build a recreation of a specific existing video game. The change was released as an update to Opus 5.5 and applies to Claude Code, the company's coding tool, according to Game Developer.
The updated instructions tell Claude to build three kinds of project: original games, games within a genre, and games built from the user's own designs and assets. They also tell Claude not to build a recreation of a specific existing game, even if that game is renamed or presented as original, per Engadget.
Addy Osmani, a technical staff member at Anthropic, confirmed the change. He said the aim is to steer Claude away from recreating another person's specific game, and that using Claude to infringe intellectual property violates Anthropic's usage policy. Anthropic has also clarified that original games, genre games, and games made from a user's own designs and assets should be unaffected.
The line runs between a specific title and a category. A request for a platformer, a roguelike (a genre built around randomly generated levels and permanent death), or a tower defense game falls on the permitted side, as does a project built on a developer's own sprites (2D image assets), level data, and mechanics. A request to rebuild a particular published game, with its name changed or left in place, falls on the other side. The instructions are written to catch the second case regardless of how the request is framed, which is the part most likely to matter in practice.
In my view, the difficult question is the boundary, not the principle. Game mechanics are generally hard to protect, and a genre is a loose collection of shared conventions. A developer who asks for a clone of a well-known title with a few details changed is making a request the instructions now address directly, but the distance between 'a game like this' and 'this game, renamed' is a matter of degree. The update answers that question for Claude Code by stating that renaming does not change the outcome. How consistently the restriction is applied at the edges will only become visible through use.
The broader context here is that coding assistants are increasingly used to prototype playable software quickly, and games are an obvious case for that work. For a developer working on an original title, or building on their own assets, the change should leave the workflow intact. What it removes is a shortcut that relied on another studio's work, which is a narrower restriction than a blanket ban on game development.
