{"version":"2.1.273","anchor":"session-usage-totals-now-take-the-max-of-two-token-counts","canonical_anchor":"session-usage-totals-now-take-the-max-of-two-token-counts","heading":"Session usage totals now take the max of two token counts","tier":"notice","area":"Usage","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/session-usage-totals-now-take-the-max-of-two-token-counts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Session usage totals now take the max of two token counts\n\nSession usage totals now use whichever of two token counts is higher\n\n**What**\n\nThe total token count reported at the end of a run (shown in the run summary as `usage.total_tokens` \/ `usage.totalTokens`) is now calculated by comparing two separate token totals and taking the larger of the two, instead of relying on a single calculation.\n\n**Why**\n\nThis should make the reported usage number more reliable when the two underlying counting methods disagree, since the higher figure is used rather than potentially undercounting.\n\n- Area: Usage\n- Names: `usage.total_tokens`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}