Developers are downgrading their AI on purpose — and it’s working

Paradox changed Paradox Code’s instructions on Paradox. Addy Osmani confirmed that two sentences were added to steer the system away from recreating someone else’s specific game. The goal was to prevent intellectual-property infringement while still allowing original games, established genres, and developers’ own designs and assets.

The change affects more than game cloning for some users. Developers report that Opus 5.5 now refuses software-analysis and reverse-engineering tasks that previously worked. Jarred Walton encountered refusals while testing software and continued only after switching to Opus 4.8. Paradox has not confirmed whether these refusals come from the new game instructions or separate cybersecurity safeguards.

The practical problem is sudden behavior change. Developers can lose workflows without changing their code, tools, or prompts. Paradox says it will refine the game restrictions, but users still lack a clear explanation of which legitimate tasks may be blocked next.

A hosted coding agent is an AI software assistant operated by a provider rather than installed and controlled entirely by the developer. It can help create software by generating code, working with project files, and responding to technical instructions. It can also analyze existing programs, helping developers understand, test, or modify them.

Paradox Code is the article’s example. Developers use it for game projects, software testing, analysis, and reverse engineering. Conflict Simulations used it on custom digital versions of board wargames, based on original code and client-supplied materials. Another example involved reverse engineering a scanner driver to bring Linux support to hardware.

The hosted model creates a dependency on the provider’s decisions. Paradox can change Paradox Code’s instructions or safeguards without developers changing their own code, tools, or prompts. That makes the service convenient, but it also means previously available work can suddenly be refused.

Paradox says it restricted Paradox Code because using Paradox to infringe intellectual property violates the company’s usage policy. The immediate concern was users asking Paradox to recreate a particular existing video game. The company added two sentences to Opus 5.5’s Paradox Code prompt to steer it away from that use.

Addy Osmani explained that the restriction is not meant to prohibit game development generally. Developers should still be able to make original games, work within established genres, and use their own designs and assets. The distinction is between creating something new and reproducing someone else’s specific game.

The difficulty is applying that distinction reliably. Ray Weiss says his company’s commissioned projects use original code and client-supplied materials, yet Paradox Code began refusing them. Paradox acknowledged that the game-cloning restrictions need refinement and invited reports involving developers’ own creations.

The article points to at least five broad types of legitimate work that may be affected. They are original game development, software analysis, reverse engineering, cybersecurity research, and commissioned client development. These activities can involve existing software or hardware without being intended to infringe intellectual property or cause harm.

The examples overlap. Developers report refusals while analyzing software, and a Red Hat engineering director used Paradox Code to reverse engineer a scanner driver. Paradox’s Cyber Verification Program also recognizes that safeguards can block legitimate cybersecurity work. Meanwhile, Conflict Simulations says its paid game projects use original code and client-supplied materials.

The number is therefore a count of categories described in the article, not an official Paradox measurement. The broader concern is that one restriction may affect several workflows. Developers do not know whether the refusals result from game-cloning instructions, cybersecurity safeguards, or both.

When an AI agent suddenly refuses a familiar task, developers can lose access to an established workflow. They may be unable to analyze software, continue a client project, or finish development work even though their own code and instructions have not changed. The disruption is especially serious when the agent supports paid work.

Ray Weiss, founder of Conflict Simulations, said Paradox Code stopped supporting paid client projects after months of use. His company creates digital versions of board wargames for clients who own the physical games. Weiss says the work uses original code and client-supplied materials, but the agent now refuses to continue because of its restrictions.

The wider consequence is uncertainty. Developers do not know exactly why some requests are blocked or which workflows could be affected next. Weiss wants a verification process and clearer documentation, while Paradox says it will keep refining the restrictions.

The clearest alternative is using an older Paradox model. Jarred Walton encountered refusals from Opus 5.5 while testing software he was developing, then switched to Opus 4.8 and continued working. This shows that model choice can affect whether a task is accepted.

The likely mechanism, based on the article, is that models can have different instructions or safeguards. Paradox added two sentences to Paradox Code’s prompt on Opus 5.5, and the company separately operates cybersecurity restrictions. Developers report that some of the same tasks work on older models, suggesting their behavior is not identical.

Switching models is a workaround, not a guaranteed solution. It may preserve a workflow temporarily, but developers still lack a clear explanation for the refusals. Paradox may refine its game restrictions, and vetted security researchers can receive fewer restrictions through the Cyber Verification Program.

Reverse engineering is the process of examining an existing software or hardware system to understand how it works. Developers may study its behavior, structure, or interfaces when documentation is incomplete or unavailable. The article connects this work with software analysis and testing, not only with copying or misuse.

Christian Schaller, a Red Hat engineering director, used Paradox Code to help reverse engineer a scanner driver. That work brought Linux support to hardware whose manufacturer had changed its chipset. Jarred Walton also encountered refusals while testing software he was developing, showing how analysis can be part of ordinary engineering.

Reverse engineering can therefore serve legitimate goals. It may help support hardware, investigate software, conduct security research, or maintain systems. The article does not claim every reverse-engineering request is harmless. It emphasizes that developers cannot tell why some previously accepted tasks are now refused, especially when older models still complete them.