{"version":"2.1.246","anchor":"rewind-now-refuses-more-precisely-when-the-client-is-behind","canonical_anchor":"rewind-now-refuses-more-precisely-when-the-client-is-behind","heading":"Rewind now refuses more precisely when the client is behind","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/rewind-now-refuses-more-precisely-when-the-client-is-behind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Rewind now refuses more precisely when the client is behind\n\nA refused rewind now says \"unseen later turn\" instead of a vague stale-target message.\n\n**What**\n\nA rewind request can now include the id of the last user message the client actually saw. If turns exist after the rewind point that the client has not seen, the refusal says \"unseen later turn\" rather than the old catch-all \"stale target\".\n\n**Details**\n\n- A prompt that is queued but has not started is now refused separately as \"prompt pending\".\n- The queue check counts the drainable main-thread queue rather than testing a boolean for pending user intent.\n- Unconditional in this build.\n\n**Evidence**\n\n`last_seen_user_message_uuid`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}