tengu_breezy_crescent
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.268, including the newest one read.
Monitor tool watches can now be capped with an auto-expiring timeout instead of running forever
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.268.
In the changelogs
4Releases whose published page names tengu_breezy_crescent.
-
v2.1.287
Monitor tasks' expiring default can now be switched on without the server
A local condition can now force on the setting that makes background Monitor tasks expire, even if the server says otherwise
gate cited by this entry, found in this entry's text
-
v2.1.271
Background Monitor task now defaults to expiring instead of running forever
Background Monitor tasks now default to expiring instead of running indefinitely
gate cited by this entry, found in this entry's text
-
v2.1.268
Monitor tool gains a bounded, self-expiring watch mode (behind tengu_breezy_crescent)
Monitor tool watches can now be capped with an auto-expiring timeout instead of running forever
gate cited by this entry, found in this entry's text
-
v2.1.268
Background-monitor guidance changes wording when an experimental re-arm flag is on
Background-monitor guidance text can now mention re-arming instead of saying notifications run indefinitely
gate cited by this entry
Gate readings
3| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.287 read on another version | On for this account, and not off by default | on | on | on |
| v2.1.271 read on another version | On for this account, and not off by default | on | on | on |
| v2.1.268 | Not enough to say | no value returned | off | off |
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
16| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| this account | on | 2026-11-02T13:05:04Z | 2026-11-06T12:05:05Z | v2.1.316 to v2.1.318 |
| anonymous | on | 2026-10-17T05:30:04Z | 2026-11-06T12:05:05Z | v2.1.302 to v2.1.318 |
| this account | off | 2026-11-02T12:55:05Z | 2026-11-02T12:55:05Z | v2.1.316 |
| this account | on | 2026-11-01T20:45:05Z | 2026-11-02T12:40:07Z | v2.1.316 |
| this account | off | 2026-11-01T20:40:05Z | 2026-11-01T20:40:05Z | v2.1.316 |
| this account | on | 2026-11-01T20:25:04Z | 2026-11-01T20:30:06Z | v2.1.316 |
| this account | off | 2026-11-01T20:20:05Z | 2026-11-01T20:20:05Z | v2.1.316 |
| this account | on | 2026-10-07T18:00:12Z | 2026-11-01T19:30:06Z | v2.1.292 to v2.1.316 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | on | 2026-09-14T13:45:04Z | 2026-10-17T05:10:04Z | v2.1.270 to v2.1.302 |
| this account | off | 2026-10-07T17:59:34Z | 2026-10-07T17:59:34Z | v2.1.293 |
| this account | on | 2026-09-14T15:25:04Z | 2026-10-07T17:10:05Z | v2.1.270 to v2.1.292 |
| this account | off | 2026-09-10T21:47:12Z | 2026-09-14T14:55:05Z | v2.1.268 to v2.1.270 |
| anonymous | off | 2026-09-10T15:30:09Z | 2026-09-14T13:05:05Z | v2.1.267 to v2.1.270 |
| this account | no longer carried | 2026-09-10T21:46:45Z | 2026-09-10T21:46:45Z | v2.1.268 |
| this account | off | 2026-09-10T16:05:13Z | 2026-09-10T17:40:05Z | v2.1.267 |
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_breezy_crescent was v2.1.268, 10 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
48One 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.