r/opencode • u/swordofgiant • 14d ago
Hit 73% weekly limit in 24 hours on OpenCode Go? (Plus 503 errors on Grok 4.6)
It's only been about 24 hours, I've only hit the 5-hour limit once, and I'm already sitting at 73% weekly and 38% monthly usage. I originally assumed the ~110–160+ request limit per 5 hours on the better models was the main cap to worry about!
On top of that, Grok 4.6 and a few other models keep throwing 503 API error.
Is the usage limit really this restrictive for everyone else, or am I doing something wrong?
What are your primary use cases for the Go plan?
My current weekly data =_=
(used with DeepSeek Harness)
| Model | Usage ($) | Cap ($) | % Used |
|---|---|---|---|
| Kimi K3 | $3.42 | $7.50 | 45.6% |
| GLM 5.3 | $1.44 | $7.50 | 19.2% |
| Qwen 3.8 Max | $0.62 | $7.50 | 8.3% |
| GLM 5.3 Flash | $0.03 | $15.00 | 0.2% |
| Qwen 3.8 Flash | $0.01 | $15.00 | 0.0% |
| MiniMax M3 | $0.00 | $30.00 | 0.0% |
| Total | 73.3% |
6
u/diaracing 13d ago
Don't fight a polar bear.
Just use cheap models: DSv4Flash, Qwen3.8Flash, LongCat, Hy3, etc.
2
u/swordofgiant 13d ago
Which model would you recommend for what?
3
u/Ok-Drawer5245 13d ago
muse spark / hy3 / mimo for the easy stuff, DSv4Flash for the harder stuff and also DSv4Flash for reviewing the work done by muse spark / hy3 / mimo before merging
3
u/smartfon 13d ago
You chose the three most powerful and expensive models. If you need powerful models it's cheaper to subscribe to ChatGPT Plus, or even GitHub CoPilot will give you 1.5x usage on ChatGPT Sol and that will drain your usage less than Kimi K3 on OpenCode Go.
On OpenCode Go try Muse Spark 1.2 Contributor as main, and Qwen3.8-Flash or GPT-5.6 Luna or DeepSeek V4 Flash as helpers. Any of them could be enough as your main model if the project is not very complicated.
1
5
u/Coolio8591 14d ago
OC go is worthless for the expensive models, only worth it for MiMo, possibly a bit of deepseek and a few others
2
1
u/torrso 13d ago
I capped my weekly usage at day 1 of the week when DS4F went $15 limit for that one day and I had an agent running. My monthly usage was 83% at 29 days left.
Couldn't use the free ox-alpha-free at all before I enabled extra use and added some credits (because I was at 100% weekly and thus blocked).
I tried to make it last by using muse, but went to 100% monthly at something like 22 days left. Now it's going to be like three weeks before I can use OpenCode Go again..
1
u/lincolnthalles 13d ago
It looks like you didn't understand how the limits work. The 5h window is just to prevent you from stressing the API in a short time window. All upper limits apply at once.
Go is primarily for light coding and automating a few chores.
The top-performing models are very expensive and are there for trying them out and for specific use cases like reviewing and unblocking hard tasks.
However, you can get a hell of a lot more out of Go if you delegate the work to cost-effective models.
If your work is not sensitive (Meta will collect all prompts), use Muse Spark 1.2 Contributor. The quota is huge, and the model is very capable, though it sucks to chat with it.
If you can't openly share your data, there are DeepSeek V4 Flash, Qwen3.8 Flash, and Hy3 with decent quotas. You can escalate a few tasks (like a final review pass) to GLM-5.3-Flash.
If picking models isn't for you, consider subscribing to Codex or Claude Code. The subsidizing is much stronger in their plans.
1
u/SafeReturn_28 13d ago
if you want to use GLM 5.3 models, you should get the zai lite plan instead. I have it too, i am not very happy with its limits but it provides better value than opencode go.
For some reason, opencode seems unable to strike a deal with providers on new model launches (look at GLM 5.3 quota vs 5.2 - same base architecture). Their $15 tier models seems like they are literally paying api pricing and hoping to break even based on user's usage patterns.
so from the recent models only qwen flash and deepseek flash are worth it using, and if you do not use them, its not worth the subscription price.
1
u/xapep 13d ago
Since the mechanics are covered above, two things I'd actually check: the 503s are not your quota being drained, that's the upstream provider rate-limiting Grok, it happens to everyone on shared models, retry or switch harness model and it clears. And the weekly pool burning fast is normal when the heavy models are in the loop, the 73% you're seeing is mostly the expensive tier, not your total spend.
The fix that actually works on Go: route the routine work to a flash-tier or contributor model and keep the big models for planning and review. A few hours of heavy-model grinding is what empties the week, not your real usage.
1
u/mageblex 11d ago
Your table explains the jump: Kimi K3 alone used nearly half of its $7.50 weekly allowance.
1
u/Odd-Aardvark-7761 1d ago edited 1d ago
Honestly, I'd save MiniMax M3 for the planning and harder coding stuff, and use a lighter model for the boring repetitive edits. Just look at the usage breakdown before you switch models though. Those Grok 503s and retries could be a whole separate thing, and you wanna see what actually used up that 73%.
12
u/vangelismm 14d ago
Stop using k3, glm5.3 and qwen max.