I noticed something odd while checking the OpenCode Go usage dashboard: the monthly usage reset timer feels slower than expected.
In the screenshot, the dashboard shows:
- Rolling usage: 3%, resets in 1 hour 21 minutes
- Weekly usage: 1%, resets in 5 days 20 hours
- Monthly usage: 49%, resets in 17 days 23 hours
- “Use available balance after reaching usage limits” is turned off
OpenCode Go has three usage windows: short-term rolling, weekly, and monthly. What stood out here was not only the monthly usage percentage, but the way the monthly reset timer seemed to move more slowly than expected.
What felt strange?
The rolling and weekly usage numbers are low, so this does not look like an immediate short-term limit issue.
The monthly usage, however, is still shown at 49%. The number does seem to go down over time, but the reset timer has felt unusual: it stayed around “20 days” for a long time, and at times it seemed to advance by only one day every two real days.
That does not automatically mean there is a bug. It could be a display refresh issue, a subscription-cycle calculation, a timezone difference, or simply how OpenCode Go internally calculates usage windows. Still, if you read it as a normal “days until monthly reset” counter, the behavior feels confusing.
How are OpenCode Go limits defined?
According to the official OpenCode Go documentation, Go includes three usage limits:
- 5-hour limit: $12 of usage
- Weekly limit: $30 of usage
- Monthly limit: $60 of usage
These limits are defined by dollar-value usage, not by a simple request count. That means the number of requests you can make depends on which model you use.
Reference:
Are there similar reports?
I did not find an exact public report matching this specific symptom: “the monthly reset timer appears to move too slowly.”
However, there are related discussions.
On GitHub, there is a feature request asking OpenCode to expose Go plan usage data through an API. The issue specifically mentions the dashboard’s rolling, weekly, and monthly usage percentages with reset timers. This suggests that, for now, the web dashboard is the main place users can inspect this information.
On Reddit, one user asked whether the OpenCode Go monthly reset happens on the first day of each calendar month or 30 days from the subscription date. A reply said the monthly limit tracks the exact subscription cycle.
There is also a Reddit discussion about why OpenCode Go has rolling, weekly, and monthly limits at the same time. The complaint there is not the same as this timer issue, but it shows that the multi-window limit system can be hard to interpret.
Bug or expected behavior?
This screenshot alone is not enough to call it a bug.
Possible explanations include:
- The monthly reset is based on the subscription cycle, not the calendar month.
- The dashboard does not refresh or recalculate in real time.
- Timezone differences make the visible countdown feel off.
- The monthly percentage and the “resets in” value may be calculated from different internal data.
- The dashboard display may simply be delayed.
For now, the most accurate description is probably this: the monthly usage itself appears to be changing, but the monthly reset countdown does not feel intuitive.
How to verify it
If this keeps happening, the best approach is to keep screenshots over several days.
Useful details to record:
- Screenshot time and date
- Rolling usage and reset timer
- Weekly usage and reset timer
- Monthly usage and reset timer
- Rough amount of OpenCode Go usage during that period
- Main models used
With several screenshots, it should become clearer whether the monthly reset timer is actually lagging, or whether it is following a subscription-cycle rule that is just not obvious from the UI.
Summary
In this screenshot, OpenCode Go shows rolling usage at 3%, weekly usage at 1%, and monthly usage at 49%, with the monthly reset shown as 17 days 23 hours away.
The monthly number does seem to move, but the countdown behavior can feel strange if it stays on the same day count for a long time or advances more slowly than expected.
I could not find an exact matching public report, but OpenCode Go’s usage limits and reset windows are being discussed in the official docs, GitHub issues, and Reddit threads. If the behavior continues, keeping timestamped screenshots and reporting it to OpenCode would be the cleanest next step.
