Repository navigation
Free tier limit reached even after resetting the quotas . #58869
Description
Description
Describe the bug
OpenCode continues to display Free usage limit reached even after the displayed daily reset time has passed.
I first encountered this issue in OpenCode Desktop while using free models. The warning stated that my free messages would reset on October 26, 2026, at 5:29 AM. I waited until after the reset time, but the same warning persisted at approximately 8:00 AM.
I then installed and tested the official OpenCode CLI v2.1.4 using the same account. The CLI also displayed the free usage limit error in a new session.
This suggests that the issue is not exclusive to the Desktop interface. However, I cannot determine whether the cause is an account/network-level restriction, a server-side quota calculation issue, or another limit that is not clearly communicated.
Expected behaviour
After the displayed reset time, free-model requests should become available again if the relevant quota has reset.
If another limit is being enforced, the error should clearly identify the limit, its applicable time window, and when or under what conditions access will be restored.
Actual behaviour
The same free usage limit warning persists after the displayed reset time, including in a new CLI session.
The CLI reports:
Free limit reached
The message indicates that free messages have been used and displays a reset time, but waiting until that time has passed does not restore access.
Environment :
- OS: macOS
- Architecture: Apple Silicon (MacBook Air M1)
- OpenCode Desktop: version not independently verified
- OpenCode CLI: v2.1.4
- Account: existing OpenCode account
- Plan: Free
- Models observed: DeepSeek V4.1 Flash Free in Desktop; Flint 40B Free in CLI
Additional context
I have already waited past the displayed reset time and tested a new session. The same warning appeared in both Desktop and CLI.
Could the maintainers clarify whether this behaviour is expected under another free-tier limit, or whether the displayed reset time or quota enforcement is incorrect?
I would appreciate guidance on how to distinguish a genuine quota restriction from an incorrect or misleading reset message.
I can provide additional logs and timestamps if needed.
Plugins
OpenCode Zen
OpenCode version
2.1.4
Steps to reproduce
- Open OpenCode Desktop on macOS and sign in to the existing account.
- Select a free model and send a prompt.
- Observe the
Free usage limit reachedmessage and note the displayed reset time. - Wait until after the displayed reset time.
- Create a new session and retry a short prompt.
- Install and launch OpenCode CLI v2.1.4 with the same account.
- Open a new CLI session and attempt a short prompt using a free model.
- Observe whether the same limit error persists.
Screenshot
Operating System
mac OS
Terminal
Mac Os Terminal
Activity
opencode-agent commentedon Oct 25, 2026
Thanks for the clear write-up, and sorry about this. It's frustrating to wait past the reset time you were shown and still be blocked in both Desktop and the CLI.
The free-message allowance and its reset time are counted and enforced by the OpenCode Zen (Console) service for your account, not by the OpenCode app. The app only shows the error and reset time the service sends back, so the team has to check this on the account and service side. Billing and account support isn't handled in GitHub issues. Please email help@anoma.ly with the details, such as:
If you've already emailed, the team will get to it, especially now that we've seen it here.
Please keep email addresses, account information and payment details out of this public issue and put them only in the email.
Other people have reported similar problems, which may help:
The bot will close this issue in 1 day.
opencode-agent commentedon Oct 26, 2026
Hi @ABHISHEK-COLLABWE, I'm closing this issue now. Billing and account support is handled by email, not in GitHub issues. If the free-usage limit is still blocking you after the reset time, please email help@anoma.ly with the details, and the team will look into it there. Please keep account and payment details out of this public issue. Thanks for the clear report, and sorry for the trouble.