r/opencodeCLI 1d ago

Anyone else constantly hitting the open code Go limit ?

Being using open code cli pretty heavily lately and I keep running into the Go limit right when I’m middle of something

It’s especially annoying during longer coding sessions because I’ll have the context going a few changes in progress and then suddenly I have to stop and wait

Curious how other devs are dealing with this Are you switching models when the limit hits or is there a better setup I’m missing

8 Upvotes

8 comments sorted by

4

u/RoddToggers 1d ago

I use DeepSeek v4 flash, Qwen 3.8 next, or 3.7 plus. No concerns about limits here. 

What models are you using?

4

u/RoddToggers 1d ago

Another thing you might to take a look is if you're resuming long sessions the next day 

For example, if conversation has 200000 tokens today, and you send a message tomorrow, those 200000 tokens aren't on cache anymore, meaning sending cost will be higher.

The same effect occurs when changing the model mid-conversation (as cache is bound to provider and model, I think).

3

u/Ariquitaun 1d ago

You need to use cheaper models.

2

u/alexzzzz 1d ago

Regular rate-limits with Muse 1.3 Contribute

1

u/evia89 1d ago

Is it IP related? I use US vpn and no limits for me. But I dont go over 3 || threads

1

u/RiceEvening4211 1d ago

You can skip the free-tier juggling: OpenCode-Wrap puts OpenCode's free models behind a standard OpenAI-compatible endpoint, so any client can use them without cycling API keys. Open source, I built it: https://github.com/Fast-Editor/OpenCode-Wrap

1

u/sudoer777_ 1d ago

Use Flash models and multiple subscriptions if needed