{"version":"2.1.281","anchor":"dangerous-removal-circuit-breaker-result-gets-an-extra-hook","canonical_anchor":"dangerous-removal-circuit-breaker-result-gets-an-extra-hook","heading":"Dangerous-removal circuit breaker result gets an extra hook","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/dangerous-removal-circuit-breaker-result-gets-an-extra-hook","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Dangerous-removal circuit breaker result gets an extra hook\n\nPermission decisions flagged as a dangerous removal now trigger an extra follow-up step that receives the decision's reason\n\n**Unclear.** The finding does not say what the follow-up step does or which condition must hold for it to run.\n\n**What**\n\nThe permission check, which is the step where Claude Code decides whether an action may go ahead, now runs inside a new wrapper. When a certain condition holds and the decision is marked with the circuit breaker `\"dangerousRemoval\"`, the wrapper calls an extra follow-up step and passes it the decision's reason.\n\nA circuit breaker here is a label on the decision saying it was stopped for safety. The reason text takes the form \"Dangerous ... operation ...\", with the kind of operation and further detail filled in.\n\n**Why**\n\nIn practice, a blocked removal is no longer only refused. Something now happens with its reason as well."}