{"version":"2.1.281","anchor":"reminder-delivery-override-and-credit-retry-awareness","canonical_anchor":"reminder-delivery-override-and-credit-retry-awareness","heading":"Reminder delivery override and credit-retry awareness","tier":"internal","area":"System Reminders","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/reminder-delivery-override-and-credit-retry-awareness","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Reminder delivery override and credit-retry awareness\n\nReminder delivery can now be forced with deliveryOverride, and the decision also sees creditRetryStateless\n\n**Unclear.** The finding does not say what sets `deliveryOverride` or what `creditRetryStateless` and `reminderFold` represent.\n\n**What**\n\nClaude Code decides when to deliver reminders, which are extra notes added to a conversation. Three changes affect that:\n\n- `deliveryOverride` can now force the delivery decision\n\n- The deciding step now also receives `creditRetryStateless`\n\n- Copies of a request now also carry a `reminderFold` field\n\n**Why**\n\nReminder delivery can now be set directly instead of always being worked out, and the decision can take a credit-related retry into account.\n\n- Area: System Reminders\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}