{"version":"2.1.287","anchor":"tengu-breezy-crescent-gate-now-has-an-extra-override","canonical_anchor":"tengu-breezy-crescent-gate-now-has-an-extra-override","heading":"Monitor tasks' expiring default can now be switched on without the server","tier":"notice","area":"Monitor Tool","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/tengu-breezy-crescent-gate-now-has-an-extra-override","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Monitor tasks' expiring default can now be switched on without the server\n\nA local condition can now force on the setting that makes background Monitor tasks expire, even if the server says otherwise\n\n**Unclear.** It is not clear what the local condition checks, or when it is true.\n\n**What**\n\nThe remote setting `tengu_breezy_crescent`, which decides whether background Monitor tasks expire and need to be re-armed instead of running forever, could be turned off by the server. It now has a second route: if a separate local condition is true, it is treated as on whatever the server says. Otherwise Claude Code falls back to the server's answer, which is on unless the server sends otherwise.\n\n**Why**\n\nIn some situations the expiring behaviour now applies regardless of remote configuration, so it can no longer be switched off from the server in those cases.\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.287; 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: Monitor Tool\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}