{"version":"2.1.281","anchor":"new-model-facing-denial-text-for-rm-removals-blocked-by-the","canonical_anchor":"new-model-facing-denial-text-for-rm-removals-blocked-by-the","heading":"New model-facing denial text for rm removals blocked by the safety check","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/new-model-facing-denial-text-for-rm-removals-blocked-by-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### New model-facing denial text for rm removals blocked by the safety check\n\nWhen an rm is blocked because no one answered, Claude is told a safety check denied it and not to work around the block\n\n**What**\n\nA dangerous removal can be denied because nobody answered the approval prompt, or because the session cannot show a prompt at all. In those cases the model now receives a dedicated message. The model is the AI running the commands. The message says:\n\n- The denial came from a built-in Claude Code safety check, not from the user.\n\n- The model should not get around it by splitting the command, putting it in a script or running it again.\n\n- If it applies, the prompt has already gone unanswered a given number of times this session and was not shown again.\n\n**Why**\n\nClaude no longer mistakes an automatic block for your decision. It is also told not to find a workaround for a removal that the safety check stopped.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}