Cairn
NousResearch/hermes-agent

Token usage and cost tracking fixes across providers

Cluster 32400 · agent. Data as of

Nothing open on GitHub. Fix merged in #73516 on 28 Jul 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #73516. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #73516. That is separate from the fix event.
Still open
Nothing open on GitHub.

Multiple bugs causing usage costs to report as zero or be undercounted across Gemini, Telegram, Langfuse, and other providers, addressed through billing route fixes, pricing alias resolution, and propagating cost/token fields through various code paths. Also includes a feature request for ACP session cost tracking in state.db.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #73516 feat(gemini): salvage cluster — 3.6-flash aux default, vertex catalog, direct cost tracking (fixes #32400)

    merged to main

    files: agent/usage_pricing.py, contributors/emails/[redacted:email], hermes_cli/models.py, plugins/model-providers/gemini/__init__.py, tests/agent/test_usage_pricing.py, tests/plugins/model_providers/test_gemini_profile.py

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #32404 fix(pricing): track cost for direct Gemini providers + add Gemini 3.x entries (#32400) · superseded by another PR → #31382
  • #60063 fix: support Gemini billing route mapping and pricing update · merged via another change → ecebff8, 26dd976, #73516, #32400
Closed issues · 1
  • Closed#32400Direct Gemini cost tracking is always $0.00 — resolve_billing_route() lacks gemini/google-gemini-cli branches + missing gemini-3.5-flash pricing entry
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.00 means 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 Lab

At a glance

Subsystem
agent
Merged PRs
#73516
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
28 Jul 2026

For your agent

The same facts, typed.

cluster/32400.json
cluster/32400.md