Repository navigation
tui: new sessions fail with "Insufficient account funds" on active OpenCode Go while CLI works #54244
Description
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
- opencode version: 2.0.26
- OS: Darwin 27.0.0 (darwin arm64)
- Terminal: ghostty (TERM=xterm-256color, TERM_PROGRAM=ghostty, COLORTERM=truecolor)
- Shell: /bin/zsh
- Install/channel: latest
- Active plugins: none
Reproduction
- Have an active OpenCode Go subscription on the workspace;
opencode auth listshowsOpenCode Console Personal stored. - Confirm the CLI works:
opencode run --model opencode-go/deepseek-v4.1-flash "Reply with exactly: OK"→ printsOK. - Also confirm the config default works:
opencode run "Reply with exactly: OK"→ printsOK. - Open the TUI (
opencode) and start a new session, send any prompt. - The request fails with "Insufficient account funds" / "Insufficient balance".
Expected Behavior
A new TUI session should use the Go-covered model and succeed, exactly like opencode run does 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
- Workspace: Personal (owner). Go is active. Console usage (30d): $0.82 across 273 requests (almost all
deepseek-v4.1-flash). No member budget cap (budget: null). - Enabled Go models include
deepseek-v4.1-flashanddeepseek-v4-pro;deepseek-v4-flashanddeepseek-v4-flash-vision-expare disabled for the workspace. - Pinned the working model globally in
~/.config/opencode/opencode.jsonc("model": "opencode-go/deepseek-v4.1-flash") — TUI still fails. - Removed and re-added the account (
opencode auth) — still fails. - Workarounds that work: the pre-existing session, and
opencode run(CLI). - Likely related: OpenCode Go activo pero la TUI muestra "Insufficient balance" mientras CLI funciona #33406 (CLI works, TUI shows "Insufficient balance"), I'm subscribed to OpenCode Go ($10/month, next billing August 10, 2026). My balance is $0.00. #38208, OpenCode Go models return "Insufficient account funds" with active subscription and 0% usage #51424.
Metadata
Metadata
Assignees
Labels
No labels
Activity
opencode-agent commentedon Oct 10, 2026
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:
/models, choosedeepseek-v4.1-flashfrom the OpenCode Go group and then send a prompt, does it still fail?modelset on any agent (inopencode.jsoncor an agent file), or a project-levelopencode.jsonwith amodel?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/...Console provider instead ofopencode-go/...; others report new logins being billed as "standard" instead of "go".auth listalso shows only the Console credential.shyamm-dev commentedon Oct 10, 2026
opencode-agent commentedon Oct 10, 2026
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:
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.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.Related: #51424, #50611.
shyamm-dev commentedon Oct 10, 2026
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