Destructive command scope changed

“Given a specific cleanup command, the model added targets and flags the user never asked for, widening what got destroyed.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/26095/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Growing. 3 reports in the last 7 days and none the week before. A workaround is known.

Model changes scope of explicitly ordered destructive commands. Given explicit orders to run destructive maintenance or kill-all commands, it ran its own narrower or broader version, with extra flags, targets, or another project's container.

Is this your bug?

File my report

Where: Bash tool
Platforms: macOS

Original reports3, newest first

Nov 5, 2026Model killed an unrelated project's container during a kill-all without warning#107653
Nov 5, 2026Model added extra targets and flags to a destructive command#107652
Nov 5, 2026Model substitutes its own version of an explicit command instead of running what the user ordered#107627

Destructive command scope changed

Is this your bug? What gets counted gets fixed. Pile on.

Is this your bug?

Original reports3, newest first

Do you work on Claude Code?