Only free models work with GO #55856

Activity

1. opencode-agent commented on Oct 15, 2026

   

   opencode-agentBot

   on Oct 15, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report! The "Insufficient account funds" error usually means the request went through the OpenCode Console provider (opencode/<model>, paid from Console credits) instead of OpenCode Go (opencode-go/<model>, covered by your Go plan). Free models work either way, which fits what you're seeing. To find out which case you're in, could you share:

   1. Whether you use the desktop app, the TUI (opencode) or opencode run, plus your OS and how you installed OpenCode.
   2. How you connected Go: Console sign-in (device code) or pasting the Go API key, and from which screen.
   3. The provider and model the failing request used, e.g. what the footer or /models shows ("Personal / OpenCode" or "OpenCode Go"), or the full model ID (opencode/... or opencode-go/...).
   4. Whether your config (opencode.json/opencode.jsonc) has a provider or providers block for opencode-go (please remove any API keys before pasting).
   5. Whether running opencode run --model opencode-go/<model> "say OK" with a paid Go model works.

   You can reply here 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 may already cover your problem (most likely first):

   • 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: in the desktop app, "Connect OpenCode Go" runs the Console sign-in instead, so paid models fail with "Insufficient account funds" (you commented there already)
   • tui: new sessions fail with "Insufficient account funds" on active OpenCode Go while CLI works #54244: new TUI sessions use the Console provider and fail with this error, while the CLI works
   • OpenCode Go models return "Insufficient account funds" with active subscription and 0% usage #51424: same symptom with an active Go plan and 0% usage (closed; reported on v1, with v2 confirmations in the comments)
   • provider: legacy V1 provider.opencode-go block silently dropped in v2 breaks Go credentials (fixed by removing the block) #54370: an old v1-style provider.opencode-go config block breaking Go credentials after upgrading to v2
2. opencode-agent

   added

   triaging

   on Oct 15, 2026
3. opencode-agent

   closed this as not plannedon Oct 18, 2026
4. opencode-agent commented on Oct 18, 2026

   

   opencode-agentBot

   on Oct 18, 2026 – with OpenCode Agent

   Contributor

   More actions

   We're closing this for now because we didn't get the details we asked for. Without knowing which client you used, how OpenCode Go was connected and which provider/model the failing request went through (opencode/… or opencode-go/…), we can't tell what's causing the "Insufficient account funds" error.

   If you're still seeing it, please follow #50611, which is the closest match. Or reply here with those details and we can reopen this. Thanks!