{"version":"2.1.251","anchor":"cloud-schedule-suggestion-is-no-longer-behind-its-old-experi","canonical_anchor":"cloud-schedule-suggestion-is-no-longer-behind-its-old-experi","heading":"Cloud-schedule suggestion is no longer behind its old experiment flag","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/cloud-schedule-suggestion-is-no-longer-behind-its-old-experi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Cloud-schedule suggestion is no longer behind its old experiment flag\n\nThe suggestion to turn a loop into a cloud schedule no longer needs its old experiment.\n\n**What**\n\nThe prompt that suggests turning a session-local loop into a durable cloud schedule used to require the `tengu_surreal_dali` experiment. That name no longer appears anywhere in this build; the suggestion is now gated by two other checks combined with the existing remote-sessions policy check.\n\n**Details**\n\n- The remaining conditions are the account policy allowing remote sessions and there being no existing schedules.\n- What the two replacement checks test is not determinable from the build, so whether this is now on for everyone eligible or moved behind another gate is open.\n\n**Evidence**\n\n`## Offer cloud first`\n\n- Flag `tengu_surreal_dali`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.251; this account: on, anonymous baseline: on, compiled default: not a boolean we can read)\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}