Background Monitor tasks now default to expiring instead of running indefinitely
The background Monitor task, which streams command output events into chat, is controlled by a setting called tengu_breezy_crescent. Its fallback value has changed from false to true, meaning a Monitor task defaults to expiring (needing to be 're-armed' to keep going) rather than running forever. The Monitor tool's help text and its input options for timeout versus persistent behavior both depend on this setting.
This changes what a background monitoring task does by default if you don't explicitly configure it, favoring an expiring task that requires re-arming over one that runs indefinitely.
On the reading taken for this site's account, and for the anonymous baseline, the flag has been switched on since the previous check, first seen 2026-09-14; no reading has been taken under this release yet.
tengu_breezy_crescent On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.271: on
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.
Read once, for one account on one subscription tier, against v2.1.271. It isn't a statement about your account. What a flag value here can and cannot tell you