{"version":"2.1.251","anchor":"resumed-sessions-repair-assistant-messages-missing-an-id","canonical_anchor":"resumed-sessions-repair-assistant-messages-missing-an-id","heading":"Resumed sessions repair assistant messages missing an id","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/resumed-sessions-repair-assistant-messages-missing-an-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Resumed sessions repair assistant messages missing an id\n\nOld sessions with malformed assistant messages now resume cleanly instead of coming back broken.\n\n**What**\n\nAssistant messages saved without an internal message id, an artifact of older stream-json input handling, are now given a generated id when a session is resumed instead of coming back broken.\n\n**Details**\n\n- Runs unconditionally on the resume path and logs how many entries it stamped.\n- Tracked upstream as issue #61940.\n\n**Evidence**\n\n`stamped a message.id on ${y} id-less assistant entr`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}