Anthropic is right to stop Claude Code from rebuilding other people’s games. The rule is fair. What it lacks is a clear way to fix a wrong refusal, and that part needs work fast.
Claude Code picked up the rule around October 27, and Anthropic confirmed it on October 30. Below we cover what changed, why we think it’s the right call, where it misfires, and what still works if you build games with Claude.
What changed
X user Chasm spotted a new instruction in Claude Code under a flag called “tengu_heron_brook.” It 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.” Chasm said there is no way to turn it off.
Addy Osmani, a member of Anthropic’s technical staff, confirmed it on X. “We added two sentences to Claude Code’s prompt on Opus 5.5 to steer it away from recreating someone else’s specific game because using Claude to infringe IP is against our usage policy,” he wrote. He added that “original games, genre games, and games built from your own designs and assets are meant to keep working.”
When Game Developer asked for comment, an Anthropic spokesperson pointed to Osmani’s post. Anthropic’s Claude Code changelog doesn’t mention the change.
Why we think it’s the right call
The timing isn’t mysterious. In early October, AI decompiled browser ports of Halo CE, GTA Vice City and The Simpsons Hit and Run appeared almost overnight, and many of them ran well. A viral Bloodborne PC port credited Claude in almost every part of the project.
Small studios felt it next. Digital Sun Games cancelled a public playtest for ReVamp over fears that someone would feed the demo to an AI tool and ship a copy. Alliance Arts cancelled the Drunken Goddess Reflux demo, warning its content could be used to quickly imitate the game with AI. When developers start hiding demos, the whole indie ecosystem gets quieter.
Infringing someone’s IP was already against Anthropic’s usage policy. The new rule just makes the model act on it. We’d rather the tool that made cloning trivial take some responsibility than leave every studio to play whack a mole alone.
It also leaves the useful stuff intact. Games in a genre are explicitly fine. Vampire Survivors, Balatro and Peak are simple ideas with endless imitators, but riffing on an idea is a different thing from lifting a codebase wholesale. A roguelike deckbuilder is a genre. A pixel perfect facsimile of one specific game is not.
It’s also a contrast with Valve, which said it doesn’t want to be gatekeepers over which tools developers use. We agreed with Valve on that one. A store judging tools is a different job from a tool declining to copy a specific game. Both positions can be sensible at once.
Where it misfires
The rule is two sentences long. The arguments about it are somewhat longer.
The real problem is that Claude can’t check who owns what. It has no way of verifying that you made the game you’re working on. That cuts both ways. A determined copier can lie, and safety limits on AI tools can often be sidestepped with rhetorical tricks. Meanwhile an honest developer can get refused.
That has already happened. The owner of Conflict Simulations LLC builds digital versions of board wargames for clients who own them, and says Claude Code started refusing that work around October 27. “A blanket category rule against ‘games’ cannot tell the difference between piracy and commissioned professional work for a game’s owner,” the developer wrote on GitHub. Anthropic’s support bot replied that the policy covers all customers with no exception. The developer has since filed an appeal.
Some refusals may come from neighboring rules. Users say Opus 5.5 has also turned down harmless reverse engineering, including a developer checking their own software on October 31. Separately, Claude Code’s cyber safeguards flagged anti-cheat code in one developer’s game. Anthropic hasn’t said the game rule covers either case.
None of this makes the rule wrong. It makes the appeal path the most important part, and right now that path is a reply on X. Osmani’s offer is genuine and welcome. It is also not a process. A careful rule deserves a clear way to say “this one is mine.”
What still works, what’s blocked, and what to do
These are the practical bits worth keeping.
Still works. Original games, games in a genre, and games built from your own designs and assets are meant to keep working. A platformer, a cozy farming sim or a survivors style arena are all fair game.
Blocked. A recreation of a specific existing game, even if it is renamed or called original. Swapping the title on a clone doesn’t change what it is, and the rule says so.
Describe your game, not someone else’s. Pitch your mechanics, your art direction and your own names. If the honest description of a project is “that game, renamed,” the rule is working as written.
Keep your receipts. Put your own design docs and assets in the project, and keep any license or client contract handy. Claude can’t read ownership off a file, but a human reviewing your appeal can. Our guide on who owns your game covers the rights side of AI made work.
Report a wrong refusal. Use the thumbs down button in the product. Anthropic’s policy says a block does not by itself mean you broke the rules. You can also file an issue on the Claude Code GitHub tracker, where developers have been documenting game refusals, or reply to Osmani’s post, since he asked for exactly that.
Don’t try to trick it. Anthropic’s usage policy prohibits intentionally bypassing its guardrails, and a jailbroken clone is still a clone. If your work is legitimate, the appeal is the faster road anyway.
Security work on your own game is separate. Anti-cheat and security reviews run into Anthropic’s cyber safeguards, not the game rule. Its Cyber Verification Program offers adjusted access for eligible teams.
Keep the rest of your workflow. Claude Code is still a strong agent for original projects, and our Claude Code page covers what it does well for game development.
