anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #2078] feat: introduce RPM rate limiting for providers/models pairs #10188

New Issue
Closed
opened 2026-02-16 18:14:48 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:14:48 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/2078

State: closed
Merged: No

Summary

Rate limit handing is currently missing. This PR introduces per provider/model pair rate limiting through the config file, adding the rpm field to limit.

Implementation is simple, it sleeps the request that would cause limiting in order to stay in the "message flow" so you don' t have to wait and re-prompt the model after you've hit limits.

"provider": {
    "google": {
      "models": {
        "gemini-2.5-pro":{
          "limit":{
            "rpm": 10
          }
        }
      }
    }
  }

The status bar has also been updated to show the ETA of the next request when being limited

image

Notes

I'm unsure if rpm should be nested under a rate object or not @thdxr ?

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/2078 **State:** closed **Merged:** No --- ## Summary Rate limit handing is currently missing. This PR introduces per provider/model pair rate limiting through the config file, adding the `rpm` field to `limit`. Implementation is simple, it sleeps the request that would cause limiting in order to stay in the "message flow" so you don' t have to wait and re-prompt the model after you've hit limits. ```json "provider": { "google": { "models": { "gemini-2.5-pro":{ "limit":{ "rpm": 10 } } } } } ``` The status bar has also been updated to show the ETA of the next request when being limited <img width="129" height="79" alt="image" src="https://github.com/user-attachments/assets/c610db8c-1e85-48be-a626-986a14d12a2e" /> ### Notes I'm unsure if `rpm` should be nested under a `rate` object or not @thdxr ?
yindo added the pull-request label 2026-02-16 18:14:48 -05:00
yindo closed this issue 2026-02-16 18:14:48 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#10188
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?