Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Claude Code now refuses commissioned game work

Written November 6, 2026

Claude Code blocked recreating named games, even commissioned work for owners. Anthropic revised the rule in 2.1.317 — here is what changed.

What happened

Around 27 October 2026, Claude Code began receiving a server-side instruction that makes sessions refuse game-related development work. The clearest account comes from a GitHub issue filed on 30 October by the owner of Conflict Simulations LLC, a business that builds personalized digital modules of board wargames on paid commission for individual clients who own the games. The code is original, written from scratch, built from materials the clients supply themselves after showing proof they own the game, and the finished modules are for the clients' own use — never sold or distributed publicly. Sessions that had performed this work for months began refusing to continue it, citing the new instruction against reproducing games. The reporter works across multiple machines and two paid accounts (Max and Team), and asks for three things: narrow the instruction to target actual infringement, provide a verification or exemption path for professionals doing commissioned, ownership-verified work, and document server-delivered instruction changes of this scope in the changelog.

Two details in the reporter's own account complicate a simple before-and-after story. First, the work is not publisher-licensed: the reporter corrected the issue on 30 October to say so plainly, after an earlier version of the issue had described it as licensed. Second, the refusals did not start the day the rule reportedly arrived. Sessions kept doing the same client work after about 27 October, and the refusals began only after the reporter asked Claude to check whether the rule affected the work. Clearing that session did not resolve it — the refusal persisted in sessions working from the same repositories.

What Anthropic confirmed

On 30 October, Addy Osmani of Anthropic's technical staff confirmed the change in a public post, as reported by Tom's Hardware: Anthropic 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 intellectual property is against its usage policy. Osmani added that original games, genre games, and games built from your own designs and assets are meant to keep working, and that Anthropic will keep iterating to get the balance right. He invited developers whose own work gets turned down to send the case to him directly. The rule is server-side: no local setting adjusts it, and the change arrived without a changelog entry. The two sentences themselves have not been published by Anthropic; the wording circulating in screenshots comes from an X user, not from Anthropic.

What changed in 2.1.317

After complaints that the rule blocked legitimate projects, Anthropic revised it. Osmani wrote in a further post, reported by Tom's Hardware, that the rule was changed in version 2.1.317: you can now name a game to explain what you want, and Claude should create an original game in the same genre. If you ask it to copy the original game, it will offer to make something similar instead. That revision answers the most common complaint — mentioning a game to explain the mechanics you wanted was enough to trigger a refusal — but it does not answer the commissioned-work case at the centre of the GitHub issue. Building a personalized digital module of a specific existing board wargame is still a recreation of that game, not an original game in the same genre, so the revised rule still points at refusing it. There is still no published policy text naming games, and no formal exemption process for professionals doing commissioned work. The support bot told the reporter the policy covers all customers with no exception, and both of the reporter's support tickets were passed to staff.

What the rule draws, and what it does not

The distinction the rule draws is between a named, commercially released game and a genre exercise or an original design. Original games, games in a genre, and games built from your own designs and assets are meant to keep working. A recreation of a specific existing game is refused, even if it is renamed or called original. What the rule does not distinguish is piracy from commissioned professional work for a game's owner: a blanket category rule against games cannot tell the difference, as the reporter put it. Teams discover the boundary at request time, from the refusal, not from policy text — there is no published document that states where the line falls. Wider reports that Opus 5.5 is also refusing reverse-engineering and security work are user reports only; Anthropic has not linked them to this rule, and the confirmed scope is games.

What a game developer can do

Frame the request around what is original: a game in a genre, mechanics explained by naming a game as a reference, or assets and designs of your own. Under the revised rule, naming a game to explain the mechanics you want should now work, with Claude building an original game in the same genre. Do not expect a recreation of a specific existing game to go through, even for a client who owns the game — that is the case the rule is aimed at, and there is no exemption path to apply for. If Claude turns down work that is genuinely yours, Osmani invited developers to send the case to him directly; that is an informal route, not a published process. And treat the server-side nature of the rule as the operational fact: the behaviour can change without a version you install or a changelog you can read, so a workflow that depends on Claude Code accepting game work can break mid-project with no warning.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Claude Code 2.1.318: sign-in expiry and fork effort · Audit a repository's git config before any agent opens it · What broke in agent tools this week