feat: per-turn ledger — time, tokens, cost per user turn - #37
Merged
Conversation
Session summary gains a table with one row per user turn: wall-clock from the user message to the last agent message of the turn, tool calls and errors, input/output/cache tokens and cost summed from assistant usage, with bars scaled to the session maximum so the expensive turn is visible before reading any number. Rows jump to the originating user message. buildTurnLedger lives in lib/pure.ts (also bundled into public/js/pure.js); unit tests cover attribution, content-part tool calls, both cost shapes, total_tokens-only platforms, and the no-usage case.
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.
Session summary gains a table with one row per user turn: wall-clock from
the user message to the last agent message of the turn, tool calls and
errors, input/output/cache tokens and cost summed from assistant usage,
with bars scaled to the session maximum so the expensive turn is visible
before reading any number. Rows jump to the originating user message.
buildTurnLedger lives in lib/pure.ts (also bundled into public/js/pure.js);
unit tests cover attribution, content-part tool calls, both cost shapes,
total_tokens-only platforms, and the no-usage case.