Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.284entry #125

Claude Code v2.1.284 ·

Self-paced /loop runs confirm and re-arm in a different order

The instructions Claude follows when /loop paces itself were rebuilt, changing when it confirms, how it re-arms and what it says on stopping

You'll notice Improvements
JSON All of v2.1.284
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Slash CommandsArea: what it touches
ImprovementsKind: in v2.1.284,
ImprovementsSection of the release

Unclear It is not clear what decides whether the confirmation comes before or after the next run is scheduled.

What

When you run /loop without an interval, Claude decides itself when the next run happens. The instructions it follows for this have been rewritten:

  • Short confirmation: in some cases Claude confirms briefly before scheduling the next run. Otherwise it confirms after the next wakeup is set.
  • Cloud sessions: sessions where CLAUDE_CODE_REMOTE is set get extra instructions.
  • Stopping: the stop instructions now add a note ending with the reminder that "a stopped loop has no next tick to surface it."
  • loop.md runs: Claude is told to set the next run "again this turn", instead of "at the end of this turn".
Why

This 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.

Read from
Names in the bundle/loop
Since it was published

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.

Confirmed since Anthropic's documentation has since written up /loop, on Hooks reference. * A [scheduled task](/docs/en/scheduled-tasks) firing, including a `/loop` iteration hooks see the edit
Added since A small documentation edit on Run prompts on a schedule touched a line naming /loop after this was published. * When you resume a session with `claude --resume` or `claude --continue`, Claude Code restores the tasks scheduled with `CronCreate`, except recurring tasks that have [expired](#seven-day-expiry) and one-shot tasks whose scheduled time ha… scheduled-tasks see the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what decides whether the confirmation comes before or after the next run is scheduled.
Anthropic's documentation agreesA small documentation edit on Run prompts on a schedule touched a line naming /loop after this was published.
Anthropic's release notes agreeFixed /loop status updates in self-paced mode often not being shown because Claude wrote them only in its reasoning; Claude now writes each…

See this entry in the whole of v2.1.284 →

Feedback