{"version":"2.1.282","anchor":"cost-tracker-snapshots-now-keep-restored-token-counts","canonical_anchor":"cost-tracker-snapshots-now-keep-restored-token-counts","heading":"Restored sessions now keep their token counts","tier":"notice","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/cost-tracker-snapshots-now-keep-restored-token-counts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Restored sessions now keep their token counts\n\nWhen a session's cost figures are saved and restored, token totals now come back along with the cost\n\n**Unclear.** Where the restored token count is shown is not known.\n\n**What**\n\nClaude Code keeps a running record of what a session has used. When that record is saved and later restored, for example on resuming a session, it now carries the token count (tokens are the small chunks of text the model reads and writes, and the unit usage is measured in) as well as the cost in dollars. Before, only the cost was restored.\n\n**Why**\n\nToken totals may no longer start again from zero after you resume a session.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}