Skip to content

fix(console): restrict legacy access to Black - #50700

Closed
vaprdev wants to merge 4 commits into
v2from
disable-console-signup
Closed

vaprdev wants to merge 4 commits into
v2from
disable-console-signup

Conversation

@vaprdev

@vaprdev vaprdev commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • allow only accounts with an active OpenCode Black subscription to authenticate into or continue using the legacy Console
  • redirect non-Black accounts, including existing legacy sessions, to https://console.opencode.ai
  • prevent the legacy auth worker from creating accounts
  • replace the legacy workspace Go page with a redirect to https://console.opencode.ai/go and remove its obsolete management UI
  • point public Go subscription links to the new Console
  • reject legacy Go checkout creation server-side

Production check

  • 1,887 workspaces have an active Black subscription
  • 1,786 have a booked but inactive Black record
  • none of the inactive bookings were created in the last 30 days, so access requires an active subscription_id

Verification

  • bun run check

Deployment note

Stripe Checkout Sessions created before deployment remain usable until they expire. Expire open legacy Go Checkout Sessions operationally if an immediate hard cutoff is required.

@vaprdev vaprdev changed the title fix(console): disable legacy signups fix(console): disable legacy signups and Go activation Sep 22, 2026
@vaprdev vaprdev changed the title fix(console): disable legacy signups and Go activation fix(console): restrict legacy access to Black Sep 22, 2026
@vaprdev

vaprdev commented Sep 22, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #50716, which targets the deployable legacy Console branch (). The branch does not trigger the Console deployment workflow.

@vaprdev vaprdev closed this Sep 22, 2026
@vaprdev

vaprdev commented Sep 22, 2026

Copy link
Copy Markdown
Contributor Author

Correction: superseded by #50716, which targets the deployable legacy Console branch (dev). The v2 branch does not trigger the Console deployment workflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant