{"version":"2.1.246","anchor":"resuming-a-session-restores-its-accumulated-cost","canonical_anchor":"resuming-a-session-restores-its-accumulated-cost","heading":"Resuming a session restores its accumulated cost","tier":"notice","area":"Cost Tracking","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/resuming-a-session-restores-its-accumulated-cost","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Resuming a session restores its accumulated cost\n\nResuming a session picks up its running cost instead of resetting the counter to zero.\n\n**What**\n\nSession cost is now saved into the conversation transcript and read back when the session loads, so a resumed session continues from its existing spend instead of restarting the counter at zero.\n\n**Details**\n\n- The transcript's record-type table gained a cost-state entry with last-wins semantics, so the newest cost line for a session wins.\n- Malformed cost-state lines are validated on read and dropped rather than breaking the load.\n- Both loaders carry the restored cost onto the session: the full transcript read and the incremental follow-on read.\n\n**Evidence**\n\n`\"cost-state\": \"last-wins\"`\n\n- Area: Cost Tracking\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}