{"version":"2.1.284","anchor":"loop-self-pacing-prompt-reordered-stop-mentions-final-upda","canonical_anchor":"loop-self-pacing-prompt-reordered-stop-mentions-final-upda","heading":"Self-paced \/loop runs confirm and re-arm in a different order","tier":"notice","area":"Slash Commands","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/loop-self-pacing-prompt-reordered-stop-mentions-final-upda","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Self-paced `\/loop` runs confirm and re-arm in a different order\n\nThe instructions Claude follows when `\/loop` paces itself were rebuilt, changing when it confirms, how it re-arms and what it says on stopping\n\n**Unclear.** It is not clear what decides whether the confirmation comes before or after the next run is scheduled.\n\n**What**\n\nWhen you run `\/loop` without an interval, Claude decides itself when the next run happens. The instructions it follows for this have been rewritten:\n\n- Short confirmation: in some cases Claude confirms briefly before scheduling the next run. Otherwise it confirms after the next wakeup is set.\n\n- Cloud sessions: sessions where `CLAUDE_CODE_REMOTE` is set get extra instructions.\n\n- Stopping: the stop instructions now add a note ending with the reminder that \"a stopped loop has no next tick to surface it.\"\n\n- `loop.md` runs: Claude is told to set the next run \"again this turn\", instead of \"at the end of this turn\".\n\n**Why**\n\nThis changes the order in which Claude handles each `\/loop` step. The difference is easiest to see in how and when it reports back to you.\n\n- Area: Slash Commands\n- Names: `\/loop`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}