A subtle detail in the Claude Code interface recently caused a backlash disproportionate to its brevity: two sentences added to the Opus 5.5 model's prompt that essentially say, "don't recreate existing games, even if you rename the project." The change arrived without public announcement, without a changelog entry, and without a local toggle. It was spotted by an X user known as chasm and confirmed by Addy Osmani, a member of the Claude Code technical team at Anthropic. What the company describes as a legitimate intellectual property protection measure has instead generated a wave of refusals across legitimate projects — including contracted professional work — raising a difficult question: how does an AI company define, in two sentences, what counts as and what doesn't count as a game?
What changed
Around October 27, Claude Code sessions running on the Opus 5.5 model began receiving, directly from Anthropic's servers, an internal configuration identified as `tengu_heron_brook`. This is not a software update, a separate classifier, or an account-level restriction. The constraint operates as an instruction added to the system prompt — meaning it shapes the model's response in real time, without a technical filter that blocks inputs or outputs in any deterministic way.
The exact text, found in Claude Code sessions running version 2.1.311, is deceptively simple: "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." There is no ambiguity built in: an original game, a project within an established genre, or work based on the user's own assets is permitted; a recreation of an identified commercial title is prohibited. Renaming the project or presenting it as something new does not bypass the restriction.
The change appeared nowhere in an official announcement. The Claude Code changelog, in version 2.1.311 dated October 26, makes no mention of games, intellectual property, or policy changes. The only public confirmation came in an X post by Addy Osmani on October 30, in which he wrote that Anthropic had "added two sentences to Claude Code's prompt on Opus 5.5 to steer it away from recreating someone else's specific game" and linked the decision directly to the company's usage policy: "using Claude to infringe IP is against our usage policy."
The problem: where does piracy end and legitimate development begin?
Anthropic's intent is clear — and reasonable. AI programming tools have made it trivial for a single developer to produce, in hours, a playable imitation of a commercial game. Independent studios have reported that public demos of their games are being cloned by AI agents before launch, and Alliance Arts cancelled the public demo of Drunken Goddess Reflux in October specifically for this reason. Protection against AI cloning is a genuine problem.
But the execution is blunt. The restriction does not distinguish between cloning a commercial game to distribute pirated copies and recreating mechanics inspired by an existing title for the purposes of prototyping, hardware testing, or legitimate development. Tuomas Taini, a developer who used Claude Code to create DuckQuest — a controller prototype for Quest 3 with gameplay inspired by Duck Hunt — posted a frank reaction: "This is horrible for hardware prototyping." He was not trying to clone or sell Duck Hunt; he was testing controllers using mechanics as a reference for feedback.
The most documented case is that of the operator of Conflict Simulations LLC, a company that builds personalized digital modules of tabletop wargames for individual clients. In a GitHub issue on the Claude Code repository on October 30, the developer reported that Claude Code began refusing work the company had routinely completed for months — including projects for clients who owned the original physical games. "A blanket category rule against 'games' cannot tell the difference between piracy and commissioned professional work," they wrote. Anthropic's support confirmed that the policy covers all customers without exception, and the developer filed a formal appeal.
Here lies the structural problem: owning a physical board game does not transfer digital reproduction rights. The developer had the right to possess the physical game, but not to reproduce its content digitally — even for an individual client's personal use. The legal distinction exists, and it is complex. But Claude Code has no verification or accreditation system to distinguish legitimate work from piracy. It has two sentences.
Why this matters for the gaming industry
The restriction arrives at a moment when indie game development is already feeling the effects of automated generation. Steam itself has reported an increase in AI-built clones — and the Anthropic restriction, applied to Opus 5.5, is only one piece of this puzzle. Other AI tools may not have this restriction, and the technical barrier for a user to simply switch models is practically non-existent.
What Anthropic has not answered publicly is how Claude Code classifies, in practice, the boundary between "generic genre project" and "specific title recreation." Without a clear framework — and without a formal verification path for contracted work — developers are left guessing. Anthropic itself acknowledged the problem: Osmani said the company will continue adjusting the implementation and asked developers to report incorrect refusals directly to him. The implicit message is that this version is a first iteration.
The question that remains: when an intellectual property policy is reduced to two sentences in a prompt, who decides where the line is drawn? And what happens when that line is drawn incorrectly?
Sources: The Next Web, DataStudios, Gameriv
✓ Independent sources cross-checked and verified before publishing
