fix(claude): track active goal spend from assistant API messages - #471
Merged
Conversation
Accumulate per-call assistant token spend (main thread and subagent sidechains) while a goal is active, instead of deriving it from the turn result's session-cumulative usage counter. Deduplicate samples by API message id (with uuid fallback) so replays land once in the ledger; context-poll ticks no longer derive tokens from apiUsage.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tickets: none
resultusage, which the CLI reports as a session-cumulative counter that mixes pre-goal and sidechain spend into the total.apiUsagesnapshot; it only ticks the goal's elapsed time while assistant messages drive the token total.