Claude Code Won't Recreate Existing Games Anymore: What the Opus 5.5 Rule Blocks and What Still Works

If you use Claude Code to make games, nothing changes for original ideas: Anthropic says original games, games in a genre, and games built from your own designs and assets “are meant to keep working.” What changed is that Claude Code on Opus 5.5 is now told not to build “a recreation of a specific existing game, even if it is renamed or called original.” So “make me a cozy farming game with a fishing mini-game” is fine, while “rebuild Pokémon Red in the browser and call it something else” is the kind of request it is now steered away from. If Claude turns down a game that is genuinely yours, the fastest fix is to put your own design document and assets in the project and say so plainly, and Anthropic has asked to hear about those cases. Below is the exact rule, where it came from, how to check whether it applies to you, and how to work with it. Everything was checked on November 1, 2026 against Addy Osmani’s statement on X, Anthropic’s Usage Policy, the Claude Code docs, the Claude Code package on npm, and independent analysis by XDA Developers and madrobot.blog.

Key facts:

  • The rule (verbatim): “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.” (XDA, madrobot.blog)
  • Confirmed by Anthropic: Addy Osmani, of Anthropic’s technical staff, wrote that Anthropic “added two sentences to Claude Code’s prompt on Opus 5.5” because “using Claude to infringe IP is against our usage policy.” (X)
  • Where it appears: inside Claude Code version 2.1.314, published on npm on October 30, 2026 (00:12 UTC). It is not in 2.1.312. It is not mentioned in the public changelog. (npm, madrobot.blog)
  • It is an instruction, not a hard block. There is no setting to switch it off, and how strictly Claude applies it depends on the request.
  • If Claude refuses your own game: Osmani asked people to “send it my way.” You can also report it with /feedback inside Claude Code.

What exactly changed

Claude Code sends Claude a set of instructions (the “system prompt”) before every session. In version 2.1.314 those instructions gained two sentences:

“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.”

The rule came to light in an X post by the user @chasmmmmmmmmmmm on October 30, which said Claude Code “picked up a new rule around Oct 27, sent from Anthropic’s servers under a flag called ‘tengu_heron_brook’” and that “there’s no setting to turn it off.”

Two independent write-ups then looked inside the Claude Code program itself:

  • XDA Developers says it found the exact sentence inside the 2.1.314 binary, plus a separate switch called original_games_guidance tied to the Opus 5.5 instructions. In XDA’s tests, Opus 5.5 said its session instructions prohibited recreating specific existing games, “including renamed versions.”
  • madrobot.blog compared releases and reports the line is in 2.1.314 but not in 2.1.312 (there was no public 2.1.313), and that the new version skips its own copy of the line if the same text already arrives from Anthropic’s servers, which suggests it was tested remotely first.

npm’s own release timestamps match that sequence: 2.1.312 was published on October 27 and 2.1.314 on October 30, 2026 (UTC).

Anthropic’s explanation

When asked about it, an Anthropic spokesperson pointed reporters to Addy Osmani’s reply on X, posted on October 30, 2026 (16:58 UTC, which is October 31, 00:58 Beijing time). In full:

“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. Original games, genre games, and games built from your own designs and assets are meant to keep working. We’ll continue to iterate to ensure we’re striking the right balance. In the meantime, if Claude turns down something that’s yours, send it my way.”

The policy he refers to is Anthropic’s Usage Policy, which already listed “Infringe, misappropriate, or violate the intellectual property rights of a third party” under things you may not use Claude for. So the rule is not a new ban; it is Claude Code now actively steering away from a kind of request that was already against the policy.

What still works and what doesn’t

The rule draws its line between a specific existing game and everything else. Based on the wording and Anthropic’s statement, here is how common requests map onto it. Treat the middle column as guidance, not a guarantee: the rule is a prompt instruction, so Claude judges each request.

What you ask forUnder the new ruleWhy
”A roguelike deck-builder with a space theme”Should workA game in a genre
”A puzzle game where blocks rotate the whole board” (your own idea)Should workAn original game
”Build my game from this design doc and these sprites” (yours)Should workYour own designs and assets
”Recreate Tetris / Pokémon Red / GTA, exactly”Steered awayA specific existing game
”Same as Pokémon Red, but call it Monster Quest”Steered awayThe rule says “even if it is renamed or called original"
"Help with a decompilation of a game I own”Unclear; may workXDA found Opus 5.5 willing to help, separating reverse engineering from recreation, but did not test a full project
A fan game, mod, or remake of an abandoned gameUnclearDepends on whether it is a recreation of a specific game. Anthropic has not given examples

The practical difference: “inspired by a genre” is fine, “a copy of that particular title” is not. A game being old, out of print, or free to play does not change the wording of the rule.

Does the rule apply to you?

You cannot see the rule in a settings screen, but you can check the two things it depends on: your Claude Code version and your model.

Step 1: Check your version and model

Inside Claude Code, type:

/status

The Status tab shows your Claude Code version, the model you are on, your account and connectivity (commands reference). If you are not comfortable in a terminal, you can simply tell Claude Code “show me my Claude Code version and which model this session uses.”

What to look for:

  • Model: the rule is tied to the Opus 5.5 instructions. Per the model configuration docs, Opus 5.5 is now the default model for Pro, Max, Ultra, Team, Enterprise and Anthropic API accounts, so most people on a plan are on it unless they chose otherwise.
  • Version: the sentence is built into 2.1.314 and later. As of November 1, 2026, npm lists 2.1.316 as “latest” and 2.1.309 as “stable”.

Step 2: Don’t assume an older version or another model avoids it

Two details from the reporting matter here:

  • The original sighting says the rule arrived from Anthropic’s servers around October 27, before 2.1.314 shipped, and XDA describes that delivery path as one that applies “to all models used in Claude Code” for accounts that receive it. So being on the “stable” release does not mean you will never see it.
  • More importantly, recreating someone else’s specific game is against Anthropic’s Usage Policy on every model, and the same policy prohibits intentionally bypassing “capabilities, restrictions, or guardrails” in Anthropic’s products. Switching models or downgrading to get a clone built is not a workaround we recommend; it puts your account at risk and does not make the result legal to publish.

For choosing a model for ordinary work, see our guide to Opus vs Sonnet vs Haiku 5.5.

How to brief Claude Code on your own game so it isn’t misread

The most common complaint after the change, raised on Hacker News and quoted by madrobot.blog, is: “How would Claude know if the designs and assets are my own?” The rule itself does not say. You can reduce misunderstandings by giving Claude Code the evidence up front, which is also simply good practice for any game project.

1. Put your design in the project folder

Before you start, create a short design document in the project, for example GAME_DESIGN.md, and describe your game in your own words: the core idea, the rules, the controls, the art style, and what makes it yours. You do not need to write it by hand; you can tell Claude Code:

Create GAME_DESIGN.md from my notes below. This is my own original game. Keep my wording for the core mechanic.
[paste your notes]

2. Keep your own assets in the project

If you have your own sprites, sounds or level sketches, put them in a folder such as assets/ and tell Claude Code which files are yours (“all files in assets/ were drawn by me”). The rule explicitly allows “games from the user’s own designs and assets.”

3. Describe the genre, not a famous title

“A turn-based monster-collecting RPG with a weather system” describes a genre. “Like Pokémon Diamond but…” invites Claude to treat it as a recreation. Name the mechanics you want, not the game you are thinking of. Mentioning another game as a loose reference (“the pacing feels a bit like old Zelda dungeons”) is different from asking for that game; if you hit a refusal, rewording to describe the mechanic is the honest fix.

4. Make it stick across sessions

Claude Code reads a CLAUDE.md file at the start of each session in that project. Run /init to create one, or /memory to edit it (commands reference), and add one line such as: “This project is my original game. The design is in GAME_DESIGN.md and the art in assets/ is mine.” That way you do not have to repeat yourself every session. If you build many projects the same way, a reusable Claude skill can hold your standard brief.

What to do if Claude refuses your own game

  1. Re-explain once, with evidence. Point Claude to GAME_DESIGN.md and your assets/ folder and say the project is yours. Most misunderstandings come from a prompt that names a famous game.
  2. Report it in Claude Code. Type /feedback (or /bug). It opens a dialog where you choose how much of the conversation to include and confirm before anything is sent; when you are signed in to Anthropic, the report goes to Anthropic (commands reference).
  3. Tell Anthropic publicly if you want. Osmani’s post asks people to send him cases where “Claude turns down something that’s yours.” Replying to his post on X with a short description is the route he offered.
  4. Don’t try to trick it. Renaming the game, calling it “original”, or hiding which game you mean is exactly what the rule says it should not accept, and deliberately working around product guardrails is against the Usage Policy.

Common questions

Is this a hard block I’ll hit in every session? No. It is two sentences in Claude’s instructions, not a filter. madrobot.blog notes “how firmly Claude sticks to it will depend on the request,” and XDA saw different behavior between Opus 5.5 and Opus 5.

Can I turn it off in settings? No. There is no documented setting for it, and the original report says “there’s no setting to turn it off.”

Does it affect non-game apps? The wording only mentions games. Some Hacker News readers asked whether, for example, rewriting an Electron app as a native app would count; Anthropic has not addressed that, and nothing in the two sentences refers to other software.

Does it apply in the Claude app or claude.ai chat, not just Claude Code? Anthropic’s statement only mentions “Claude Code’s prompt on Opus 5.5.” We found no official statement about other Claude apps. The Usage Policy’s IP rule applies everywhere, though.

Will this change again? Probably. Osmani wrote that Anthropic will “continue to iterate to ensure we’re striking the right balance,” and the changelog for 2.1.314 does not mention the rule at all, so watch for behavior changes rather than release notes.

Is “a game in the style of X” allowed? “Games in a genre” are explicitly allowed. A game that copies one specific title’s characters, levels, names or art is what the rule targets. If in doubt, describe your own twist on the genre.

Bottom line

For people making their own games with Claude Code, the change mostly asks you to describe your game instead of pointing at someone else’s. Keep a design document and your own assets in the project, describe genres and mechanics rather than famous titles, and use /feedback or Osmani’s X thread if Claude still refuses something that is yours. For more on running long Claude Code projects day to day, see using Claude Code as a daily driver, and for limits that can interrupt a long build, see what to do when Claude Code’s usage limit is reached.

Sources