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

Claude Code v2.1.307 ·

Resuming an interrupted turn in remote sessions changes what gets picked back up

Remote resumes of interrupted turns stop adopting unmatched permission requests and can add a critical reminder when something is left unresolved

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

What

A turn is one round of Claude working on your request. When a remote session (one running on a machine other than your own computer) is cut off mid-turn and later resumed, Claude Code decides what to pick back up. This release changes that in several ways:

  • Interrupted permission requests (the prompts asking you to allow an action) are resumed only when their tool_use_id, the id of the action they belong to, is among that turn's actions. The adoptUnderivable path, which could also take over requests that could not be matched this way, is removed.
  • On resumes using CLAUDE_CODE_RESUME_INTERRUPTED_TURN, Claude Code can now queue a critical_system_reminder message to Claude when an unresolved item remains. This only happens when a setting that defaults to false is turned on.
  • The code that handles tasks left behind by the interruption was reworked to read the restored worker state consistently.
  • The scheduler now passes wakeupScheduledFor when a scheduled (cron) job fires.

Why

Fewer interrupted permission prompts will be picked back up after a session moves or restarts, and Claude can be told directly when something was left unfinished. If you run Claude Code in the cloud, resumed sessions may behave a little differently around pending prompts.

Read from

See this entry in the whole of v2.1.307 →

Feedback