anomalyco / anomalyco/opencode
[BUG] OpenCode Go subscription not recognized after purchase / Deepseek v4 Flash locked
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
After running out of my Deepseek v4 Flash credits, I purchased the OpenCode Go subscription. However, the system does not recognize my active subscription. It continuously prompts me to pay for OpenCode Go again and completely blocks my access to the Deepseek v4 Flash model, even though the payment has already been completed.
Steps to reproduce
Consume all available free credits for Deepseek v4 Flash.
Purchase the OpenCode Go subscription.
Attempt to use the Deepseek v4 Flash model again.
See the error/prompt requesting payment for the OpenCode Go subscription despite having just paid.
Expected behavior
After successfully paying for the OpenCode Go subscription, the account status should be updated immediately, and access to the Deepseek v4 Flash version should be restored without further payment prompts.
Actual behavior
The system ignores the active OpenCode Go subscription, keeps asking for payment, and restricts access to the Deepseek v4 Flash version.
Screenshots
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported sequence: exhaust Deepseek v4 Flash credits, purchase OpenCode Go, and retry the model. The payload names no files, tests, or entry points, so trace how the purchase updates account status and how model access checks that status. Done means an active subscription is recognized immediately and the payment prompt no longer blocks Deepseek v4 Flash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100