{"version":"2.1.284","anchor":"loop-dynamic-pacing-prompt-reorders-confirm-and-arm-steps-p","canonical_anchor":"loop-dynamic-pacing-prompt-reorders-confirm-and-arm-steps-p","heading":"\/loop has most models schedule the next run before confirming","tier":"notice","area":"Slash Commands","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/loop-dynamic-pacing-prompt-reorders-confirm-and-arm-steps-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### `\/loop` has most models schedule the next run before confirming\n\nWhen `\/loop` paces itself, most models are now told to decide and schedule the next run first and write their confirmation afterwards\n\n**Unclear.** It is not clear which models besides claude-mythos-5 keep the old order.\n\n**What**\n\nWhen `\/loop` runs without a fixed interval, Claude chooses when to run next by setting a wake-up. The order of steps in its instructions now depends on the model:\n\n- Models with a particular per-model setting turned on, which is the default for claude-mythos-5, keep the old order: confirm briefly, then set the wake-up.\n\n- Other models are told to decide whether the loop continues, set the wake-up, and only then confirm briefly.\n\nThe wording for setting the wake-up again after a task notification is reordered in the same way. Before, every model was told to write its confirmation before setting the wake-up.\n\n**Why**\n\nClaude's turn ends as soon as the wake-up is set. Setting it before writing the status text probably makes it less likely that a loop stops because the turn ended before the next run was scheduled.\n\n- Area: Slash Commands\n- Names: `\/loop`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}