Claude Code Won't Recreate Existing Games: Anthropic Confirms Rule
Anthropic confirmed Claude Code on Opus 5.5 now refuses to recreate specific existing games. What changed, what still works, and why indie devs care.
If you've been asking Claude Code to "make me a game like..." and getting stonewalled lately, it's not your imagination. Anthropic confirmed on Friday, October 30 that it added a rule telling Claude Code not to recreate a specific existing game, even if you rename it or call it original. Here's what changed, what still works, and why indie devs are paying attention.
What changed in Claude Code
- The rule: users spotted a new line in Claude Code's built-in rules reading "Do not build a recreation of a specific existing game, even if it is renamed or called original," per Game Developer.
- When: it was reportedly pushed around Tuesday, October 27, and users say it can't be switched off.
- Which model: Anthropic says the change applies to Claude Code's prompt when running Opus 5.5.
- Confirmed: an Anthropic spokesperson pointed Game Developer to a post from staffer Addy Osmani, who said the company added "two sentences" to steer Claude away from recreating someone else's specific game.
- Why: Osmani said using Claude to infringe IP is against Anthropic's usage policy.
What still works, and what people say broke
Per Osmani, original games, genre games and games built from your own designs and assets "are meant to keep working." So a roguelike, a cozy farming sim or a Metroidvania is fine. A pixel-perfect copy of a specific hit with a new name is not. He also asked people to send him cases where Claude refuses work that's actually theirs, and said Anthropic will "continue to iterate."
That's the official line. On the ground, Tom's Hardware rounded up user reports of Claude Code refusing things that sound legit: replicating a single mechanic, anti-cheat work on a dev's own game, and some general reverse-engineering jobs. Those are user claims, not confirmed by Anthropic, but they're the kind of edge cases a blunt rule tends to catch.
Why this is happening now
The timing isn't random. Over the past few weeks, AI-cloning fears have hit indie devs hard. Studios have pulled or delayed public playtests over worries that someone could clone a build and beat them to market, and Valve addressed AI cloning threats during Steam Next Fest. Add the AI decompilation wave that put classic games in browser tabs, and the pressure on AI companies was obvious.
The 2nd Shift take
Good call, imperfect tool. Nobody building something original loses anything from a rule against copying a specific game, and indie devs scared to post a demo deserve some backup. But let's not pretend it stops determined cloners. Jailbreaks exist, open-weight models have no such rule, and Claude can't actually tell whether you own the game you're describing. The real test is the false positives: if solo devs get blocked prototyping their own mechanics, that's a tax on the exact people this is meant to protect. Watch how fast Anthropic tunes it.
Building your own game or content with AI? Take the CRAFTR Quiz to find your creator type, then tell us in the 2nd Shift Discord whether Claude has blocked anything of yours.
Keep reading: AI Game Decompilation: Browser Ports, Pokémon and the Claude 'Nerf' and Valve on Steam AI Clones: No New Rules, Report Threats.
Sources: Game Developer, Tom's Hardware, PC Guide.
The week's biggest games, releases and fixes in one email. Free, once a week.