Repository navigation
agent-wasm: report step token counts in needTools and final outcomes - #4
Merged
Merged
Conversation
outcome_to_json dropped step.timing. Both outcomes now carry
timing: {promptTokens, thinkTokens, answerTokens}, so a page can show
per-step statistics. Times are left out (0 on wasm32); the page times
the step itself.
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.
outcome_to_json dropped each step's timing, so a page could not show the prompt size or the number of generated tokens. Both outcomes now carry timing: {promptTokens, thinkTokens, answerTokens}. Times are left out because they are 0 on wasm32; the page times the step itself. A unit test covers both outcomes, and the module doc describes the field.