Anthropic adds server-side rule to keep Claude Code from recreating existing games
📅 October 30, 2026 • Source: Game Developer Anthropic has added a server-side rule to Claude Code that instructs the Opus 5.5 model not to recreate existing games. The rule reads: «Do build original games, games in a genre, and games from the user's own designs and assets. Do not build a recreation of a specific existing game, even if it is renamed or called original.» The change lands amid an…
On October 30, 2026, Anthropic introduced a new server-side rule for Claude Code model version 5.5, preventing the AI from reproducing existing games. The rule instructs the model to "build original games, games in a genre, and games from the user's own designs and assets" while explicitly forbidding "a recreation of a specific existing game, even if it is renamed or called original." This move comes amid a growing concern about AI-generated game clones that replicate the mechanics and visual style of independent releases.
The change was noticed on October 27 by user chasm on X and later confirmed by XDA in Claude Code v2.1.314's binary. There is no user-configurable way to disable the rule, ensuring consistent behavior across installations. Anthropic's technical staff member Addy Osmani confirmed the change, stating that the policy is in place due to their usage policy against IP infringement.
Original games, genre-based games, and projects built from the user's assets remain unaffected, and developers can reach out to Osmani if they encounter issues with their work.
The impact of this rule is twofold. For game studios, it lowers the risk of Claude Code being used to produce close copies of existing games. This concern was highlighted when Digital Sun canceled the public playtest of their game ReVamp due to fears of cloning. However, the rule also creates friction, as it blocks developers using Claude Code for licensed tabletop wargames and leaves some developers questioning the broadness of its wording.
Anthropic directs legitimate requests to their support team, providing a documented path for developers to seek clarification.
This incident demonstrates content policy enforcement at the prompt level within developer tooling, rather than just in terms-of-service documents. Notably, the change to Claude Code's behavior occurred without a local setting, and its discovery was made by users examining the binary rather than from a changelog. As tool behavior can change between versions due to server-side prompts, developers must now consider policy updates alongside functional updates when reviewing releases of coding agents.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
