Repository navigation
Free usage limit reached despite zero usage shown (OpenCode 2.2.x) #60419
Description
I'm experiencing an issue with the free message quota.
OpenCode reports that I have exhausted my daily free messages, but the usage dashboard appears to show zero (or no meaningful usage), and I am unable to send any requests.
Versions affected:
OpenCode Desktop: 2.2.2
OpenCode CLI: 2.2.0
Error message (Desktop):
Plain Text
You've used today's free messages.
They reset at 30 Oct 2026, 21:35.
Error message (CLI):
Plain Text
You've used today's free messages.
They reset at 12:35 AM, 10/31/2026.
Additional observations:
The reset time shown by Desktop and CLI is inconsistent.
The issue persists across both Desktop and CLI.
I appear to have valid stored credentials.
Switching integrations does not resolve the issue.
The account appears blocked even though usage does not seem to reflect exhausted quota.
Authentication status:
Plain Text
$ opencode auth list
OpenCode Go OpenCode Go stored
OpenCode Console OpenCode Console stored
OpenRouter API key stored
Steps to reproduce:
Open OpenCode Desktop 2.2.2 or CLI 2.2.0.
Attempt to send a message using the free tier.
Receive: "You've used today's free messages."
Wait until the displayed reset time.
Issue remains and no messages can be sent.
Expected behavior:
Free messages should become available after the reset time.
Usage counters should accurately reflect consumption.
Desktop and CLI should report the same reset time.
Actual behavior:
Account remains blocked.
"You've used today's free messages" is shown even when usage appears to be zero.
Different reset times are displayed between Desktop and CLI.
Environment:
Windows + WSL
OpenCode CLI 2.2.0
OpenCode Desktop 2.2.2
Thank you for looking into this issue.
Activity
opencodejr commentedon Oct 30, 2026
Thanks for the detailed report! I think this is a duplicate of #59387, the main issue for free-tier problems. One of the symptoms it lists is exactly this one: "You've used today's free messages. They reset at ..." and the reset never happens, even though usage shows little or nothing.
Possible duplicates and related issues, ordered by likelihood:
About the different reset times: 21:35 and 12:35 AM are exactly 3 hours apart. That is most likely the same reset time shown in two timezones, one used by Desktop on Windows and the other by the CLI inside WSL (you can compare
datein WSL with the Windows clock).Please add a short comment on #59387 with your versions, platform (Windows + WSL), the free models you tried and the exact error. Anything specific to your account goes by email to help@anoma.ly, not here.
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
Luism-cloud commentedon Oct 30, 2026
Confirmo que mi problema coincide con los inconvenientes de cuota gratuita descritos en esta incidencia.
Mi entorno es el siguiente:
He probado los modelos gratuitos Big Pickle y DeepSeek V4.1 Flash Free, pero todos aparecen como agotados y muestran el mensaje de que los mensajes gratuitos del día se han utilizado y se restablecerán a las 20:00.
El problema comenzó antes de actualizar a la versión 2.2.3 y continúa después de actualizar tanto CLI como Desktop. También he probado a crear sesiones nuevas y cambiar de modelo, sin obtener resultados.
Apenas he utilizado los modelos gratuitos, por lo que considero que podría existir un error en la contabilización del consumo o en el restablecimiento de la cuota diaria.
Espero que puedan revisar este problema. Gracias.
opencodejr commentedon Oct 31, 2026
We haven't heard back, so I'm closing this as a duplicate of #59387. That is the main issue for the "You've used today's free messages. They reset at ..." error when the reset never comes, and maintainers are collecting v2 reports there.
If it still happens on Desktop 2.2.2 or CLI 2.2.0, please add a short comment on #59387. Include your platform (Windows + WSL), the free models you tried, the exact error, and that your usage shows zero. For anything specific to your account, email help@anoma.ly and keep account details out of the public issue.
The 3-hour gap between the reset times on Desktop and the CLI is most likely the same time shown in the Windows and WSL timezones. Thanks for the detailed report!