查看中文版 →

Deutsche Version ansehen →

Открыть русскую версию →

Log inChoose a plan
Blog · Costs and limits

The best OpenCode Go alternative keeps OpenCode

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.

Price is the symptom. Predictability is the problem.

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.

What a plan you can plan around looks like

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.

Stay on OpenCode Go if open-weight models do your work

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.

  • It gives Kimi K2.7 Code, MiniMax-M3 and GLM-5.3-Flash $60 a month each, and DeepSeek V4.1 Flash $80. On CodingPass Go each open-weight model can use up to $40, from the shared allowance.
  • It lists 30 models. We have fewer.
  • Its 5-hour cap is 20% of each model's monthly allowance. Ours is 17%.

If the price change still bothers you, add a second provider for overflow instead of leaving.

Switch if Claude does your hard work

CodingPass Go is the better fit if any of these sound like you:

  • You want Claude in OpenCode. OpenCode Go has no Claude Sonnet on any tier. On CodingPass Go, Sonnet 5.5 can use the whole $60, and Claude Haiku 5.5 gets $60, 4 times OpenCode Go's $15.
  • You plan with a strong model and execute with a cheap one. It's the setup people recommend most, and here it comes out of one allowance: Sonnet 5.5 writes the plan, Haiku 5.5 or an open-weight model carries it out.
  • You've hit a cap you didn't see coming. Dollar caps at list prices, and a 429 that says exactly when the window comes back, take the guessing out.
  • You may need more later. Plus adds Claude Opus 5.5 and GPT-6.1 Sol, Pro adds Claude Fable 5.2, and Team pools one allowance across seats.

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.

Adding CodingPass Go takes two minutes

Your sessions and config stay where they are. You add one provider.

  1. Create a key. Sign in with Google, GitHub or email, pick Go, then open Console → Keys → New key. Keys start with cp-live-.

  2. Add the provider to ~/.config/opencode/opencode.json.

    ~/.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" }      }    }  }}
  3. Export the key and pick the model in /models.

    ~/.zshrc
    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.

FAQ

Do I have to cancel OpenCode Go?
No. OpenCode takes several providers at once. OpenCode Go for open-weight models and CodingPass Go for Claude is a reasonable setup.
Do cache reads count against the allowance?
Yes, at the provider's official cache-read price, a small fraction of the input price. Long OpenCode sessions are mostly cache reads, so the allowance lasts longer than the headline number suggests. A session whose cache has expired costs more, the same as anywhere else.
Is this against provider terms?
No. You use a CodingPass key. Nobody's Claude or ChatGPT account is logged into, shared or forwarded. Requests must follow each provider's usage policies.
Boarding

Keep OpenCode. Change the provider.

Claude Sonnet 5.5 in OpenCode for $10 a month. One provider block, no surprise charges, cancel anytime.

  • Request ID on every response
  • Full refund if you've used 5% or less
  • No surprise charges
Choose GoOpenCode guide

$10/mo until you cancel.