Resuming a session picks up its running cost instead of resetting the counter to zero.
What's wrong with this entry?
Session cost is now saved into the conversation transcript and read back when the session loads, so a resumed session continues from its existing spend instead of restarting the counter at zero.
- The transcript's record-type table gained a cost-state entry with last-wins semantics, so the newest cost line for a session wins.
- Malformed cost-state lines are validated on read and dropped rather than breaking the load.
- Both loaders carry the restored cost onto the session: the full transcript read and the incremental follow-on read.
"cost-state": "last-wins"
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.239
Cost is computed as a multiplied token subtotal plus web search
Both mention cost tracking
-
v2.1.242
Cost summary can note that figures use your organization's rates
Both mention cost