-
Notifications
You must be signed in to change notification settings - Fork 386
evals: record the synthetic user's tokens, not just its cost #1645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
tawnymanticore
merged 2 commits into
dchiang/eb-v2-merge
from
fix/evalrun-synthetic-user-usage
Aug 20, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Persisting the full
Usagehere is right, but it silently changes what the score-summary rollup reports.scored_trace_usageinapp/desktop/studio_server/eval_api.pysumssynthetic_user_usageinto the per-trace figure null-tolerantly, and its docstring is explicit that it was written against a cost-only field: "Today that field carries cost only, so token counts pass through from the assistant side." Once this field carries tokens and latency, three things change in the run-config usage summary with no code in this diff touching them:total_llm_latency_mson the usagerespond()now returns,Usage.__add__sums latency across the drive's turns, and the summary blend sums it again into the agent's figure.usagebut agent-only tokens — the same summary field reads two different quantities depending on record age.Cost blending is total-spend semantics and matches the legacy records. Token and latency blending conflates two models, which is the exact conflation this PR argues against. Suggest making
scored_trace_usageblend cost only (e.g. addUsage(cost=trace.synthetic_user_usage.cost)rather than the whole object) and updating its docstring in this PR, since this PR is what changes the field's contents. If blending everything is the intent, the docstring and PR description should say so instead.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed and fixed in
09751db7. You're right on all three counts, and the magnitude is worse than it reads — measured on the exact shape this branch now writes (agent 100 in / 50 out / 4000ms, SU 3548 in / 61 out / 9000ms):Input tokens 36×, latency 3.25×, both attributed to the agent under test — the exact conflation
synthetic_user_usageexists to undo, reappearing one layer up in the rollup. And silently: nothing in the diff touchedeval_api.py, which is what made it worth catching at review rather than in a dashboard.Taken your suggestion exactly —
scored_trace_usagenow addsUsage(cost=trace.synthetic_user_usage.cost)rather than the whole object, and the docstring says why per quantity:usage.cost / total_tokensmeaningless.Your third point — that blending everything gives one field two meanings by record age — is the one I'd have been most likely to miss, and it's called out in the docstring now so the next person changing this field sees the constraint.
Two tests pin the boundary: cost blends while tokens and latency stay agent-only, and an SU record carrying tokens but no cost leaves the total untouched.
Generated by Claude Code