Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Scheduled TasksArea: what it touches
Internal ChangesKind: in v2.1.323,
Internal ChangesSection of the release
What
Scheduled tasks let Claude Code run work at set times. The check that decides whether they are available has gained a term that is always true, which does not change its result. It still turns scheduled tasks off when CLAUDE_CODE_DISABLE_CRON is set, and it still consults the remote flag tengu_kairos_cron, which counts as on when the server sends nothing. In an earlier reading the flag server returned that flag on, both for this site's account and for an anonymous baseline.
Why
If you want scheduled tasks off, setting CLAUDE_CODE_DISABLE_CRON remains the switch you control.
tengu_kairos_cronOn for this account, and not off by default
The 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.323: 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.
