anomalyco / anomalyco/opencode

[Billing/Subscription] OpenCode Go payment successful but subscription not activated

Open
#49,509 1 comment 0 reactions 1 assignee View on GitHub

@fwang is already working on this.

Since Sep 17, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description
Description

I successfully paid for an OpenCode Go subscription, but the subscription is still not recognized in the OpenCode console. The workspace still behaves as if Go is not active and continues to prompt for subscription.

Workspace

https://opencode.ai/workspace/wrk_01M01T011XEG96SMAJVE4BH2DM/go

Payment details
  • Plan: OpenCode Go
  • Amount paid: US$10.00
  • Billing period: 15 Sep – 15 Oct 2026
  • Receipt number: 2373-8868
  • Invoice number: 75RXEF7N-0002
What happened
  • Payment completed successfully through Stripe.
  • The payment is reflected in billing history.
  • The OpenCode Go subscription still appears inactive/not provisioned for the workspace.
  • I have already contacted support at help@anoma.ly.
Expected behavior

After successful payment, the OpenCode Go subscription should be activated and recognized for the workspace.

Actual behavior

The workspace still shows the Go plan as unavailable/inactive and continues to ask for subscription even though payment succeeded.

Related reports

This appears similar to other billing/provisioning reports such as #40236, #39989, #37790, #42883, and #42969.

Could someone please check whether the subscription entitlement failed to provision or whether the workspace needs to be re-synced?

No screenshots are attached. No real name, email address, card details, or other personal information are included.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.