You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Include Token Pricing (Input/Output Cost) in GUI Model Selector Metadata #39047
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Verification
I have verified this feature hasn't been suggested before.
Description
What
Introduce real-time token pricing metadata (cost per 1 million tokens for both input and output) directly into the hover/details card within the GUI Model Selector layout.
Why this fits OpenCode
The selector currently focuses entirely on context lengths and reasoning capabilities, but it completely hides token pricing. That leads to accidental cost spikes whenever someone flips to a heavy reasoning model or dumps a massive file into context.
Checking pricing shouldn't require leaving the app or pulling up external docs mid-task. Putting input and output rates right next to context limits fixes that feedback loop and lets us make smart choices before hitting enter. This becomes increasingly relevant now that the newer models like Kimi K3 have a bigger price variation when compared to their 'previous counterparts' like GLM 5.2 etc.
Suggested Implementation
Modify the GUI model metadata overlay component to include two distinct, human-readable lines appended immediately below the Context row:
Model GLM-5.2
Provider OpenCode Go
Inputs text
Reasoning Allows reasoning
Context 1,000,000
Input Cost \$X.XX / 1M tokens
Output Cost \$X.XX / 1M tokens
For custom or local providers (e.g., Ollama / LM Studio), these fields should cleanly fall back to $0.00 / Free or omit the lines conditionally based on the provider config schema.
Activity
github-actions commentedon Sep 27, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.