anomalyco / anomalyco/opencode
Console never loads workspace → Go shows "Subscribe" and usage is $0 while the Go subscription is active (works on another account)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
After the Console moved to org-scoped URLs, the Console for my account never loads my workspace. Every workspace-dependent surface is stuck in a loading state, the workspace switcher is empty, and the Go tab offers "Subscribe" even though my Go subscription is active and in use.
Result: Console usage shows $0.00 and I cannot see my Go quota or balance anywhere in the UI. A different account signed in on the same machine works fine — only this GitHub-authenticated account is affected.
On the same machine and the same auth.json, the Go usage API and the third-party plugin @slkiser/opencode-quota both read my real quota successfully (see Evidence below), so the subscription itself is intact — the Console just can't see the workspace.
Steps to reproduce
- Sign in at
https://opencode.ai/auth(Continue with GitHub). - Open
https://opencode.ai/console→ it lands onhttps://opencode.ai/console/org_<org_id>. - Observe the workspace switcher (top-left), the Go tab, and Settings → Billing.
Actual behavior
- Workspace switcher (top-left): shows
Select workspacewith an empty list; repeatedly displaysLoading workspace.... No workspace can be selected. - Go tab (
/console/org_<org_id>/go): renders theSubscribestate with payment buttons (Card / Link / Alipay / UPI). It briefly showsChecking workspace members...before offering a new subscription. - Overview: 0 requests / 0 tokens / $0.00, "No requests were recorded", "No model usage".
- Settings → Billing: stuck on
Loading billing...indefinitely. - Settings → Account: stuck on
Loading password settings...indefinitely. - Old deep link
https://opencode.ai/workspace/<workspace_id>/gonow 302-redirects to the login/authorize page (route appears dead). https://opencode.ai/console/<workspace_id>/gorenders a blank page.
Expected behavior
- The Console lists my workspace(s) and lets me select the one that owns the Go subscription.
- The Go tab shows my active subscription and its rolling / weekly / monthly usage.
- Billing and Account pages load.
Evidence that the subscription is intact (same account, same machine)
Calling the usage API with this account's Go key returns HTTP 200 with real, non-zero usage:
GET https://opencode.ai/zen/go/v1/usage
Authorization: Bearer <go_api_key>
{"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"}}}
The third-party plugin @slkiser/opencode-quota v4.10.0 (which reads the same key from auth.json, no cookies) also reports:
[OpenCode Go]
Five-hour 3h 34m █████████████████████████████████████░░ 95% left
Weekly 1d 8h 23m █████████████████████░░░░░░░░░░░░░░░░░░░░ 54% left
Monthly 18d 13h 51m ███████████████████████░░░░░░░░░░░░░░░░░░░ 59% left
So the workspace + subscription exist server-side; only the Console UI fails to load the workspace and therefore shows $0 / "Subscribe".
Possible cause
Looks like the wrk_ → org_ workspace migration / workspace loading failed for this account: the Console has no workspace in scope, so all workspace-scoped queries (subscription, billing, usage) never resolve.
Environment
- Account: GitHub
@Super-Ivan(email redacted; can be provided privately) - Console URL:
https://opencode.ai/console/org_01M2X03EH8BXK2MFVV7CDZQGG4 - Console org id:
org_01M2X03EH8BXK2MFVV7CDZQGG4 - Old workspace id (from the previous UI):
wrk_01KVMTCRN3NBTCBN2ZDK21MV29 - OpenCode version:
1.18.31 - OS: Windows 11 (win32)
- Browser: Chrome (latest) — also reproduced in a separate browser session
Related
- Possibly related: #49755 (New OpenCode Console fails to load workspace budget)
- Possibly related: #26213 (Go API proxy returns cost "0" and dashboard not tracking usage)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the org-scoped Console entry points described in the issue, especially /console/org_<org_id>, its Go route, Settings → Billing, and Settings → Account. Trace why workspace loading and the workspace-scoped queries do not resolve for this GitHub-authenticated account, using the reported org_ and wrk_ identifiers as reproduction data. Done means the workspace switcher populates, Go shows the active subscription and usage, and Billing and Account load normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100