You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.288,
ImprovementsSection of the release
What
The rewind_conversation request, which takes a conversation back to an earlier message, now waits for any turn that is being stopped to finish settling before it cuts anything. It also refuses, with the reason state_changed, when the saved records of the conversation it needs are no longer on disk.
The saved conversation history now keeps track of rewrites that are still pending and of records that have been deleted. Separately, when a Send-now action interrupts a turn, the message where the conversation is cut is marked as having been interrupted that way.
Why
These checks make rewinding in remote sessions safer against two things happening at once, such as a rewind arriving while a stop is still in progress.
Read from
Names in the bundlerewind_conversation
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 doubtWhat the Send-now interruption mark changes for a user is not known.
