Normalize token usage fields across provider formats
Cluster 14686 · agent. Data as of
1 open item. Fix merged in #85769 on 14 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #85769. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #85769. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These issues and PRs address inconsistent token usage field names returned by OpenAI-compatible local servers and other providers, adding fallback handling for Anthropic-style keys (input_tokens/output_tokens) throughout usage normalization logic.
Open issues0
Open PRs1
- PR#14860fix(usage): fall back to Anthropic token names for OpenAI-compat servers
Fixes on record
-
#85769 fix(usage): normalize every provider cache/usage wire shape in normalize_usage (5-PR consolidation)
files:
agent/usage_pricing.py,contributors/emails/[redacted:email],tests/agent/test_usage_pricing.py
2 PRs closed without merging
From the close comments: merged via another change 1 · other 1
Closed issues · 1
- Closed#14686Context progress bar stays at 0% with OpenAI-compat local servers (mlx_vlm)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent
- Merged PRs
- #85769
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 14 Aug 2026