You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OpenCode Go: Kimi K3 per-model limit appeared separate but consumed shared monthly quota #49186
Go: Kimi K3 usage unexpectedly consumed shared monthly quota after model limits appeared separate in the usage UI/docs
I used Kimi K3 believing its displayed usage allowance was separate from the other Go models. I later realized that the usage was actually deducted from the same shared Go monthly quota, which caused approximately 20% of my monthly allowance to be consumed unexpectedly.
The current presentation of per-model usage limits made this behavior unclear to me.
Could you please clarify whether this is the intended quota accounting behavior? If so, it may be helpful to make the shared nature of the quota more explicit in the UI/documentation.
I have also contacted support/Discord separately regarding whether the affected usage can be restored.
Screenshots and timestamps are available if useful.
If your issue is specifically about the UI not making the shared nature of the monthly quota visible (rather than a billing error), #47547 is likely the closest match. Please check those issues and consider adding your details there if they describe the same root cause.
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.
Activity
github-actions commentedon Sep 15, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is specifically about the UI not making the shared nature of the monthly quota visible (rather than a billing error), #47547 is likely the closest match. Please check those issues and consider adding your details there if they describe the same root cause.
redcasinotimonneo commentedon Oct 8, 2026
Hi there, please read the comment i wrote under the similar issue as yours: #49014 (comment) @Ghmoonth
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊