Skip to content

Big Pickle: Rate limit exceeded for more than 4 hours and does not reset after restarting OpenCode #52696

Closed as not planned

Description

@youngrok093-cpu

Description

OpenCode Big Pickle has been unusable for more than 4 hours because of a persistent rate-limit error.

Environment:

  • OS: Windows
  • Provider: opencode
  • Model: big-pickle

OpenCode log confirms:
providerID=opencode
modelID=big-pickle

Error:
AI_APICallError: Error from provider (Console): Rate limit exceeded. Please try again later.

The same error has continued for more than 4 hours.

I completely closed OpenCode and restarted it, but the same error occurred again.
Multiple attempts at different times produced the same result.

Please confirm:

  1. Is this an account quota, a Big Pickle model-specific rate limit, or an upstream/provider-side problem?
  2. What is the exact cooldown/reset period?
  3. Is there a way to check the remaining time until the limit resets?
  4. Is Big Pickle currently experiencing a service-side rate-limit or availability problem?
  5. Is any action required on my account, or should I simply wait for the limit to reset?

This is currently blocking an active production automation maintenance task.

Thank you.

Plugins

None

OpenCode version

No response

Steps to reproduce

  1. Open OpenCode on Windows and use provider "opencode" with model "big-pickle".
  2. Send any normal request. OpenCode returns: "Error from provider (Console): Rate limit exceeded. Please try again later."
  3. Completely close and restart OpenCode, then try again. The same error persists for more than 4 hours.

Screenshot and/or share link

Image

Operating System

Windows 10

Terminal

Windows PowerShell / OpenCode terminal

Activity

  1. youngrok093-cpu commented on Oct 2, 2026

    @youngrok093-cpu
    Author

    Update: This issue is still blocking an active production automation system. The rate-limit error has persisted and OpenCode remains unusable. If possible, could you please confirm whether this is an account-level, model-level, or service-side limit, and provide the expected reset time or a workaround? Thank you.

  2. Tarquinen commented on Oct 20, 2026

    @Tarquinen
    Member

    Thanks for reaching out, and sorry this didn't get a reply sooner.

    We don't handle billing, account or usage-limit support in GitHub issues. The app only shows the error the OpenCode service returns, and the reason for a limit or a billing problem can only be checked in the service's own records. Please email help@anoma.ly about this. If you've already emailed that address, please reply in the same thread with anything new.

    Please keep payment details, email addresses and account information out of this public issue and put them only in the email. We'd suggest editing this issue to remove any you've shared here.

    Closing this issue, since support will continue over email.

    — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions