anomalyco / anomalyco/opencode

Bug: Free usage quota does not reset after the expected period instead it extends for a longer time

Open
#50,091 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

I exhausted my OpenCode free usage quota yesterday at approximately 10:00 AM Nepal Time.
After that, OpenCode showed:

Free usage exceeded, subscribe to Go [retrying in ~20h]

I did NOT use OpenCode today at all but,Yesterday I used around 818,754 tokens.

However, today at approximately 9:07 AM Nepal Time, OpenCode was still showing:

Free usage exceeded, subscribe to Go [retrying in 73801s - attempt #1]

73801 seconds is approximately 20 hours 30 minutes.

This means I went through the entire cooldown period without using OpenCode, but the free quota still did not become available. Instead, I received another approximately 20-hour retry timer.

Expected behavior:
After the free usage quota reset period elapsed, I should have been able to use the free model again.

Actual behavior:
The quota remained unavailable and OpenCode started another approximately 20-hour countdown.

Timeline
Yesterday ~10:00 AM NPT — Free quota exhausted
Yesterday — OpenCode showed approximately 20-hour retry timer
Overnight — OpenCode was not used
Today ~9:07 AM NPT — Still blocked
Current message: Free usage exceeded, subscribe to Go [retrying in 73801s - attempt #1]

Impact

This effectively prevents me from using the free OpenCode model for another full day despite not using any quota today.

Environment

OS: Windows
Timezone: Nepal Time (UTC+5:45)
OpenCode version: 1.18.31
Model: Muse Spark 1.3 FREE

I don't currently have logs available.

Plugins

none

OpenCode version

1.18.31

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

Windows Terminal

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no source files, tests, or reproduction steps. Start by locating the free-quota reset and retry-timer entry points for OpenCode 1.18.31, then reproduce the timeline under UTC+5:45 on Windows; done means the free model becomes available after the expected cooldown.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.