anomalyco / anomalyco/opencode

[FEATURE] Where are token costs even being derived from?

Open
#45,340 0 comments 0 reactions 1 assignee View on GitHub

@MrMushrooooom is already working on this.

Since Aug 26, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Feature hasn't been suggested before.
  • I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request

Howdy. I use two-sessions for about 10 hours a day. Usually DeepSeek V4. The running cost across the last two months was $1 per day. I can track this in my session logs and how often I refill my credits (e.g. $20 spend).

Last week, OpenCode ran a "2x" special (half price tokens). DeepSeek V4 is also known for its token caching.
I went weeks at a time before refilling $20. Last Monday, we rebuilt succeeded in our own automation and security framework to future-enable code generation automation. We even wrote an SDK for OpenCode.

And then, starting last Monday, costs have skyrocketed by 10x.

I subscribe to the developer newsletters and customer newsletter: no updates, no notices, no information.
Here is a new typical reality: half-way through the day and $4 in the tank. Less than 1M tokens, even.
I have dozens of screenshots where the same setup cost us pennies on the dollar, not $4, typically $0.20.

We have no accountability or transparency with OpenCode. Please provide a mechanism to update us of your downstream supplier changes. We continue to ask, and continue to politely follow the channels you prescribe.

OpenCode is not viable as a codegen automation tool under these circumstances.
Honestly, what else do you expect us to take away from the experience of the last four years? Thanks.

OpenCode is a product I will pay $4 a week to use for 2 sessions running 10 hours a day.
OpenCode is not a product I will pay $4 an hour to use. And we received no updates on this price change.
There are not many options left here but rudeness after good faith efforts continually are broken down.
Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.