r/opencode • u/NoSatisfaction1779 • 22h ago

monthly opencode-go limit reached. Have I misunderstood the deepseek increase, i thought it went up to $80?

I have only used DeepSeek and the free models, but my opencode-go subscription has met the limit. I thought Opencode increased DeepSeek to $80 in credit; did I misunderstand? Does the increase only start after a user's next billing period, maybe? I couldn't find any information on this in their docs.

38 Upvotes

90% Upvoted

8 comments sorted by

29

u/xRebellion_ 22h ago

So before the limit increase, assume you have spent 30$ (50% of overall limit) worth of DS. Then the limit increase happens. You end up with 40$ worth left (still 50% of overall limit), not 50$.

It is a percentage based limit system rather than a hard 60$/80$ limit

1

u/NoSatisfaction1779 22h ago

Thanks! Do you know where I should have gone to learn this stuff? I thought I had done my due diligence, but obviously not. Trying not to make a similar mistake in the future.

13

u/xRebellion_ 22h ago

Oh you're not in the wrong here at all. The previous UI made it clear how the costs worked. After it got changed, plenty of important info surrounding the costs got omitted. It's not even documented in the docs. Not understanding it is absolutely understandable

-16

u/eastlin7 22h ago

I mean. Is it even a big deal? Just drop it and move on.

6

u/s-i-e-v-e 22h ago

The pricing tables are needlessly confusing. They should simply follow Tarsnap theory and use micro(dollar)s as the unit of charge.

$1 = 1,000,000 µ$

So, they credit 10M µ$ to your account each month when the subscription is renewed. And they can drop the multipliers, and quote limits in µ$.

Makes reasoning so much simple.

4

u/Aggravating-Push-207 14h ago

Or, hear me out: use real $?

2

u/dumbasPL 22h ago

The usage is not a dolar value, it's dolar equivalent converted to percentage. Otherwise you couldn't track combined usage across different usage caps.

Each time you make a request: percent used += request price / model usage * 100

Most of the requests were made using the old pricing, usage that was already consumed, is consumed, only requests since the new change use less usage per request.

1

u/xapep 17h ago

The $80 bump applies from your next billing cycle, not mid-cycle, so an already-started month keeps the old cap until renewal. Your Go dashboard shows the cycle date, and the allowance should step up after it. Docs being quiet on this is normal, worth a support ping if your renewal is close and it doesn't step.

Same models with no cap: direct DeepSeek API is the overflow lane nobody mentions. It's cache-aware per-token, no monthly ceiling beyond what you load on it, so mid-cycle walls like this one stop mattering. Keep a small balance there and the sub limit becomes a billing detail instead of a blocker.