{"version":"2.1.248","anchor":"autonomous-loop-tick-prompts-now-work-for-everyone","canonical_anchor":"autonomous-loop-tick-prompts-now-work-for-everyone","heading":"Autonomous \/loop tick prompts now work for everyone","tier":"use","area":"Loop Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/autonomous-loop-tick-prompts-now-work-for-everyone","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Autonomous \/loop tick prompts now work for everyone\n\nThe \/loop tick prompt is no longer behind a remote flag and works for everyone.\n\n**What**\n\nThe 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`.\n\n**Details**\n\n- 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.\n- The separate persistent-loop switch is unchanged: still off by default under `tengu_kairos_loop_persistent`, with `CLAUDE_CODE_LOOP_PERSISTENT` forcing it on.\n\n**Evidence**\n\n`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.`\n\n- Flag `tengu_kairos_loop_prompt`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.248; this account: on, anonymous baseline: on, compiled default: not a boolean we can read)\n- Flag `tengu_kairos_loop_persistent`: Not enough to say (read for one account on one subscription tier against v2.1.248; this account: no value returned, anonymous baseline: no value returned, compiled default: off)\n- Area: Loop Mode\n- Names: `\/loop`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}