OpenCode Go workspace subscription is orphaned/hidden and cannot be managed from dashboard #33102

Activity

1. github-actions

   assigned

   fwang

   on Jun 20, 2026
2. github-actions commented on Jun 20, 2026

   

   github-actionsBot

   on Jun 20, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Billing issue in OpenCode Go, payment deducted twice under different invoice #29248: Billing issue in OpenCode Go, payment deducted twice under different invoice (referenced directly in your issue — now closed)
   • Paid for OpenCode Go but subscription is not activated / “No payment method” error #30515: Paid for OpenCode Go but subscription not activated / "No payment method" error (closed)
   • Cobro doble de suscripción zen y go #31028: Double subscription charges (cobro doble de suscripción zen y go, open)
   • actual by mistake my payemnt is deducted #28776: Payment deducted unexpectedly (closed)

   If your issue is distinct from the above, please clarify how it differs so maintainers can handle it separately.
3. mukhlim commented on Jun 20, 2026

   

   mukhlim

   on Jun 20, 2026

   Author

   More actions

   Thanks for checking.

   My case is similar to the linked billing issues, but I believe it is distinct because the main problem is not only a one-time duplicate invoice.

   In my case:

   1. My OpenCode dashboard does not show an active/manageable OpenCode Go subscription.
   2. Despite that, my card has been charged repeatedly for OpenCode Go.
   3. I only saved the last two invoices, but the recurring charges appear to have been happening for longer.
   4. I tried cancelling/removing the payment method from the dashboard, but I need confirmation that there is no hidden/incorrectly linked Stripe/customer subscription still active.
   5. This looks like an account-linking or billing-record mismatch: the subscription exists in billing, but it is not visible/manageable from my dashboard account.

   So this is different from a simple duplicate invoice case. I need help from the team to check the billing/customer records privately and confirm:

   • all active OpenCode Go subscriptions linked to my payment method/account are cancelled;
   • no future recurring charges will be attempted;
   • the full billing history can be reviewed;
   • duplicate, unauthorized, or unmanaged recurring charges can be refunded.

   I can provide receipt numbers, email addresses, card last 4 digits, and screenshots privately via the correct support channel. I do not want to post sensitive billing details publicly on GitHub.
   I already contacted / will contact help@anoma.ly with private billing details.
4. mukhlim commented on Jun 20, 2026

   

   mukhlim

   on Jun 20, 2026

   Last edited by mukhlim

   Author

   More actions

   Clarification: this appears to be a workspace-level billing bug, not just a duplicate invoice.

   From what I remember, I first subscribed to OpenCode Go, but the dashboard did not show an active/manageable subscription. Because of that, I tried subscribing again through other workspace/account states. It seems one email/account can have multiple workspaces, and each workspace can have its own Go subscription.

   This likely created multiple Go subscriptions under the same email/payment method. The visible workspace subscriptions were later cancelled / payment method removed, but at least one earlier subscription appears to have become orphaned or hidden and kept charging.

   So the core issue is that a Go subscription can exist at the workspace/billing level while not being visible or manageable from the user’s current dashboard/account view.

   Please audit all workspace, customer, and subscription records linked to my email/GitHub account/payment method, not only the currently visible workspace.
5. mukhlim

   changed the title [-]OpenCode Go subscription not visible in dashboard but recurring charges continue[/-] [+]OpenCode Go workspace subscription is orphaned/hidden and cannot be managed from dashboard[/+] on Jun 20, 2026
6. opencode-agent commented on Jul 6, 2026

   

   opencode-agentBot

   on Jul 6, 2026 – with OpenCode Agent

   Contributor

   More actions

   Root-cause update (2026-07-06, sanitized):

   • Confirmed recurrence in production. A paid orphan subscription remains active in Stripe, but because it is not linked to workspace billing it grants no workspace entitlement.
   • At origin/dev 38bb38e, Lite checkout only rejects an already-linked subscription, then creates a Checkout Session using customer_email when the workspace has no linked customer. There is no idempotency key or pending reservation, so concurrent, retried, or stale Sessions can race, and customer_email can yield duplicate Stripe customers. This is a code-path/race finding; it does not assert that specific Checkout Sessions were observed in production.
   • The first customer.subscription.created webhook claims the workspace; a later subscription under another customer throws Customer ID mismatch. Its invoice.payment_succeeded lookup, keyed only by the linked customer, also throws. The later Stripe subscription can therefore stay paid while workspace linkage and entitlement fail.
   • We need concurrency tests for Session creation/webhook ordering and reconciliation tests for paid subscriptions not linked to workspace billing.
7. mukhlim commented on Jul 7, 2026

   

   mukhlim

   on Jul 7, 2026

   Author

   More actions

   Thanks for looking into this.

   Please let me know the correct private channel where I should send the billing details, such as receipt numbers, invoice IDs, card last 4 digits, email addresses, and screenshots.

   To avoid any ambiguity, I still need confirmation for these points:

   1. all active OpenCode Go subscriptions/customer records linked to my payment method have been cancelled;
   2. no future recurring charges will be attempted;
   3. the full billing history can be reviewed;
   4. duplicate, unauthorized, or unmanaged recurring charges can be refunded.

   I will not post sensitive billing information publicly on GitHub.
8. github-actions commented on Sep 6, 2026

   

   github-actionsBot

   on Sep 6, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
9. github-actions

   closed this as not plannedon Sep 6, 2026