Repository navigation
tui: new sessions fail with "Insufficient account funds" on active OpenCode Go while CLI works #54244
Description
Activity
Thanks for the detailed report! One detail would help us tell whether this is a TUI bug or a provider mix-up.
In the TUI, the provider decides how a model is billed.
opencode/<model>(OpenCode Console / Zen) is billed from Console credits, andopencode-go/<model>is billed to your Go subscription. If a request goes through the Console provider with $0 credit, you get exactly this "Insufficient account funds" error. Also, a new TUI session doesn't always use themodelfromopencode.jsonc: a model you picked before for that project or agent, or a model set on the agent, takes priority over the config.Could you tell us:
- In a new TUI session, before sending, which model and provider does the prompt footer show? Is it listed under OpenCode Go or under Personal / OpenCode (Console)? A screenshot is ideal.
- If you open
/models, choosedeepseek-v4.1-flashfrom the OpenCode Go group and then send a prompt, does it still fail? - Do you have a
modelset on any agent (inopencode.jsoncor an agent file), or a project-levelopencode.jsonwith amodel? - The full error text exactly as the TUI shows it.
You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it so we know you're done.
These existing issues look closely related (most likely first), in case one of them already covers your problem:
- OpenCode Go models return "Insufficient account funds" with active subscription and 0% usage #51424: same "Insufficient account funds" error with an active Go plan at 0% usage. One commenter found they had picked the
opencode/...Console provider instead ofopencode-go/...; others report new logins being billed as "standard" instead of "go". - desktop: "Connect OpenCode Go" runs Console sign-in instead of the Go API-key flow, then reports success and fails with "Insufficient account funds" #50611: "Connect OpenCode Go" stores only an OpenCode Console credential, and requests then fail with "Insufficient account funds". Your
auth listalso shows only the Console credential. - OpenCode Go subscription not working in Desktop App: "Invalid credential" / "Insufficient account funds" and Go badges disappear #51689: the same Go/Console credential mix-up in the desktop app.
- OpenCode Go activo pero la TUI muestra "Insufficient balance" mientras CLI funciona #33406: the same "CLI works, TUI says Insufficient balance" symptom on v1.17.9.
- DeepSeek V4.1 Flash Personal / OpenCode
- using the Opencode Go still fails.
- Yes DeepSeek V4.1 Flash is my default
- Error: Upstream request failed: Insufficient account funds
Thanks for the follow-up, that helps a lot.
We can't reproduce this in our sandbox. The "Insufficient account funds" error comes from the OpenCode backend and only shows up with a real Console/Go account, which our test environment doesn't have. A maintainer with a Go account will need to look at it.
What your answers tell us so far:
- The footer showing DeepSeek V4.1 Flash · Personal / OpenCode means new sessions use the Console provider (
opencode/deepseek-v4.1-flash). That provider is billed from Console credits, not your Go plan, so with $0 credit this error is expected for that model. It looks like a model you picked earlier for the project or agent takes priority over themodelin youropencode.jsoncfor new sessions. That's our reading of the code, not something we could run. - The part that still needs a maintainer: you say picking DeepSeek V4.1 Flash from the OpenCode Go group in the TUI also fails, while
opencode run --model opencode-go/deepseek-v4.1-flashworks on the same account. This may be the same backend problem reported in OpenCode Go models return "Insufficient account funds" with active subscription and 0% usage #51424, where requests from newer logins seem to be billed as "standard" instead of "go".
If you can, it would help to check whether
opencode run --model opencode/deepseek-v4.1-flash "Reply with exactly: OK"fails with the same error. That would show whether the CLI and TUI difference comes down to which provider the TUI picks.- The footer showing DeepSeek V4.1 Flash · Personal / OpenCode means new sessions use the Console provider (
Also looks like I started getting this message when i tried using opus model which i do not have access to and switched back to the Personal / OpenCode deepseek model which worked for me before and after that every new session i open started showing this issue
Summary
With an active OpenCode Go subscription, new TUI sessions fail with "Insufficient account funds" / "Insufficient balance" even though the CLI succeeds with the same account and model. Go usage stays near 0%, so it is not a real usage/budget limit.
Environment
Reproduction
opencode auth listshowsOpenCode Console Personal stored.opencode run --model opencode-go/deepseek-v4.1-flash "Reply with exactly: OK"→ printsOK.opencode run "Reply with exactly: OK"→ printsOK.opencode) and start a new session, send any prompt.Expected Behavior
A new TUI session should use the Go-covered model and succeed, exactly like
opencode rundoes on the same account/model.Actual Behavior
New TUI sessions error with "Insufficient account funds"/"Insufficient balance". Go usage does not increase (stays near 0%). Existing sessions continue to work, and the CLI works.
Additional Context
deepseek-v4.1-flash). No member budget cap (budget: null).deepseek-v4.1-flashanddeepseek-v4-pro;deepseek-v4-flashanddeepseek-v4-flash-vision-expare disabled for the workspace.~/.config/opencode/opencode.jsonc("model": "opencode-go/deepseek-v4.1-flash") — TUI still fails.opencode auth) — still fails.opencode run(CLI).