tengu_sleepy_snowflake
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.271, including the newest one read.
New 'sleepy_snowflake' setting controls how widely kept reminders are delivered, per model and conversation
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.271.
In the changelogs
4Releases whose published page names tengu_sleepy_snowflake.
-
v2.1.282
Resumed sessions start from their recorded reminder setting
A per-model reminder setting now starts from the value recorded in the session, and a server value can still replace it
gate cited by this entry
-
v2.1.277
Reminders about kept/discarded output now default to full scope
Reminders about kept-or-discarded output now default to reaching the whole conversation instead of being off
gate cited by this entry, found in this entry's text, named in this entry
-
v2.1.277
Reminder scope defaults from off to all
Reminder-scope setting now defaults to 'all' instead of 'off' when unset
gate cited by this entry, named in this entry
-
v2.1.271
New 'sleepy_snowflake' reminder-scope control per model/conversation
New 'sleepy_snowflake' setting controls how widely kept reminders are delivered, per model and conversation
gate cited by this entry
Gate readings
3| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.282 read on another version | Not enough to say | no value returned | no value returned | not a boolean we can read |
| v2.1.277 read on another version | Not enough to say | no value returned | no value returned | not a boolean we can read |
| v2.1.271 read on another version | Not enough to say | no value returned | no value returned | not a boolean we can read |
Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.
Flag server, over time
4| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | "all" | 2026-10-17T05:30:04Z | 2026-11-06T11:00:09Z | v2.1.302 to v2.1.318 |
| this account | "all" | 2026-09-17T01:15:04Z | 2026-11-06T11:00:09Z | v2.1.274 to v2.1.318 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | "all" | 2026-09-17T01:15:04Z | 2026-10-17T05:10:04Z | v2.1.274 to v2.1.302 |
One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.
First cited
2The earliest release whose published evidence quoted tengu_sleepy_snowflake was v2.1.277, 18 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
45One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.