fix: parse Grok Build usage logs - #45
Merged
Merged
Conversation
|
本机测试了下: 结论
|
juliantanx
marked this pull request as ready for review
July 16, 2026 03:21
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
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.
Summary
updates.jsonltotalTokenscounters into positive per-turn deltasRoot cause
Grok Build's session directory was registered in discovery, but
Aggregatorhad no parser for thegroktool. The generic JSONL parser also does not understand Grok's JSON-RPC fields or cumulative token semantics. Despite producing no records, the CLI advanced each file's watermark to EOF, preventing a later fixed version from automatically importing historical sessions.Impact
aiusage parse --tool grokand automatic parsing now import existing and newly appended Grok Build usage. Repeated/decreasing cumulative counters do not double-count tokens, multiple sessions remain isolated, and a second parse is idempotent.Grok currently exposes no stable input/output/cache split, so positive total-token deltas are recorded as input tokens.
Validation
pnpm test— 605 tests passed across core, web, widget, site, and CLIpnpm build— core, web, CLI, and widget builds passedCloses #43