[Bug] opencode-go returns AI_APICallError: Insufficient Balance on deepseek-v4-pro and deepseek-v4-flash despite active Go subscription with 50% usage remaining #27598

Activity

1. github-actions

   assigned

   MrMushrooooom

   on May 14, 2026
2. github-actions commented on May 14, 2026

   

   github-actionsBot

   on May 14, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Error: 402 Insufficient Balance - opencode-go #27593: Same error — 402 Insufficient Balance on opencode-go, reported the same day
   • OpenCode Go: deepseek-v4-flash returns insufficient balance while other Go models work #27595: Near-identical report for deepseek-v4-flash via opencode-go (now closed)
   • OpenCode Go Kimi K2.5/K2.6 returns 429 insufficient balance despite active Go subscription #24492, [Subscriber Alert] OpenCode Go billing failure: Kimi disabled due to "insufficient balance" on proxy account #24470: Previous upstream balance issues with other models on opencode-go

   Please review these issues to see if your problem is already tracked. If it is, consider adding a comment there instead to consolidate information.
3. joaomj commented on May 14, 2026

   

   joaomj

   on May 14, 2026

   More actions

   i am facing the same problem.
4. CamiloFernando commented on May 14, 2026

   

   CamiloFernando

   on May 14, 2026

   More actions

   Reproducing "Agent completed without producing any output" in --format json mode

   Adding a reproduction for the empty-response failure that differs from the balance/credits angle in the OP.

   ---

   Environment

   • opencode 1.14.50
   • Provider: opencode-go
   • Models affected: mimo-v2.5, deepseek-v4-pro, glm-5.1 (all reasoning models)
   • Works: native TUI (opencode run)
   • Breaks: --format json mode (used by any programmatic consumer, e.g. opendesign)

   ---

   Root cause: trailing SSE event after [DONE]

   The opencode-go backend sends a non-standard SSE event after the stream terminates:

   data: {"id":"...","choices":[{"index":0,"delta":{"content":"ok"},"finish_reason":"stop"}]}
   
   data: [DONE]
   
   data: {"choices":[],"cost":"0"}    ← this event should not exist after DONE
   

   Reproduce with:

   curl -s -N -X POST https://opencode.ai/zen/go/v1/chat/completions \
     -H "Authorization: Bearer <your-key>" \
     -H "Content-Type: application/json" \
     -d '{"model":"opencode-go/mimo-v2.5","messages":[{"role":"user","content":"Reply with only: ok"}],"stream":true,"max_tokens":200}'

   ---

   What breaks

   opencode's --format json subprocess mode parses the stream sequentially. When it processes {"choices":[],...} after [DONE], it sees an empty choices array and overwrites the assembled message with empty content. The session loop never emits exiting loop and never sends HTTP 200 back to the caller.

   Evidence from opencode's own log (~/.local/share/opencode/log/):

   # Content IS streaming (bus events fire normally):
   INFO service=bus type=message.part.delta publishing   ← repeated many times
   INFO service=bus type=message.part.updated publishing
   INFO service=bus type=message.updated publishing
   INFO service=bus type=session.status publishing
   # ← process exits here. No "exiting loop", no "http.status=200"
   

   Compare to a working session (Claude provider), which shows:

   INFO service=session.prompt step=1 exiting loop
   INFO service=bus type=session.idle publishing
   INFO http.method=POST http.url=/session/.../message http.status=200 Sent HTTP response
   

   A programmatic consumer (opendesign) catches this as:

   [test:agent] OpenCode → no_text (exit 0)
   

   — opencode exited 0 but getText() was empty (the content was assembled internally but never flushed to the stdout JSON stream).

   ---

   TUI vs --format json

   The TUI mode either ignores post-DONE events or doesn't re-parse them. --format json mode re-processes every SSE event sequentially, so it gets tripped by the trailing one. This is why opencode run in a terminal works perfectly while any programmatic consumer fails.

   ---

   Suggested fix

   On the backend: stop emitting data: {"choices":[],"cost":"0"} after data: [DONE]. If cost reporting is needed, include it in the final non-empty choices event or in a custom header.

   On the client side: ignore any SSE event that arrives after data: [DONE] has been seen.
5. r3vs commented on May 15, 2026

   

   r3vs

   on May 15, 2026

   Author

   More actions

   Im closing this it's working since yesterday night.
6. r3vs

   closed this as completedon May 15, 2026