{"version":"2.1.282","anchor":"kept-reminder-scope-is-seeded-from-the-recorded-session-valu","canonical_anchor":"kept-reminder-scope-is-seeded-from-the-recorded-session-valu","heading":"Resumed sessions start from their recorded reminder setting","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/kept-reminder-scope-is-seeded-from-the-recorded-session-valu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Resumed sessions start from their recorded reminder setting\n\nA per-model reminder setting now starts from the value recorded in the session, and a server value can still replace it\n\n**Unclear.** It is not clear what the reminder is or exactly when the recorded value is used.\n\n**What**\n\nA reminder setting that Claude Code works out for each model now starts from the value recorded in your session the first time it is checked. A value sent later by the server can replace that recorded one. This only applies when using Anthropic's own API as the provider, and only when an internal switch allows it.\n\nA separate reminders setting can also come from the recorded session value now. After the `CLAUDE_CODE_SLEEPY_SNOWFLAKE` environment variable, a recorded yes or no is used as \"all\" or \"off\" before any other source is consulted.\n\n**Why**\n\nA resumed session keeps the reminder behaviour it started with.\n\n- Flag `tengu_sleepy_snowflake`: Not enough to say (read for one account on one subscription tier against v2.1.282; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}