Repository navigation
Description
Description
I am an opencode Go subscriber (Taiwan, GMT+8) and I want to report two problems that together caused me to burn $12 of quota in 45 minutes with zero output, and I had no idea my quota was exhausted until everything silently stopped.
Problem 1 ??Free model (big-pickle) congestion is silent and unresponsive for hours.
On 2026-08-10 (UTC) my big-pickle sessions kept failing with Rate limit exceeded. Please try again later. (16+ occurrences between 11:18 and 15:39, confirmed in the local log %LOCALAPPDATA%\.local\share\opencode\log\opencode.log). After 15:39 the model went completely silent for ~4 hours (next record only at 19:24). During that time I got no responses and no error surfaced in the UI ??I only saw a stuck session. I assumed it was general network congestion.
Problem 2 ??When I switched to paid models to unblock myself, quota drained with no warning, and then everything stopped silently.
At 19:26 I switched to the Go paid models (deepseek-v4-pro, then glm-5.1) because big-pickle was unresponsive. Over ~45 minutes I made 254 paid calls (glm-5.1 ?158, deepseek-v4-pro ?95, deepseek-v4-flash ?1). At 20:07 the log shows AI_APICallError: Insufficient balance. Manage your billing here: .../billing and every session stopped mid-task. Weekly usage jumped to 40% in that single burst. I never saw an in-app quota warning; the first I knew was that my tasks silently stopped with no completed results.
The result: I paid for a plan, my work stalled for hours due to the free-tier congestion, the workaround (switching to paid models) consumed a large chunk of quota in under an hour, and I finished with no output and no clear error explaining why. My goal here is not a refund ??I want the congestion and the lack of warning/visibility fixed.
Plugins
None (stock opencode Desktop)
OpenCode version
OpenCode Desktop 1.18.10
Steps to reproduce
- Use the free big-pickle model during a period of congestion ??observe
Rate limit exceeded. Please try again later.errors in the local log, followed by several hours with no responses and no surfaced error in the UI. - Switch to a Go paid model (e.g. deepseek-v4-pro / glm-5.1) to unblock the stuck session.
- Run agentic work with parallel subagents ??observe the rolling 5-hour quota ($12) being exhausted within ~45 minutes.
- When the quota is exhausted, the log records
Insufficient balancebut there is no in-app warning beforehand, and sessions stop mid-task with no completed results.
Screenshot and/or share link
Local log evidence (paths): C:\Users\hpspy\.local\share\opencode\log\opencode.log
- 16+
Rate limit exceedederrors for big-pickle between 2026-08-10T11:18 and 15:39 UTC - big-pickle silent 2026-08-10T15:39 ??19:24 UTC (~4h)
- 254 paid-model stream calls 2026-08-10T19:26 ??20:11 UTC
Insufficient balanceerrors from 2026-08-10T20:07 UTC
Operating System
Windows 11 (Asia/Taipei, GMT+8)
Terminal
OpenCode Desktop (1.18.10), built-in terminal
Activity
github-actions commentedon Aug 11, 2026
This issue might be a duplicate of existing issues. Please check:
spyang1963-pattern commentedon Aug 11, 2026
Thanks for flagging the potential duplicate with #40588. I believe this report is distinct and should not be merged, for two reasons:
It is one linked chain of events, not a single UX complaint. The congestion on the free model (big-pickle) left me with no responses for ~4 hours (16+ \Rate limit exceeded\ entries in the log between 11:18-15:39 UTC, then silence until 19:24). Because nothing surfaced in the UI, I switched to paid Go models to unblock myself — and only then discovered (by burning quota) that the paid quota drains with no in-app warning either. OpenCode free tier cuts off service mid-task with no warning - expose remaining allowance / add countdown #40588 covers the paid-quota side; it does not cover the free-model congestion side that forced the switch in the first place.
I have concrete, quantifiable evidence that is already linked in the report: local log paths, 254 paid stream calls in ~45 minutes (glm-5.1 x158, deepseek-v4-pro x95, deepseek-v4-flash x1), \ of the rolling 5-hour quota consumed, and \Insufficient balance\ errors from 20:07 UTC onward with sessions stopping mid-task and no completed output.
My ask remains: improve visibility/warning when quota is being consumed, and surface free-model rate-limit/silence to the user instead of a permanently stuck session.
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊