A corrupted stats file no longer shows NaN in your usage and cost display.
What's wrong with this entry?
A corrupt or partially written stats cache no longer produces NaN in the usage display.
- After structural validation, the cache passes through a normaliser.
- Every per-model counter is coerced to a number defaulting to 0: input and output tokens, cache reads, cache creation, web search requests, cost, context window and max output tokens.
- Unrecognised model keys are dropped, as are hour buckets whose value is not numeric.
- A cache that fails structural validation still returns empty.
Stats cache has invalid structure, returning empty cache
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Extra-usage panel now shows for team and enterprise accounts
Both mention usage limit
-
v2.1.236
Wrap-up hint near the usage limit is now per-plan and once per window
Both mention usage limit
-
v2.1.236
Visible notice when approaching the 5-hour usage limit
Both mention usage limit