Opus 5.5 refuses to delete repo history even with user consent, sparking confusion
Angaisb_ · x · 2026-10-16
A user complains that Opus 5.5 won't perform a delete action even with explicit consent. The screenshot shows the model's reply: wiping repo history permanently deletes data (old file versions), so "that's an action I have to leave to you even when you ask" — instead it provides a command with a Run button, keeping every current file intact and removing only old versions.
A textbook case of conservative AI guardrails: the model hands destructive actions back to the user rather than executing them, leaving the user baffled.
More from Fun
- Passenger uses Grok Imagine to fake kissing videos of seatmates, then tells them to butt out — shakoistsLog · 2026-10-16
- Interp-circle joke: solving interpretability would have found the 'jhana neuron' — EigenGender · 2026-10-16
- Dev uses Claude to draw animated mascot GIFs frame-by-frame in code until usage runs out — jeremy_goldberg · 2026-10-16
- Fleuret: submission caps would cut conference papers 75%; reply recalls the 100-phone Pokémon Go bike — ducha_aiki · 2026-10-16
- New Eval Is Just Asking an LLM Judge to Rate a Trace 1-100 — stochasticchasm · 2026-10-16
- Researcher's AI calendar assistant fails at simply declining a meeting invite — BlancheMinerva · 2026-10-16