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

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 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, 28 Sep 26

ImprovementsSection of the release

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

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 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 →

The build it came inv2.1.284

28 Sep 2026 · 328 entries, this one is #125.

Use it now18
You'll notice199
Nothing to try yet25
Under the hood86

Either side of it

v2.1.283Older

Open the release →

Names in this entry

slash/loop
Skill. Run a prompt repeatedly while the session stays open. Omit the interval and Claude self-paces between iterations. Omit the prompt and Claude runs the built-in maintenance prompt or your loop.md. Example: /loop 5m check if the deploy finished. See Run prompts on a schedule. Alias: /proactive
envCLAUDE_CODE_REMOTE
Remote sessions started from review can skip writing some state to disk.
settingloop.md
Your loop.md can come from stored state when a storage handle is available, otherwise from disk.

Anthropic's note

Upstream's own release notes for v2.1.284 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Fixed /loop status updates in self-paced mode often not being shown because Claude wrote them only in its reasoning; Claude now writes each update, and the outcome when the loop stops, as visible text

Is this right?