{"version":"2.1.271","anchor":"background-monitor-task-now-defaults-to-expiring-instead-of","canonical_anchor":"background-monitor-task-now-defaults-to-expiring-instead-of","heading":"Background Monitor task now defaults to expiring instead of running forever","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/background-monitor-task-now-defaults-to-expiring-instead-of","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Background Monitor task now defaults to expiring instead of running forever\n\nBackground Monitor tasks now default to expiring instead of running indefinitely\n\n**What**\n\nThe 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.\n\n**Why**\n\nThis 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.\n\nOn 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.\n\n- Flag `tengu_breezy_crescent`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.271; this account: on, anonymous baseline: on, compiled default: 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.\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}