You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OpenCode Go subscription no longer recognized + unable to access Console #52031
I traced the Go gateway and login paths at the current v2 source revision (gateway, login). Go entitlement is tied to both the API key's workspace and its user; the subscription webhook writes those same identifiers. The Console UI also distinguishes the subscribing member from other workspace members.
The reported “Global regions” / “active subscription required” errors differ from the reviewed gateway and English error messages, and its login service enables GitHub/Google OAuth, with email-code login commented out and no password-reset handler. The deployed service and account linkage need to be identified before changing entitlement checks.
Could a maintainer check the affected account's workspace/subscription linkage and identify the deployed authentication/gateway revision serving these errors?
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.
Activity
github-actions commentedon Sep 29, 2026
This issue might be a duplicate of existing issues. Please check:
Dante-dan commentedon Oct 1, 2026
I traced the Go gateway and login paths at the current
v2source revision (gateway, login). Go entitlement is tied to both the API key's workspace and its user; the subscription webhook writes those same identifiers. The Console UI also distinguishes the subscribing member from other workspace members.The reported “Global regions” / “active subscription required” errors differ from the reviewed gateway and English error messages, and its login service enables GitHub/Google OAuth, with email-code login commented out and no password-reset handler. The deployed service and account linkage need to be identified before changing entitlement checks.
Could a maintainer check the affected account's workspace/subscription linkage and identify the deployed authentication/gateway revision serving these errors?
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 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊