Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.292entry #221

Claude Code v2.1.292 ·

/loop wake-ups record when the chain started and what triggered them

Scheduling the next /loop wake-up now records when the loop chain started, whether a keepalive triggered it, and which tool call scheduled it

Under the hood Internal Changes
JSON All of v2.1.292
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
LoopArea: what it touches
Internal ChangesKind: in v2.1.292,
Internal ChangesSection of the release
What

/loop runs a task repeatedly, waking up at intervals. Scheduling the next wake-up has been reworked. It now records:

  • when the chain of wake-ups started
  • whether the wake-up came from a keepalive
  • which tool call scheduled it

Before, the wake-up was built directly as a timed schedule entry without this information.

Why

This is an internal rework of how /loop schedules itself. It does not show a visible change in how loops behave.

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 Claude Code changelog. * Reverted the 2.1.290 fix for cloud sessions staying asleep after a container restart lost a pending `/loop` wakeup or scheduled task; Claude is no longer told, and the session stays asleep changelog see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /loop, on Claude Code changelog.
Anthropic's release notes agreeFixed a background session's /loop silently stopping when the session's process restarted (for example after a crash), because its pending…

See this entry in the whole of v2.1.292 →

Feedback