The code that turns a loop marker back into a "tick" instruction for the model was previously off unless remote config switched on tengu_kairos_loop_prompt. That flag is gone from this build and the tick prompt is now built for anyone using /loop.
- Both the marker handler and the loop.md resolver used to return nothing when the flag was off; they now only check that the incoming prompt is one of the loop markers.
- The separate persistent-loop switch is unchanged: still off by default under
tengu_kairos_loop_persistent, withCLAUDE_CODE_LOOP_PERSISTENTforcing it on.
Run the autonomous check using the loop instructions established earlier in this conversation. If you cannot find them, treat this as a no-op tick.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_kairos_loop_prompt 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.248: not a boolean we can read
tengu_kairos_loop_persistent Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.248: off
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
| [`/loop`](/docs/en/scheduled-tasks) | The current CLI session | Quick polling while a session is open. `--resume` and `--continue` restore unexpired fixed-interval loops. |common-workflows see the edit
| | [Cloud](/docs/en/routines) | [Desktop](/docs/en/desktop-scheduled-tasks) | [`/loop`](/docs/en/scheduled-tasks) |desktop-scheduled-tasks see the edit
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.
Anthropic's documentation has since written up /loop, on Schedule recurring tasks in Claude Code Desktop.
Changed /loop: self-paced dynamic mode and the no-prompt autonomous default are now always available, including on Bedrock/Vertex/Foundry