{"version":"2.1.300","anchor":"session-claim-and-rewind-stand-in-changes","canonical_anchor":"session-claim-and-rewind-stand-in-changes","heading":"Several small changes to remote sessions, rewind and resume","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/session-claim-and-rewind-stand-in-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Several small changes to remote sessions, rewind and resume\n\nRemote sessions, rewind, resume and error reporting each received small internal changes\n\n**Unclear.** What any of these changes does for a user is not known.\n\n**What**\n\nSeveral small changes touch sessions, especially remote ones that run on a machine in the cloud:\n\n- Remote sessions can now react when a session claim has been delivered.\n\n- A stand-in for rewind, going back to an earlier point in a conversation, is now stored when a setting is on.\n\n- Claude Code keeps track of which agents have given up a pinned chat.\n\n- Tasks coming from MCP, the protocol for connecting outside tools, are reported as their own kind of task.\n\n- Error reports include a deployment status.\n\n- Resuming a session passes extra details when it re-adds earlier messages.\n\n**Why**\n\nThese are small adjustments to session and remote handling.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}