{"version":"2.1.277","anchor":"session-resume-now-restores-accumulated-cost-from-history-fi","canonical_anchor":"session-resume-now-restores-accumulated-cost-from-history-fi","heading":"Session resume now restores accumulated cost, tracked separately","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/session-resume-now-restores-accumulated-cost-from-history-fi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Session resume now restores accumulated cost, tracked separately\n\nResuming a session now restores its previously accumulated cost as its own tracked value, separate from unknown-model-cost tracking\n\n**What**\n\n- When resuming a session with a `history_file`, the resume path now reads and restores a `restoredCostUsd` value from that file instead of ignoring cost on resume.\n\n- The cost-tracking snapshot\/restore mechanism now stores a distinct `restoredCostUSD` value alongside `hasUnknownModelCost` (previously both were packed into the same internal field), and `reset()` now explicitly zeroes the restored value.\n\n- The cost-tracking class gained a `restoredCostUSD()` accessor and internal counter, and the cost-state schema's `totalCostUSD` now has a floor instead of being unconstrained.\n\n**Why**\n\nRestoring accumulated cost correctly when resuming a session keeps the cost totals shown to the user accurate across resumes, instead of resetting or being conflated with the separate tracking of cost from an unknown model.\n\n- Area: Sessions\n- Names: `restoredCostUsd`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}