{"version":"2.1.271","anchor":"new-sleepy-snowflake-reminder-scope-control-per-modelconv","canonical_anchor":"new-sleepy-snowflake-reminder-scope-control-per-modelconv","heading":"New 'sleepy_snowflake' reminder-scope control per model\/conversation","tier":"soon","area":"Reminders","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/new-sleepy-snowflake-reminder-scope-control-per-modelconv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### New 'sleepy_snowflake' reminder-scope control per model\/conversation\n\nNew 'sleepy_snowflake' setting controls how widely kept reminders are delivered, per model and conversation\n\n**Unclear.** Nothing has been read yet about how the tengu_sleepy_snowflake gate is currently set for this site's account, so no statement is made about whether it's active.\n\n**What**\n\nA new mechanism decides, separately for each model and each conversation, whether \"kept reminders\" are delivered at one of three scopes: `threads`, `all`, or `off`. It can be configured through the `CLAUDE_CODE_SLEEPY_SNOWFLAKE` environment variable, through a client-data map keyed by model pattern, or through a growthbook gate, and it only applies when using Anthropic's first-party API.\n\n**Why**\n\nThis gives finer control over how often reminders (contextual notes Claude Code injects) reach the model, which can affect how much reminder-related content shows up depending on your model and conversation setup.\n\n- Flag `tengu_sleepy_snowflake`: Not enough to say (read for one account on one subscription tier against v2.1.271; 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: Reminders\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}