{"version":"2.1.321","anchor":"refusal-retry-nudge-can-be-virtual","canonical_anchor":"refusal-retry-nudge-can-be-virtual","heading":"Retry nudge after a safeguard refusal can now be marked virtual","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/refusal-retry-nudge-can-be-virtual","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Retry nudge after a safeguard refusal can now be marked virtual\n\nAfter a safety refusal, the nudge sent on retry can now be marked virtual when the refused reply produced nothing\n\n**Unclear.** It is not clear what marking the nudge as virtual changes for the user.\n\n**What**\n\nWhen a safeguard (an automated safety check) refuses a response, Claude Code retries with the same model. It also adds a nudge, which is a short note to the model about what happened. The nudge used to be an ordinary note every time. It is now marked as virtual in one case: when the refused reply produced nothing.\n\nThe usage data Claude Code records for this retry now also notes whether a nudge was sent.\n\n**Why**\n\nThis is a small change to how the retry is recorded and to how the nudge appears in the conversation record.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}