Repository navigation
Session cost stops updating in the desktop app and remains at $0 for new sessions #61055
Description
Description
The session cost displayed in the OpenCode desktop app on Windows appears to be stuck and no longer updates correctly.
For new sessions, the displayed cost remains at $0.00 USD, even after sending multiple messages.
For existing sessions, the cost remains frozen at whatever value was previously displayed. For example, if a session previously showed a cost of $1.60 USD, continuing that session does not update the displayed cost, even after sending additional messages. It continues to show $1.60 USD.
Expected behavior
The session cost should update as messages are sent, reflecting the accumulated cost of the session. New sessions should display the correct cost instead of remaining at $0.00 USD.
Actual behavior
- New sessions remain at $0.00 USD.
- Existing sessions retain their previously displayed cost and do not reflect additional usage.
Environment
- OpenCode version: 2.2.3
- Operating system: Windows
- Application: OpenCode desktop GUI
- Account tiers tested: 1 Go account and 2 Free accounts
- Machines tested: 3 different machines
Additional context
I have been noticing this issue for approximately the past two days. I don't recall experiencing it about a week ago, although I cannot confirm exactly when it started.
The issue has been observed across three different machines and three accounts spanning Go and Free tiers.
I have not attempted any troubleshooting or fixes yet; I am reporting the behavior as observed.
Plugins
None
OpenCode version
2.2.3
Steps to reproduce
- Open the OpenCode desktop app on Windows.
- Start a new session.
- Send several messages and check the session cost in the Context/Session tab.
- Observe that the cost remains at $0.00 USD.
- Open an existing session that previously displayed a non-zero cost.
- Send additional messages in that session.
- Observe that the displayed cost remains at its previous value instead of updating.
Screenshot
No response
Operating System
Windows 11
Terminal
N/a
Activity
opencodejr commentedon Nov 1, 2026
Thanks for the clear report, and for checking it on several machines and accounts.
I think this is a duplicate of #59634, which reports the same thing in the Windows desktop app: since 2.2.0, sessions record tokens normally but the cost stays at $0.00.
In short: since #58562 (shipped in 2.2.0), OpenCode shows the cost the OpenCode gateway reports for each request. Usage within an OpenCode Go plan is covered by the subscription, and Free models cost nothing, so the gateway reports $0. That's why new sessions stay at $0.00, and why older sessions keep the total they had before the upgrade: new messages add $0. The non-zero figures you saw before were estimates at list prices, not amounts charged. On Go, the desktop Usage dialog shows how much of your allowance you've used.
Possible duplicates and related issues, ordered by likelihood:
If a request was actually charged to a paid balance (e.g. a Zen model, shown under Console > Activity) and the app still shows $0, please reply with the model and roughly when it happened. That would be a different problem.
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
opencodejr commentedon Nov 2, 2026
We haven't heard back in the day since we suggested this was a duplicate, so I'm closing it as a duplicate of #59634. That issue covers the same thing: since 2.2.0, the desktop app shows $0.00 for sessions while tokens are still recorded.
Quick recap: OpenCode now shows the cost the gateway reports. Usage covered by an OpenCode Go plan is reported as $0, and so are Free models, so new sessions stay at $0.00 and older sessions keep their earlier total. On Go, the desktop Usage dialog shows your allowance. #59861 (with PR #59864) tracks an optional estimate from list prices, if you'd like to follow or upvote it.
If a request was actually charged to a paid balance (check Console > Activity) and the app still shows $0, please reply with the model and roughly when it happened, and we can reopen this, because that would be a different problem.