Anthropic quietly flipped a switch inside Claude Code, and the switch says no to one very specific thing: rebuilding games that already exist. Claude Code game cloning of named titles is now blocked at the server level. If you vibe-code games for fun or profit, this changes what you can ask for. It does not change what you can build from scratch.
Sometime around October 27, a new rule landed in Claude Code’s server-side instructions. The rule is short. 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.
What the Claude Code game cloning rule actually says
Screenshots of the change spread fast. The rule sits under an internal flag called tengu_heron_brook, and here’s the part that matters: it runs on Anthropic’s servers. You can’t turn it off. There’s no toggle in settings, no config file edit, no clever prompt prefix that removes it.
An Anthropic spokesperson later confirmed the change through a statement from Addy Osmani, a member of Anthropic’s technical staff. His explanation, in plain terms: they added two sentences to the model’s instructions because using Claude to infringe someone’s IP violates Anthropic’s usage policy.
So the era of typing “make me Pokémon but call it Monstercatch” into Claude Code is over. Honestly, that was always the shadiest use case. But the rule is catching more than copycats, and that’s where things get messy.
Why Anthropic is cracking down on game cloning
The timing isn’t random. Claude Code game cloning became a real business, and AI-made clones have been terrorizing indie developers for months. The pressure finally boiled over.
One viral prototype about finding a needle in a haystack of hay drew copycat Steam pages within days. A clone called Find The Needle shipped a public demo before the original and passed it in Steam followers by October 5. The original developer estimates it sits roughly 20,000 wishlists behind the clone that copied it. Think about that. Someone else’s game, built on someone else’s idea, outperforming the real thing.
Bigger studios got nervous too. Digital Sun, the team behind Moonlighter, scaled back the public playtest for its next game over fears that players would feed the demo into an AI tool and ship a clone first. Valve even addressed the cloning problem directly with developers in South Korea.
Against that backdrop, Anthropic’s move looks defensive. The company doesn’t want its model to be the easy button for IP theft. Fair enough on paper.
What’s still allowed (and what’s blocked)
Here’s the twist: the Claude Code game cloning rule is narrower than the panic on social media suggests. Original work is untouched. Here’s the split:
| Request type | Claude Code |
|---|---|
| An original game from your own design | Allowed |
| A game in an existing genre (your own platformer, your own match-3) | Allowed |
| Using your own art, assets, and code | Allowed |
| A remake of a specific named game | Blocked |
| A renamed clone with tweaked mechanics | Blocked |
| Turning the rule off locally | Not possible |
Notice what’s missing from the blocked column: mods, ports, and repair work on games you legitimately work on. That gap is exactly where developers are reporting problems.
When legit work gets caught in the net
Claude Code’s GitHub tracker filled up with complaints within a week. A developer said the tool refused work halfway through their own project. Another hit a wall replicating a single game mechanic. A third got blocked patching a tabletop-style game. None of these were clone requests, which is exactly the problem with policing by keyword instead of by ownership.
The sharpest case: Conflict Simulations LLC, a developer doing commissioned work for a game’s actual owner, reported refusals with a blunt conclusion. A blanket category rule against games cannot tell the difference between piracy and professional work for the rights holder. Anthropic’s own support bot told them the policy covers all customers with no exceptions. They filed an appeal.
And here’s a creepy detail from that thread: the refusals started only after the developer asked Claude whether the new rule affected their projects. Then it kept refusing in fresh sessions on the same code. One commenter suggested the refusal had spread into the project’s memory or Git history. The developer planned to scrub it.
If you’re a hobbyist, that’s a weird story. If your income depends on Claude Code, it’s a work stoppage with no clear off switch.
What to do if your project gets blocked
Stuck mid-build? A few practical moves, in order:
- Start a fresh session. If a refusal got embedded in the current conversation, a clean chat sometimes clears it. Don’t ask Claude about the rule itself, just resume the actual work.
- Reframe to your own assets. Describe your original design, your mechanics, your art. The rule explicitly allows work from your own designs, so make that the center of the prompt.
- Report false positives. Osmani asked developers whose genuine projects get rejected to report the cases to him directly. Screenshots help.
- Check what’s on your machine. One tampered Claude Code extension with a backdoor hit the Cursor marketplace on October 29. If you installed plugins from random sources while chasing workarounds, audit them now.
- Consider a second tool. Keeping a fallback coding assistant isn’t cheating, it’s continuity. If one platform can stop your workflow with a server-side flag, a single-vendor setup is a business risk.
Should you switch tools over this?
Some developers are already moving game work to open-weight models with no such restrictions. That works, and nobody can flag your session from a datacenter. But be honest about the trade: you give up the polish, tooling, and safety net of a managed product, and you inherit the full responsibility for what your code does.
My take? The rule itself is reasonable. Recreation-for-profit of games you don’t own was always a lawsuits-waiting-to-happen hobby. What’s not reasonable is shipping it silently, with no appeal path documented up front, in a tool people run their businesses on. Predictability is the whole product when you build workflows on someone else’s platform.
There’s also a legal reality worth naming. Rules like this don’t erase the clones, they just relocate them. Determined cloners have already demonstrated they’ll jump platforms. What the rule does change is Anthropic’s exposure, and honestly that seems to be the main goal.
For beginners, one more thing deserves a mention. Rebuilding classic games has been the classic way to learn to code for decades. Half the developers I know made a Flappy Bird clone as their first project. If you’re using Claude Code to learn, aim that energy at original ideas from day one now. You’ll build a portfolio you actually own, which matters if any of those projects ever make money.
The takeaway
Claude Code game cloning of specific existing titles is off the table, and no local setting brings it back. If you build original games or work from your own designs, nothing changes for you. If a refusal hits your legitimate project, start a fresh session, reframe around your own assets, and report it. And if you’re building any business on one AI tool alone, this week is a good reminder to keep a backup ready.
Want to build something original instead of copying? We covered building apps and games with AI without coding and making your own games by typing, both start from your idea, not someone else’s.