Under the hoodTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SDKArea: what it touches
Internal ChangesKind: in v2.1.311,
Internal ChangesSection of the release
What
Sometimes a turn is handed off from one place to another, for example from a remote or cloud session to the worker running the conversation. A turn is one round of you asking and Claude answering. The message that hands the turn over now accepts an optional field, requires_rewind_request_id. This field is marked internal. It names a rewind_conversation request the client sent earlier. A rewind takes the conversation back to an earlier point.
A worker that supports this field adds the turn only if two things are true:
The named rewind was the last rewind that worker carried out.
The conversation has not changed since that rewind.
If either is false, the turn is refused with an error that begins invalid_handoff: required_rewind_. The reason given is one of unknown, other, moved_on or lines_waiting. One message seen is "the conversation has moved on since rewind_conversation request".
Why
A turn that was meant to follow a rewind can no longer be added to a conversation that has changed in the meantime. In remote sessions, this stops an out-of-date turn from being applied after a rewind.
Read from
Names in the bundlerequires_rewind_request_idrewind_conversation
