Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Autonomous /loop tick prompts now work for everyone

Use it now
Useful4 Signal4
Loop Mode Notable

The /loop tick prompt is no longer behind a remote flag and works for everyone.

Feature flag
tengu_kairos_loop_prompt 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.248: not a boolean we can read

tengu_kairos_loop_persistent Not enough to say

Nothing 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: on

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

/loop
What

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.

Details
  • 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, with CLAUDE_CODE_LOOP_PERSISTENT forcing it on.
Evidence

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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.248 →