When a user sets up a long-interval loop (≥60 minutes or daily cadence), Claude would offer to run it as a cloud-based scheduled task instead of a local session loop.
Feature-flagged via tengu_surreal_dali (defaults to false)
- Generates a conditional prompt offering cloud-based scheduling as an alternative to local loops
- Explains that daily-cadence loops won't fire before the session closes
- Provides guidance on using the
/schedulecommand for cloud execution - Includes differentiation text: "Runs until you close this session · For durable cloud-based loops, use /schedule"
Cloud scheduling offer (gated by tengu_surreal_dali, search for "Offer cloud first")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_surreal_dali 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.101: no gate table built for this version
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.101. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.