anomalyco / anomalyco/opencode

OpenCode Go subscription not activated after successful renewal payment

Open
#44,851 2 comments 0 reactions 1 assignee View on GitHub

@MrMushrooooom is already working on this.

Since Aug 25, 2026.

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

Description

Description

My OpenCode Go subscription appears to be lost even though the renewal payment was successfully completed and the billing period is currently active.

My subscription covers:

20 Aug 2026 – 20 Sep 2026

The payment was successfully completed on 22 Aug 2026 for US$10, and it appears correctly in my OpenCode billing history.

However, OpenCode currently behaves as though I do not have an active Go subscription.

Current behavior

On the OpenCode dashboard:

  • The Go section shows “Subscribe to Go” instead of my usage/limits.
  • Trying to use OpenCode Go models fails with an “insufficient credits” / “insufficient balance” error.
  • My billing history nevertheless shows the successful $10 Go subscription payment.

I was also successfully using Go models before this renewal issue occurred.

Expected behavior

Since the OpenCode Go renewal payment succeeded and the current paid period is 20 Aug – 20 Sep, my account should have an active Go entitlement and I should be able to use Go models subject to the normal Go usage limits.

Additional information

I have already contacted help@anoma.ly and provided the payment receipt and screenshots of my usage/billing information privately.

Please let me know if there are any logs or account identifiers I can provide privately to help debug this.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link
Image Image Image
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.