CodingPass Go vs OpenCode Go
Two $10 plans side by side: models, limits, refunds and team options.
Most people leaving OpenCode Go aren't unhappy with OpenCode. They're unhappy that the plan behind it keeps changing. So don't switch tools. Pick a provider by two things: whether you can predict next month's bill, and which model does your hard work.
Since the DeepSeek Flash price change in August, "what should I switch to?" has become the most common question about OpenCode Go. The answers usually jump straight to another tool: ChatGPT Plus, a different CLI, a local model.
We think that's the wrong place to start. OpenCode isn't the problem. One person asking the question put it plainly: "I really like the OpenCode harness/workflow." What needs replacing is the plan underneath it, and the better plan is the one you can plan around.
We make CodingPass, so we have a stake in this. That's also why this post says who should stay on OpenCode Go.
In short: keep OpenCode, and choose the provider by the model that does your hard work. If that's DeepSeek Flash, Kimi or GLM, stay on OpenCode Go; it gives more per open-weight model than we do. If it's Claude, or you're tired of caps you can't predict, add CodingPass Go: $10 a month for a $60 allowance, metered at official API prices.
A cheap plan getting more expensive is normal. What wore people down this year was how it happened. The Flash allowance changed overnight. The line about zero data retention disappeared from the docs before anyone explained it; OpenCode later said a newly added DeepSeek model had no ZDR agreement yet. A fair reason, but it arrived after the change.
"But this might all change quickly as we've seen."
A reply recommending a rival plan's bigger DeepSeek allowance, August 2026
That reply is the whole argument. Moving to whichever plan is cheapest this month only resets the clock until its next change. The limits themselves are often fine: OpenCode Go publishes its caps, and a stale session with an expired cache is expensive anywhere. The trouble is not knowing how much a session will take out of each cap before it runs, or whether the rules will still be the same next month.
This is the bar we hold CodingPass Go to. Use it on any provider, ours included.
You can work out the cost before you start. Go's limits are dollar amounts at each provider's official API prices: $60 a month shared by every model, at most $30 per week and $10 per 5-hour window. Input, output and cache reads each have a known price, so a session's cost is arithmetic, not a guess. Every cap for every model is on the usage limits page, and codingpass usage shows what's left in each window.
Going over a cap doesn't cost you. A request that would go over is rejected before it reaches the provider and isn't charged. You get HTTP 429 with the exact time the window resets. Nothing is billed outside the pass.
Your price doesn't move under you. $10 is the early-bird price, available until Dec 25, and it stays locked while you're subscribed. The regular price is $20.
The data policy is written down. We keep metadata for metering and support: model, token counts, timestamps, latency, status code, request ID and key. Prompts, code and model output aren't stored or used for training. Each provider handles requests under its API terms, and the security page lists them.
The model fits the hard part. This is where the choice actually gets made.
If DeepSeek Flash, Kimi, GLM or MiniMax does most of your work, OpenCode Go is still the better plan, and switching would cost you allowance.
If the price change still bothers you, add a second provider for overflow instead of leaving.
CodingPass Go is the better fit if any of these sound like you:
What about the other routes? ChatGPT Plus is generous with Luna but has no open-weight models. Pay-as-you-go through OpenRouter or a provider's own API is flexible but comes with no subscription allowance. Local models are private but need the GPU. Each works for someone. None of them is a reason to leave OpenCode.
Your sessions and config stay where they are. You add one provider.
Create a key. Sign in with Google, GitHub or email, pick Go, then open Console → Keys → New key. Keys start with cp-live-.
Add the provider to ~/.config/opencode/opencode.json.
{ "provider": { "codingpass": { "npm": "@ai-sdk/anthropic", "name": "codingpass", "options": { "baseURL": "https://codingpass.ai/v1", "apiKey": "{env:CODINGPASS_API_KEY}" }, "models": { "claude-sonnet-5-5": { "name": "Claude Sonnet 5.5" }, "claude-haiku-5-5": { "name": "Claude Haiku 5.5" } } } }}Export the key and pick the model in /models.
export CODINGPASS_API_KEY="cp-live-…"If you keep OpenCode Go, both providers show up side by side in /models. If CodingPass doesn't work out, you get a full refund as long as you've used no more than 5% of the allowance.
Claude Sonnet 5.5 in OpenCode for $10 a month. One provider block, no surprise charges, cancel anytime.