Scheduling surfaces now also require the allow_routines policy / Claude Code v2.1.227

You'll notice

Useful3 Signal3

Enterprise Settings not in their notes

Scheduling now requires the allow_routines policy as well as remote sessions.

Feature flag

tengu_surreal_dali On 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.227: 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.

Read once, for one account on one subscription tier, against v2.1.227. It isn't a statement about your account. What a flag value here can and cannot tell you

allow_routinesallow_remote_sessions

What

The cloud and scheduling prompts and the schedule command previously checked only the allow_remote_sessions policy setting. They now also check allow_routines, so an organisation that permits remote sessions but not routines will no longer be offered scheduling or given the tool.

Details

the tengu_surreal_dali flag, off unless the server enables it, still gates all of this on top of both policy settings

Evidence

allow_routines

Strings lifted out of the shipped bundle, so the claim above can be checked against them.