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
Since October 24–25, 2026, I have been experiencing an issue with OpenCode's free usage limits. When the initial countdown expires, access is not restored. Instead, another countdown of approximately 74,000 seconds appears.
This issue affects multiple models, and switching models does not resolve it.
Error message:
Free usage exceeded, subscribe to Go reintentando en 74000s - intento n.º 1
Plugins
No response
OpenCode version
1.18.30
Steps to reproduce
Use a free model until the usage limit is reached.
Wait for the countdown to expire.
Attempt to use the model again.
Observe that access remains restricted and another long countdown appears.
Thanks for the report, and sorry about this. Waiting out the whole countdown only to be blocked again, on every free model, is really frustrating.
The free-usage allowance and its reset are counted and enforced by OpenCode's service, not by the app on your machine. Only the team can look into this for your account, and billing and account support isn't handled in GitHub issues. Please email help@anoma.ly with the details: roughly when you first hit the limit, the countdowns you saw, and which models you tried. If you've already emailed, the team will get to it, especially now that we've seen it here.
Please keep email addresses, account details and any payment information out of this public issue and put them only in the email.
Several other people have reported the same thing since October 24, for example:
I also encountered this. Even though I already have free quota to use, it still makes me wait for more than 70,000 seconds.
This has probably been going on for two days recently.
Closing this now, since free-usage and account problems are handled by email rather than in GitHub issues. Sorry again for the trouble with the countdown starting over.
If this is still happening, please email help@anoma.ly with the details, such as when you hit the limit, the countdowns you saw and which models you tried. If you've already written to them, the team will get to it. Please keep account and payment details out of this public issue and put them only in the email.
Thanks for taking the time to report it, @Jignesh1236.
Activity
opencode-agent commentedon Oct 25, 2026
Thanks for the report, and sorry about this. Waiting out the whole countdown only to be blocked again, on every free model, is really frustrating.
The free-usage allowance and its reset are counted and enforced by OpenCode's service, not by the app on your machine. Only the team can look into this for your account, and billing and account support isn't handled in GitHub issues. Please email help@anoma.ly with the details: roughly when you first hit the limit, the countdowns you saw, and which models you tried. If you've already emailed, the team will get to it, especially now that we've seen it here.
Please keep email addresses, account details and any payment information out of this public issue and put them only in the email.
Several other people have reported the same thing since October 24, for example:
The bot will close this issue in 1 day.
TransferStation-ai commentedon Oct 25, 2026
I also encountered this. Even though I already have free quota to use, it still makes me wait for more than 70,000 seconds.
This has probably been going on for two days recently.
TransferStation-ai commentedon Oct 25, 2026
It probably starts from the 23rd. If you use up your free quota, you won't be able to use the free quota on the 2nd or even the 3rd day.
opencode-agent commentedon Oct 26, 2026
Closing this now, since free-usage and account problems are handled by email rather than in GitHub issues. Sorry again for the trouble with the countdown starting over.
If this is still happening, please email help@anoma.ly with the details, such as when you hit the limit, the countdowns you saw and which models you tried. If you've already written to them, the team will get to it. Please keep account and payment details out of this public issue and put them only in the email.
Thanks for taking the time to report it, @Jignesh1236.