Explainer / Published 2026-10-31

Claude starts refusing to clone and reverse-engineer games

Users report that Anthropic's Claude now refuses to recreate existing games or reverse-engineer game code, a rule that also blocks ordinary debugging work.

Flat editorial illustration of a pile of plain unmarked cardboard boxes on a wooden floor, with a large dark padlock standing in front of them.
Conceptual editorial illustration of sealed game boxes and a lock; it does not depict any company or product.

THE SHORT VERSION

  • Users report that Anthropic's Claude models have begun refusing to reverse-engineer, decompile or clone existing video games, without a public announcement.
  • A rule quoted by users tells the model to build original games but not to recreate a specific existing game, even if it is renamed.
  • The restrictions appear broad enough to block legitimate troubleshooting and mod work, and Anthropic has not confirmed the policy.

What users noticed

Anthropic's Claude has quietly started restricting the kinds of work it will do with video game code, according to users, and the company has not announced the change. Mashable reported that the restrictions cover modding, decompiling and reverse-engineering, and that they are broad enough to affect legitimate game developers and ordinary troubleshooting.

Tom's Hardware reported that multiple users say Claude Code and the Opus 5.5 model are blocking innocuous reverse-engineering requests, including work that uses a tool called Reverse Engineer Anything. The reports vary, which makes it hard to tell a policy from a set of over-triggered refusals.

The rule people are quoting

The clearest evidence is a rule users say is now in force. According to Tom's Hardware, it instructs the model to build original games, games in a genre, and games from the user's own designs and assets, and not to build a recreation of a specific existing game, even if it is renamed or called original.

That wording explains both the intent and the collateral damage. The intent is to stop the model being used to clone a commercial title wholesale. The collateral is that a developer asking for help understanding how an old game stores its level data may now be read as asking for a recreation, because the model cannot reliably tell analysis from cloning.

Why Anthropic would do this now

The context is a year of AI-assisted game cloning. Mashable described decompilers using AI to take apart game code, projects that made old titles playable in a browser without the rights holder's involvement, and a wave of attention that followed. Game companies have responded with subpoenas and legal pressure, and some developers have reportedly been targeted by extortion attempts.

For a model provider, the cheapest way to reduce that exposure is to refuse the category of request rather than adjudicate each one. That is a familiar pattern: models have been trained to decline entire topics because the cost of a false refusal is lower than the cost of a bad generation that ends up in a lawsuit.

The cost falls on legitimate work

The problem with category-level refusals is that the category is defined by the model's guess about intent. A developer debugging a crash in their own project, a modder working with the publisher's blessing, and a preservationist documenting an abandoned format all look similar to a classifier, and all can be refused.

That matters commercially because game studios have started to rely on these tools for exactly this kind of code archaeology. Legacy engines, proprietary formats and decades-old build systems are where AI assistance is most valuable, and they are also where the words reverse-engineering appear most often.

Policy by silence

Anthropic has not published the rule or explained the scope of the restriction, according to both reports. That leaves customers reading GitHub issues and social posts to work out what their paid tool will and will not do, which is a poor way to run a developer product.

A published policy would let teams plan. A silent one produces the worst of both outcomes: users who hit refusals cannot tell whether they are breaking a rule, and developers who follow the rules cannot tell whether their workflow is safe to depend on next month.

How a refusal actually gets decided

A model does not have a rule book it consults line by line. Refusals come from a mixture of training, system instructions and safety classifiers, and the same request can be accepted in one session and declined in another depending on context and phrasing. That is why user reports of this change are inconsistent: some see a hard block, others see occasional refusals.

For a developer, that inconsistency is the real problem. A tool that refuses reliably can be worked around; a tool that refuses unpredictably forces teams to keep a fallback for every task, which erodes the productivity case that justified the subscription in the first place.

What a published policy would need

A usable policy would say which tasks are prohibited, which are allowed with conditions, and how a refusal can be reviewed. It would also distinguish analysis from reproduction, because the difference matters to the developer and is exactly what a classifier cannot see.

Without that, the rule is discovered by trial. Companies buying these tools for engineering work need to know whether a task will be available next quarter, and silent policy changes are the fastest way to lose the trust that enterprise contracts depend on.

What is established, and what is not

Established: users report that Claude models refuse some game reverse-engineering and cloning requests; a quoted rule tells the model to avoid recreating a specific existing game; the restrictions appear to affect legitimate development work; Anthropic has not confirmed or explained the change. Not established: the exact model versions and settings affected, whether the rule is enforced by policy or by training, and how users can appeal a refusal.

For readers, the useful signal is that the boundary between copying and understanding is being drawn by model providers, not by courts. This site has covered Anthropic's tier structure, Claude Sonnet 5.5's positioning for everyday work and the verification controls proposed for high-risk models; all three describe a company tightening what its models will do.

Sources & reporting limits

  1. Anthropic takes steps to block Claude from reverse-engineering video games
  2. Anthropic's Claude AI blocks video game cloning and reverse-engineering
Keep the thread.

Follow Industry to find related stories on your next visit.

THE WEEKLY EDIT

The week, made clear.

Stories worth understanding, brought together in one weekly edition.

Share this page

Instagram, TikTok & other apps

Copy the page link, then paste it where your chosen app supports links. You choose whether to send or publish.