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

Claude Code v2.1.290 ·

Turn handoffs now track their age and expire after 30 minutes

A turn handoff held over 30 minutes now fails as expired, the handler now gets the handoff's age, and handoff validation was reworked

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

Unclear Only the description of the error was seen, not the code that enforces the 30-minute limit.

What

A turn handoff passes an unfinished turn and its pending tool calls to another worker in a Remote Control session. A tool call is an action Claude has asked to run, such as editing a file. This release changes how handoffs that have been waiting are handled:

  • An expired error now applies to handoff requests that the session service held for more than 30 minutes. Before, handoffs never expired.
  • The code that receives a handoff is now given its age. The age is worked out from the time the handoff was stored, from the service clock or the newest message, and from the machine's own clock.
  • Handoff checks were reworked. A tool name is now accepted if it matches an alias or a fallback set of names. An earlier pre-check that scanned the turn's tool requests and results was removed. One invalid_handoff error now says the turn does not carry the lines of its pending delivery.

Why

A handoff that has waited more than 30 minutes is now refused, so its actions do not run long after they were asked for. Remote sessions that hand off turns may now see expired or invalid_handoff errors where they saw none before.

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 doubtOnly the description of the error was seen, not the code that enforces the 30-minute limit.

See this entry in the whole of v2.1.290 →

Feedback