Context token count greatly underestimated

[G-Guillard]

Description

I'm not sure whether I'm misunderstanding the meaning of the context window "tokens" count (couldn't find much information about it) or if the count is plainly wrong. For a single session, today, with Qwen3.5 via OpenRouter, the TUI "Context" window showed :

Context
98,607 tokens
38% used
$2.04 spent

$ 20/M tokens seemed quite expensive, so I checked the OpenRouter dashboard, which tells a different story :

Plugins

No response

OpenCode version

1.14.22

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

Linux MX-23.6_ahs_x64 Libretto October 15, 2023

Terminal

xfce4-terminal 1.1.3

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Multi-step tool calls overwrite token counts instead of accumulating (output, reasoning, cache.write lost) #21913: Token counts are overwritten instead of accumulated in multi-step tool calls, leading to underreported token usage in the TUI
• Price Mismatch: Terminal reports $0.07 while Web Dashboard reports $0.09 #20883: Cost/price mismatch between the terminal display and external provider dashboards (same symptom of incorrect cost tracking)

If your issue is distinct from those, feel free to clarify the differences.

[lucaspar]

I see the same thing, and a similar ratio: OpenRouter reports ~20x more tokens than OpenCode.

A 50% difference is one thing, but 20 (or 30) times off makes that counter useless.

---

I see that despite having different token counts, the costs are similar. Maybe OpenCode is measuring the size of the current context window (how many tokens will be sent in the next request), and OpenRouter measures the sum of all tokens that were sent in previous requests?