# NousResearch/hermes-agent · Fix token counting for base64 images in tool output

## Open now

- Nothing open on GitHub.

These issues and PRs address a bug where base64-encoded images in Responses API function_call_output are incorrectly counted as raw text, inflating context/token estimates. The work focuses on correcting the pricing and estimation logic for such images.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #115793. Verify it addresses your case.
- **Recommended:** read PR #115793 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-115793`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: the share of member 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.

## Closed / duplicate issues

- #108320: Token estimator counts base64 images in Responses function_call_output.output as text

## Prior & competing PRs

- **#115793: fix(agent): Responses tool-result images no longer inflate the context estimate by their base64 length (#108320, salvage #108330)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `agent/model_metadata.py`, `tests/agent/test_model_metadata.py`
- **#108330: fix(agent): price Responses function_call_output images flat, not as base64 text**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `9168bba62555`, `#115793`, `#108320`, `#108330`
- **#108331: fix(agent): count Responses tool output images correctly**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#108330`

## Fix status

- Merged to main in PR #115793 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-19`.