Existing issues
What happened?
Problem
OpenCode Go (Web source) currently fails with:
Parse error: Missing rolling usage window
Cookie auth itself succeeds (HTTP 200, no AuthRequired), but the scraper cannot find a rolling window in the returned page.
What changed upstream
-
Page URL moved
- Old:
https://opencode.ai/wrk_XXX/go (also currently coded as https://opencode.ai/workspace/{id}/go)
- New:
https://opencode.ai/console/wrk_XXX/go
-
Page layout changed
The new /console/.../go page no longer exposes the old rollingUsage / rolling_usage / rolling + usagePercent / resetInSec shape the parser expects, so parse_usage_text() returns None for rolling and throws.
API key alternative now available
OpenCode Go now supports fetching limits via API key:
curl -H "Authorization: Bearer ${OPENCODE_API_KEY}" https://opencode.ai/zen/go/v1/usage | jq .
Response:
{
"usage": {
"rolling": {
"status": "ok",
"percent": 0,
"resetsAt": "2026-09-22T06:56:21.515Z"
},
"weekly": {
"status": "ok",
"percent": 6,
"resetsAt": "2026-09-28T00:00:00.000Z"
},
"monthly": {
"status": "ok",
"percent": 19,
"resetsAt": "2026-09-30T08:26:37.000Z"
}
}
}
Suggestion
- Update
fetch_usage_page() URL to https://opencode.ai/console/{workspace_id}/go (with fallback to old paths).
- Update
extract_window() / parse_usage_text() for the new console layout.
- Prefer
GET /zen/go/v1/usage with OPENCODE_API_KEY when available, since it returns clean rolling / weekly / monthly { percent, resetsAt }.
Env
- Win-CodexBar (Windows, Chrome, manual Cookie for
opencode.ai)
- Web source, reproducible on current
main
Affected area
Steps to reproduce
- Log in to opencode.ai and copy the session cookies.
- Import the cookies into Win-CodexBar. Win-CodexBar then reports:
Parse error: Missing rolling usage window
Logs, screenshots, or recordings
<img width="950" height="1636" alt="Image" src="https://github.com/user-attachments/assets/3ffb47ae-135a-4f00-8910-cc017b382be2" />
App version
v0.60.3
Windows version
Windows 10 22H2 19045.7725
Additional context
No response
Existing issues
What happened?
Problem
OpenCode Go (Web source)currently fails with:Cookie auth itself succeeds (HTTP 200, no
AuthRequired), but the scraper cannot find arollingwindow in the returned page.What changed upstream
Page URL moved
https://opencode.ai/wrk_XXX/go(also currently coded ashttps://opencode.ai/workspace/{id}/go)https://opencode.ai/console/wrk_XXX/goPage layout changed
The new
/console/.../gopage no longer exposes the oldrollingUsage / rolling_usage / rolling+usagePercent / resetInSecshape the parser expects, soparse_usage_text()returnsNoneforrollingand throws.API key alternative now available
OpenCode Go now supports fetching limits via API key:
Response:
{ "usage": { "rolling": { "status": "ok", "percent": 0, "resetsAt": "2026-09-22T06:56:21.515Z" }, "weekly": { "status": "ok", "percent": 6, "resetsAt": "2026-09-28T00:00:00.000Z" }, "monthly": { "status": "ok", "percent": 19, "resetsAt": "2026-09-30T08:26:37.000Z" } } }Suggestion
fetch_usage_page()URL tohttps://opencode.ai/console/{workspace_id}/go(with fallback to old paths).extract_window()/parse_usage_text()for the new console layout.GET /zen/go/v1/usagewithOPENCODE_API_KEYwhen available, since it returns cleanrolling / weekly / monthly { percent, resetsAt }.Env
opencode.ai)mainAffected area
Steps to reproduce
Parse error: Missing rolling usage windowLogs, screenshots, or recordings
App version
v0.60.3
Windows version
Windows 10 22H2 19045.7725
Additional context
No response