Claude Code adds game cloning limits, developers report blocks

The strategic issue is the gap between coding capability and permission to use it. The report describes a targeted restriction on recreating existing games, alongside complaints about reverse-engineering refusals. Those are different claims, and the distinction matters when assessing whether a tool has become less capable or simply more constrained. ([tomshardware.com](https://www.tomshardware.com/tech-industry/artificial-intelligence/anthropic-confirms-new-claude-code-limits-to-prevent-game-cloning-users-report-opus-5-5-is-also-actively-blocking-reverse-engineering-tasks)) For Race to AGI readers, my interpretation is that deployment rules deserve their own place beside benchmark scores: a system that can solve a task but declines it has a different practical value from one that cannot solve it.

The competitive implication is conditional. If legitimate development work is repeatedly blocked, customers could favor tools with clearer boundaries or better review processes. If the restriction stays narrowly focused on copying protected games, it could instead make commercial deployment easier to defend. Neither outcome demonstrates progress toward general intelligence. The useful next test is a reproducible comparison of original game development, authorized reverse engineering, and explicit cloning requests. That would help separate capability limits from policy decisions and reveal whether the change actually affects engineering productivity.