New OpenCode Console fails to load workspace budget, inference attempt also says Free usage exceeded despite not using any free models in the past 24 hours #49755

Activity

1. raymelon

   changed the title [-]New OpenCode Console fails to load workspace budget, also says Free usage exceeded despite not using any free models in the past 24 hours[/-] [+]New OpenCode Console fails to load workspace budget, inference also says Free usage exceeded despite not using any free models in the past 24 hours[/+] on Sep 18, 2026
2. raymelon

   changed the title [-]New OpenCode Console fails to load workspace budget, inference also says Free usage exceeded despite not using any free models in the past 24 hours[/-] [+]New OpenCode Console fails to load workspace budget, inference attempt also says Free usage exceeded despite not using any free models in the past 24 hours[/+] on Sep 18, 2026
3. khansgithub commented on Sep 19, 2026

   

   khansgithub

   on Sep 19, 2026

   More actions

   I'm getting the free usage exceeded message, despite not having touched opencode in the past 48 hours.

   👍React with 👍2Reacted by Raymel and Pedro Henrique Diniz
4. raymelon commented on Sep 20, 2026

   

   raymelon

   on Sep 20, 2026

   Last edited by raymelon

   Author

   More actions

   

   Update: Upgrade from 1.18.21 to current latest 1.18.31, did opencode console login, that finally made the rate limit error go away. But there is a caveat: the usage logs on dashboard v2 show User (email) instead of the API keys. Both Legacy and the new dashboard v2 key. I also created a new service account on dashboard v2 and a new API key, inserted it in my auth.json under "opencode": { "type": "api", "key": "" } those did not work.

   Also posted on #49751:

   Looks like this is related to dashboard v2 being silently rolled out without opt in. No communication about it, and it is destroying workflows. The usage logs on dashboard v2 show User (email) instead of API keys, and my keys stopped working because of it.

   Full details: #50078

   👍React with 👍1Reacted by khan
5. Super-Ivan commented on Sep 20, 2026

   

   Super-Ivan

   on Sep 20, 2026

   More actions

   Cross-referencing a related report: #50085

   Same class of failure here — the new Console never loads the workspace, so every workspace-scoped surface comes back empty or stuck:

   • Workspace switcher (top-left): Select workspace, empty list, repeatedly Loading workspace...
   • Go tab: renders the Subscribe state with payment buttons, briefly Checking workspace members...
   • Overview: 0 requests / 0 tokens / $0.00, "No requests were recorded"
   • Settings → Billing: stuck on Loading billing...
   • Settings → Account: stuck on Loading password settings...
   • Old deep link https://opencode.ai/workspace/<workspace_id>/go → 302 to the login/authorize page

   The subscription is definitely intact — the same account's Go key returns real usage over the API (no cookies, no workspace id needed):

   GET https://opencode.ai/zen/go/v1/usage   ->   HTTP 200
   {"usage":{
     "rolling":{"status":"ok","percent":5, "resetsAt":"2026-09-19T19:10:07.880Z"},
     "weekly": {"status":"ok","percent":46,"resetsAt":"2026-09-21T00:00:00.880Z"},
     "monthly":{"status":"ok","percent":41,"resetsAt":"2026-10-08T05:27:23.880Z"}}}
   

   @slkiser/opencode-quota v4.10.0 (reads the same key from auth.json) agrees: 95% / 54% / 59% left on the five-hour / weekly / monthly windows.

   Environment: Windows 11, OpenCode 1.18.31, GitHub login; Console org org_01M2X03EH8BXK2MFVV7CDZQGG4, old workspace wrk_01KVMTCRN3NBTCBN2ZDK21MV29.

   Also worth noting: another account signed in on the same machine works fine — only this GitHub-authenticated account is affected. Looks like the wrk_ → org_ workspace migration/loading failed for this account, leaving the Console with no workspace in scope.

   👀React with 👀1Reacted by Raymel
6. thdxr commented on Oct 11, 2026

   

   thdxr

   on Oct 11, 2026

   Member

   More actions

   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 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊
7. thdxr

   closed this as not plannedon Oct 11, 2026