Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.307entry #28

Claude Code v2.1.307 ·

SDK hosts can tell scheduled wakeups from user prompts and see requeued prompts

Command start messages to SDK hosts now say when a run was woken by /loop or a schedule, and interrupt replies list prompts put back in the queue

Use it now Improvements
JSON All of v2.1.307
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
AgentsArea: what it touches
ImprovementsKind: in v2.1.307,
What probably matters to youSection of the release
What

These changes affect programs that drive Claude Code through the SDK or the streaming JSON protocol, rather than people typing in the terminal. Such a program is called a host.

Two messages Claude Code sends to the host carry more detail:

  • The message saying a command has started now includes wakeup_source, set to loop_wakeup or schedule_wakeup, and scheduled_for. A host can tell a run that /loop or a scheduled task woke up apart from a prompt a person sent.
  • The reply to an interrupt now includes put_back, a list of the prompt IDs the interrupt returned to the queue. This happens for prompts sent with requeue_if_interrupted_within_ms, which asks Claude Code to queue a prompt again if it is interrupted within that many milliseconds.

Claude Code announces support for these in the system message it sends when a session starts.

Why

Hosts that keep an idle session open so /loop can wake it get a precise signal for why a run began, and can see which prompts an interrupt did not throw away.

See this entry in the whole of v2.1.307 →

Feedback