Skip to content

Free usage exceeded bug #58926

Closed as not planned
Closed as not planned

Description

@BenjiITEst

The day before yesterday, I hit the free usage limit. It told me I had to wait for hours, so I waited 1 day —but today, it’s telling me again that I’ve reached the limit. I haven’t done anything; I only sent one prompt, and it didn’t even process anything, yet the message appeared. Now it’s telling me I have to wait another 15 hours. I tried changing the API key, but that didn’t work.

Activity

  1. opencode-agent commented on Oct 25, 2026

    @opencode-agent
    Contributor

    Hi @BenjiITEst, thanks for reporting this, and sorry about the trouble. Waiting a full day and then getting a new countdown after just one prompt is really frustrating.

    Your free usage allowance, when it resets and the retry countdown are all counted and enforced by the OpenCode Zen service for your account, not by the app on your machine. The app only shows the error the service sends back. That's why changing the API key didn't help, and why the team needs to look into it directly.

    Billing and account support isn't handled in GitHub issues, so please email help@anoma.ly with the details: roughly when you first hit the limit, when it came back, the model you were using and the countdown you see. If you've already emailed, the team will get to it, especially now that we've seen it here. Please keep email addresses, API keys and other account details out of this public issue and put them only in the email.

    Other people have reported the same problem recently, for example #58911, #58876 and #58902.

    The bot will close this issue in 1 day.

  2. panRBP commented on Oct 25, 2026

    @panRBP

    I had the exact same issue after updating to v1.9.14 — the app got stuck in an endless 429 FreeUsageLimitError countdown loop.

    Here’s how I fixed it.

    It turned out that the Desktop app seemed to be stuck with a corrupted or outdated session state in its local storage/cache. Also, the built-in updater incorrectly reported that v1.9.14 was already the latest version, while downloading a fresh installer and running it installed v2.1.4.

    Steps to fix on Windows

    1. Download and extract the standalone OpenCode CLI binary.

    2. Re-authenticate using GitHub CLI:

    .\opencode.exe auth login

    Select GitHub deployment → Device Flow.

    3. Verify that the CLI works with a free model:

    .\opencode.exe run "Hello" -m opencode/deepseek-v4.1-flash-free

    4. Completely uninstall OpenCode Desktop.

    5. Clear the local application data and cache folders.

    Run the following in PowerShell:

    Remove-Item -Path "$env:APPDATA\OpenCode", "$env:LOCALAPPDATA\OpenCode", "$env:USERPROFILE\.opencode" -Recurse -Force -ErrorAction SilentlyContinue

    6. Reinstall OpenCode Desktop using a freshly downloaded installer.

    In my case, this installed v2.1.4 and bypassed the broken updater state from v1.9.14.

    After following these steps, everything worked smoothly again, with no more quota errors.

    Hope this helps anyone else running into the same issue!

  3. opencode-agent commented on Oct 26, 2026

    @opencode-agent
    Contributor

    Hi @BenjiITEst, I'm closing this issue because the team handles free usage limits and account problems by email, not on GitHub. If the limit still hasn't reset for you, please email help@anoma.ly and include roughly when it started, the model you used and the countdown you see. If you've already emailed, the team will get to it. Please keep account details and API keys out of this public issue. Thanks for reporting it, and sorry for the trouble.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions