NousResearch/hermes-agent
Fix model pricing unit normalization in metadata
Cluster 79174 · agent. Data as of
2 open items. Fix merged in #112256 on 16 Sep 2026. Check it covers your case.
The short answer
0open issues
2open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #112256. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #112256. That is separate from the fix event. - Still open
- 0 issues and 2 PRs.
These items address a bug where pricing units like 'per_1m_tokens' or 'per_1k_tokens' were not properly normalized during extraction, causing inflated cost calculations and false expensive-model warnings.
Open issues0
Open PRs2
Fixes on record
-
#112256 fix(pricing): custom-provider /models prices already per-million are no longer inflated 1,000,000x (#112018, #34256, #79174, supersedes #34263 #112036)
files:
agent/model_metadata.py,tests/agent/test_model_metadata.py
Closed issues · 1
- Closed#79174fix(model_metadata): pricing with 'unit: per_1m_tokens' inflated 1Mx -> false expensive-model warning
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.50: 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
- #112256
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 16 Sep 2026