Anthropic has told Claude and Claude Code to stop rebuilding existing games, even when the result gets renamed. Original games, genre games, and projects built from a developer's own assets are still allowed, according to the company.
The Rule Anthropic Added to Claude
Engadget quoted the new instruction directly. 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."
Addy Osmani, who works on Anthropic's technical team, confirmed the change on X. His explanation was short. Using Claude to infringe intellectual property violates the company's usage policy, and the goal is to steer the tool away from recreating specific titles.
He added that original games, games in a genre, and games made from a user's own designs and assets should be unaffected. He also said Anthropic will keep adjusting to find the right balance, which is a signal that the line isn't final.
Three Green Lights and One Red Light
The rule is easier to hold in your head as a short list.
Green light: an original game. Your design, your code, your art.
Green light: a game in a genre. A platformer, a roguelike, a tower defense game. Nobody owns the genre.
Green light: a game built from your own designs and assets. That includes the case where you bring art you already made and ask Claude to wire up the mechanics.
Red light: a recreation of a specific existing game, renamed or not. Calling it original doesn't move it to the green side.
What the rule doesn't define is where a genre exercise ends and a recreation starts. A platformer with a jumping mascot is a genre game. A platformer with the same level layout, enemy placement, and art direction as a known title is something else. The line runs somewhere between those two, and Anthropic hasn't published a test for finding it.
Why the Change Landed in Late October
The timing follows a stretch of projects that decompiled big commercial games and rebuilt them to run in a browser. Halo: Combat Evolved, Call of Duty: Modern Warfare 2, and Grand Theft Auto V have all been named in coverage of that wave.
Those projects are technically impressive and legally exposed. They copy level data, assets, and design wholesale, then present the result as a demo of what a coding agent can do. The demo is the point, and the copied material is the cost.
Anthropic has been through IP litigation before. In 2025 it agreed to a $1.5 billion settlement in a class action brought by 500,000 authors. After that, the Elvis Presley estate filed a similar suit. A tool that generates infringing game code is a liability the company has already paid for once.
That context explains the speed. A restriction phrased as a policy update is cheaper than another lawsuit.
The tengu_heron_brook Detail
Kotaku reported that the restriction maps to a configuration item named tengu_heron_brook. The name follows Anthropic's habit of giving internal flags odd codenames.
Treat that detail as reported, not confirmed. Anthropic hasn't walked through the change item by item, and the codename comes from coverage rather than a company statement. It's useful because it shows the restriction was a config change on the server, not a new model.
The rollout was server-side in late October, with reports pointing to around October 27. Users noticed and started posting about it on November 1. That gap explains why the change felt sudden. It was live for days before anyone outside the company spotted it, and nobody got a changelog entry in the meantime.
Developers Say Legitimate Work Got Caught
Some developers report that projects unrelated to game cloning were blocked. The examples they describe are general reverse engineering and debugging tasks, the kind of work that involves reading compiled code to find a bug.
Those accounts are user reports. Anthropic hasn't responded to the specific cases, and there's no published list of what the filter checks.
The pattern is familiar to anyone who has shipped a classifier. A rule written to stop one behavior gets enforced by something that can't always tell the target from the thing next to it. When that happens, the false positives are usually people doing ordinary work near the edge of the rule.
For a studio using Claude on its own codebase, that's the risk worth planning around. The blocked request may have nothing to do with games.
What to Do If Your Build Gets Blocked
Start by describing the work in terms of what it is, not what it resembles. "A top-down shooter with a dash mechanic and wave-based enemies" is a genre description. "A remake of a specific 2007 shooter" isn't, and neither is a project name that signals the source.
Bring your own assets and say so. If the art, level design, and audio are yours, that's one of the three allowed categories, and the request should say it plainly instead of leaving the model to guess.
Keep the design document separate from the code request. A document that describes mechanics, tuning values, and systems gives the model something to build from that isn't a copy of another game.
If a legitimate task gets refused, re-ask with the IP question removed. Ask for a general technique rather than a specific product's behavior. Most debugging work can be phrased that way without losing anything.
Where the Boundary Is Still Undefined
Anthropic hasn't published a definition of "recreation." No threshold, no checklist, no examples of what passes.
That leaves three groups in different positions. Hobbyists making original games are fine. Studios using Claude on their own IP are fine. People learning game development by rebuilding a classic are in the gray zone, and the answer may depend on how they phrase the request.
Osmani's note that the company will keep iterating suggests the line will move again. For now, the safest reading is the literal one: build your own game, in a genre you like, with assets you made.






