Repository navigation
[Bug] Free messages reset timer incorrectly adds 24 hours (+1 day) #60062
Description
Description
When the daily limit of free messages is exhausted, the countdown timer behaves incorrectly. Initially, the UI displays the reset time for the current day, but upon subsequent status updates (or sending another request), exactly 24 hours are erroneously added to the reset time.
Steps to Reproduce
- Exhaust the daily limit of free messages.
- Note the reset time message. In my case, it stated:
They reset at 03:40(implying a reset at 03:40 on the current day, October 29, 2026). - Perform another action (send a request, refresh the chat, or reload the interface).
- Check the updated limit message.
Expected Behavior
The reset time should remain consistent (today at 03:40), or if the 24 hours have already passed, the limit should reset. The cooldown time should not increase by 24 hours retroactively.
Actual Behavior
The timer "jumps" one day forward. The message changes to They reset at 30 Oct 2026, 03:40 (meaning the reset occurs tomorrow instead of today). Effectively, the cooldown is doubled or shifted indefinitely.
Screenshots
(Please attach your screenshot here when creating the Issue)
Environment
- OS: Windows 11 (latest version at the time of writing)
- App Version: [Specify the version, e.g., v2.1.4]
- Date of incident: October 29, 2026
Additional Context
The issue is likely related to the client-side reset time logic or incorrect parsing of the Retry-After header from the server. The application takes the initial time (03:40), realizes it has arrived/is arriving, and instead of unlocking access, adds 24 hours to the existing time.
Activity
opencodejr commentedon Oct 29, 2026
Thanks for the detailed report, @Ech-tex, and sorry about this. Waiting for the reset time only to see it move a day forward is frustrating.
I think this is a duplicate of #59387, the main thread for free-tier problems. It lists this exact symptom ("You've used today's free messages. They reset at ..." and the reset never happens), and other v2.1.4 users there describe the same 24-hour jump right after the reset time. The usage limit and the reset time come from the hosted free-tier service. The app shows the time the service sends back, so the shift isn't caused by the app's own timer.
Possible duplicates and related issues, ordered from most to least likely:
Please check that you're on the latest OpenCode v2 (
opencode --version, or Settings → About in Desktop). If it still happens, add a comment on #59387 with your version, the model you used and a screenshot, so all the reports stay in one place.The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
neriousy commentedon Oct 29, 2026
Closing this as a duplicate of #59387, the main issue for free tier problems.
Please read it first. Most of these reports are fixed by updating to the latest OpenCode v2 (download it manually from https://opencode.ai/v2/docs if you're on Desktop v1). If you're on the latest v2 and it's still broken, comment on #59387 with the details it asks for so everything stays in one place.
opencodejr commentedon Oct 30, 2026
Hi @Ech-tex, I'm closing this as a duplicate of #59387, the main thread for free-tier problems. It covers this same problem: the reset time jumps forward 24 hours instead of the limit resetting. We waited a day in case your problem was different, and there's been no reply.
If it still happens on the latest OpenCode v2, please comment on #59387 with your version (
opencode --version), the model you used and a screenshot, so all the reports stay in one place. Thanks for the detailed report, and sorry for the trouble.