Repository navigation
Handle Claude Code background result sequences - #186
Merged
Merged
Conversation
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.
Claude Code can emit several indexed results as background tasks finish. The parser previously rejected these streams, dropping reported cost and marking tool counts incomplete. Validate the session and result sequence, read cumulative cost/model totals once, and aggregate turn-local usage without double counting.
Preserve lower bounds for malformed streams, mixed sessions, incomplete tails, contradictory totals, and missing request evidence. Empty background notifications retain accumulated API duration. Legacy token totals and tool enumeration use the same stream interpretation.