Estoy pagando la versión de OpenCode Go y me sale deepseek v4 Flash con limites

[jefmaus]

I ran out of Deepseek v4 Flash credits and paid for OpenCode Go, but it keeps telling me I need to pay for the Go subscription. I can no longer use the Deepseek v4 Flash version, even after paying!

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• No issue template was used (Bug Report, Feature Request, or Question is required)
• Missing required fields: no description of steps to reproduce, no environment info (OS, OpenCode version, Desktop/TUI/CLI), and no expected vs. actual behavior
• The issue should be filed in English or include an English translation so maintainers can triage it

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

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

• Go subscription active but still "Free usage exceeded" — paid, no access #36265: Go subscription active but still showing "Free usage exceeded" — paid, no access
• [BUG]: Zen and Go expose identically-named models; picking the Zen one tells Go subscribers to "subscribe to Go" — and if it happens during compaction the session wedges permanently #42035: Detailed breakdown of why Go subscribers see "subscribe to Go" (Zen vs Go provider model naming conflict)

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Hi @jefmaus, thanks for updating the issue! However, it still doesn't follow one of our required issue templates.

This project requires every issue to use one of these three templates:

1. Bug Report – requires a Description field with real content and context about how to reproduce
2. Feature Request – requires a verification checkbox and description (title should start with [FEATURE]:)
3. Question – requires the Question field with real content

Your issue appears to be a bug report (something isn't working as expected after paying), but it's missing the required template structure. Please close this issue and open a new one using the Bug Report template, filling in the required fields — especially a description of what's happening and steps to reproduce.

Thank you!