{"version":"2.1.268","anchor":"session-resume-now-filters-out-already-seen-message-uuids","canonical_anchor":"session-resume-now-filters-out-already-seen-message-uuids","heading":"Session resume now filters out already-seen message UUIDs","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/session-resume-now-filters-out-already-seen-message-uuids","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Session resume now filters out already-seen message UUIDs\n\nResuming a session no longer duplicates messages it has already seen\n\n**What**\n\nThe function that rebuilds conversation history when resuming a session (renamed `YMe`) now accepts an optional set of message IDs already seen. When provided, any message whose ID is already in that set is filtered out before the resumed history is saved.\n\n**Why**\n\nThis prevents the same message from being duplicated in a session's history when resuming, keeping resumed conversations accurate.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}