{"version":"2.1.302","anchor":"session-cost-state-now-persisted-and-restored","canonical_anchor":"session-cost-state-now-persisted-and-restored","heading":"Session cost totals are now saved so they can be restored","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/session-cost-state-now-persisted-and-restored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Session cost totals are now saved so they can be restored\n\nClaude Code now saves a session's running cost and restores it, keeping the saved total when it is at least as high as the current one\n\n**What**\n\nClaude Code keeps a running total of what a session has cost. It now saves that total, with its details, alongside the session's other internal information. Previously it sent only the overall cost and the token counts. A token is the small unit of text the model reads and writes, and usage is counted in tokens.\n\nWhen the saved cost record is restored, Claude Code keeps it only if two things are true:\n\n- its total cost is at least as high as the current total\n\n- the record is within a size limit\n\nThe cost figures are also now sent only when they change, rather than every time.\n\n**Why**\n\nA session's cost total can carry over when you resume the session or when the process running it restarts, instead of being lost.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}