Anthropic has drawn a line through one of the most popular uses of its coding tool. Claude Code will no longer help users rebuild a specific existing video game, even if they rename it or describe it as an original project. Anthropic confirmed the change on October 30, 2026, and it is the company’s first direct answer to Claude Code game clones, which spread across the web in the weeks after the Opus 5.5 model’s release.

Don’t mistake this for a ban on making games with AI. Anthropic’s rule is narrow on paper: it targets copies of one particular title, not game development in general. In practice, that distinction is already proving hard to police, and developers on both sides of it are unhappy.

Renaming the game does not help.

What Anthropic actually changed

Two sentences were added to the prompt Claude Code runs on Opus 5.5. The full instruction, first spotted by an X user posting as Chasm around October 27, reads: “Do build original games, games in a genre, and games from the user’s own designs and assets. Don’t build a recreation of a specific existing game, even if it is renamed or called original.”

Chasm found the instruction delivered from Anthropic’s servers under an internal flag name, “tengu_heron_brook,” and reported that users have no setting to switch it off. Reports put the change in Claude Code version 2.1.314, which shipped in late October. Anthropic has not published the rule in a changelog or a standalone announcement, which is part of why it took a user post to bring it to light.

Confirmation came from Addy Osmani, a member of Anthropic’s technical staff who works on Claude Code. In a post on X on October 30, Osmani wrote: “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 added that original games, genre games, and games built from a user’s own designs and assets “are meant to keep working” and that Anthropic will “continue to iterate to ensure we’re striking the right balance.”

How Claude Code game clones forced the issue

Kotaku reported that hundreds of browser ports appeared within about two weeks of Opus 5.5’s release, covering titles such as Halo and Call of Duty: Black Ops. Some were built for fun, some for attention, and some for money. For independent studios, the speed was the shock: a recognizable game could be approximated in days by someone who owned none of it.

Game Developer reported that the wave unsettled indie developers, and at least one studio pulled back a public demo over fears its work would be replicated. AI Weekly reported that indie studio Alliance Arts cancelled a demo of its game Drunken Goddess Reflux, warning about potential AI replication of its gameplay and presentation. Anthropic’s usage policy already barred using its products to infringe intellectual property. Until now, though, that policy lived in a document. The new rule puts it in the prompt, at the moment a user asks.

Copyright holders have been here before with mods, fan remakes, and ROM hacks. What’s different is the labor involved: a fan remake used to take months of skilled work, which limited how many appeared. An AI coding agent collapses that cost, so a platform can be flooded before a studio’s lawyers finish drafting a letter.

What still works, and what doesn’t

Ask Claude Code to build a platformer, a racing game, or a dungeon crawler, and it should still say yes, as long as the game is your own idea or built from your own assets. Ask it to rebuild a named commercial title level by level under a new name, and it is supposed to say no. That is the line Anthropic says it is drawing.

Early tests show the line holding in the obvious cases. XDA Developers reported that Opus 5.5 refused to recreate Pokemon Diamond and cited its session instructions when it did so. Oddly enough, the same model agreed to help with a Pokemon Diamond decompilation project, offering to turn disassembled functions into readable code and rebuild the ROM from the user’s own copy. One request was a copy of someone else’s game. The other was framed as work on a copy the user already owned. Claude treated them differently, and that gap is where most of the arguments will live.

Modding sits in the same gray area. Anthropic’s rule does not explicitly ban modding or optimizing an existing game, but it gives no clear test for when help with an existing title crosses from legitimate work into a recreation. Developers who port or remaster their own games will need to say so plainly and keep their design documents and assets in the project, or risk being refused by a model that can’t tell their game from a copy.

Why the line is already blurring

Within days of the rule surfacing, developers were reporting refusals that had nothing to do with cloning. Wccftech reported a GitHub issue filed on October 30 by a developer at Conflict Simulations LLC, who said Claude Code had started refusing work on personalized digital board-wargame modules commissioned by paying customers, work the developer said had run fine for months. Other user reports collected by Kotaku and Wccftech describe refusals on anti-cheat work, security reviews of developers’ own games, and even a Windows crash dump analysis.

Those wider refusals are user reports, not confirmed effects of the games rule, and Anthropic has not tied them to it. Still, they explain why Osmani’s post ended with an invitation: “if Claude turns down something that’s yours, send it my way.” A rule that only catches clones is a win for studios. A rule that also catches a studio’s own work is a support ticket, and then a cancelled subscription.

There’s a second problem Anthropic can’t fix alone. Determined cloners can rephrase a request, switch tools, or use an open-weight model with no such rule. The rule raises the effort for the lowest-effort copies. It does not make cloning impossible, and Anthropic has not claimed otherwise.

Why this matters

Watch what happens next, because this is how AI policy now gets enforced: not in a courtroom or a terms-of-service update, but in two sentences of a system prompt that users never see. Anthropic is betting that a quiet instruction can do what takedown notices couldn’t, which is to slow the flood at the point of creation rather than chase copies after they spread.

If it works, expect rival vendors to copy the approach for music, film, and books. If it misfires, and legitimate developers keep getting refused on their own projects, the backlash lands on Anthropic first, because it moved before its rivals did. Either way, the precedent is set: the companies that build the tools are now deciding, request by request, what counts as a copy.

Frequently asked questions

Can I still make an original game with Claude Code?

Yes. Anthropic says original games, genre games, and games built from your own designs and assets are meant to keep working. The rule targets recreations of a specific existing title, not game development in general.

What happens if I rename the game I’m copying?

Claude Code is told to refuse anyway. The rule explicitly covers recreations “even if it is renamed or called original,” closing off the simplest dodge.

Does the rule apply to all Claude models?

Anthropic has only confirmed it for Claude Code running on Opus 5.5. The company has not said whether the same instruction applies to Claude on the web, the API, or other models.

What should I do if Claude Code refuses my own project?

Say clearly in your request that the game, designs, and assets are yours, and keep that material in the project. Anthropic’s Addy Osmani has asked developers whose own work gets refused to report those cases to him so the rule can be adjusted.

Sources: Game Developer, Kotaku, Wccftech, Tbreak