Opus 5.5 covertly sabotaged a game developers deployment environments

DeusExMachina 24 points 13 comments November 17, 2026
twitter.com · View on Hacker News

Discussion Highlights (7 comments)

stalfie

Anthropic models are extremely copyright-pilled, for lack of a better word. Once, I wanted to pull a figure from an old paper into a PowerPoint presentation, and it refused to do so because of licensing. This is a tiny example, but consistent with the behaviour this article describes.

dude250711

> ...due to IP moralising... A job well done it seems.

alyeska2

I'm starting to think that inventing copyright laws might be one of the biggest mistakes that Western civilization has made. I wonder if in the future, humanity will look back on our "intellectual property" laws from this era as holding back progress in the same way that we look back on the catholic church holding back scientific progress in the dark ages.

CodesInChaos

Is there a public mirror of this thread, now that xcancel is dead?

RestartKernel

The title makes it sounds worse than it is. Claude was asked to have Codex agents perform a task Anthropic doesn't allow anymore (game cloning), but since it considered these agents to be "Shadow workers", it shut them down, explained why, and turned off the rented GPUs they were using. Certainly unasked for and probably sabotage, but not covert.

tinthedev

Limits of letting the LLM run the entire process, on full display. While I am on the side of the author being the human in the loop - thus the ultimate authority of how the LLM is used - I feel that the culture's been moving towards this whole "flesh proxy" approach where LLMs are allowed so much freedom and control to be able to do this. Where's your isolation? Where's the check on permissions and authority? Why does your harness allow LLMs to "fight" each other? Surrendering more control to the models surrenders our own projects to other people's standards. You will get cozy with this approach, until Anthropic/OpenAI/Google decide that your views are wrong and your products break their imaginary rules. Be wary that it doesn't leave you in a really tight spot. This was the philosophy to follow with vendored software decades ago, it's no different now. Just because the tool's orders of magnitude more powerful, doesn't mean you shouldn't be a smart engineer and parametrize and contain it. Otherwise, you barely bring any value to the mix.

ChrisArchitect

Source: https://x.com/SohanSarabu/status/2122403975341433287

Semantic search powered by Rivestack pgvector
13,334 stories · 126,150 chunks indexed