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

feat: OAuth Marathon - multi-account credential rotation #6018

New Issue
Open
opened 2026-02-16 17:59:31 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 17:59:31 -05:00
Owner
Copy Link
Copy Source

Originally created by @jroth1111 on GitHub (Jan 14, 2026).

Originally assigned to: @thdxr on GitHub.

OAuth Marathon 🏃

Keep running when you hit the wall. Automatic credential rotation for OAuth providers - when one account hits rate limits or auth errors, opencode seamlessly switches to your next available credential within the same provider.

Note: This rotates between multiple accounts within the same provider (e.g., two OpenAI logins), not between different providers.

Works for all OAuth providers — both core providers and plugins.

For plugin authors: Plugins that manage their own multi-account pools internally must register each account via Auth.addOAuth() to benefit from this feature.

The Problem

Using OAuth providers with personal subscriptions often means hitting rate limits mid-session. Currently, when this happens, your request fails and you're stuck waiting.

Proposed Solution

Register multiple OAuth accounts for the same provider, and opencode will automatically:

  • Rotate on 429 - Rate limited? Next credential steps in
  • Retry on 401/403 - Force token refresh, failover if still failing
  • Recover from network errors - Transient failures don't stop the run
  • Track health - Cooldown periods prevent hammering exhausted credentials
  • All exhausted - Returns the last error response gracefully

How to Add Multiple Accounts

Run opencode auth login multiple times for the same provider:

opencode auth login   # Login with first account
opencode auth login   # Login with second account (adds, doesn't replace)

Architecture Overview

flowchart TD
    A[Provider.getSDK] --> B[createOAuthRotatingFetch]
    B --> C{fetchFn}
    C -->|429 Rate Limit| D[moveToBack + notifyFailover]
    C -->|401/403 Auth| E[markAccessExpired + retry]
    C -->|Network Error| F[recordOutcome + notifyFailover]
    C -->|200 OK| G[recordOutcome success]
    D --> H[Try Next Credential]
    E -->|Still fails| H
    F --> H
    H --> C

Use Cases

  1. Multiple OAuth subscription accounts for the same provider
  2. Resilience against transient auth failures and rate limits

Configuration (Optional)

Per-provider settings in opencode.json. Sensible defaults are used if omitted:

{
  "provider": {
    "openai": {
      "oauth": {
        "maxAttempts": 3,                // default: number of accounts
        "rateLimitCooldownMs": 60000,    // default: 30000
        "authFailureCooldownMs": 300000, // default: 300000
        "toastDurationMs": 5000          // default: 8000
      }
    }
  }
}

Demo

OpenAI Account 1 → 429 Rate Limited
               ↓ (automatic)
OpenAI Account 2 → 200 OK ✅
               ↓
Toast: "Rate limited on openai. Switching OAuth credential..."
Originally created by @jroth1111 on GitHub (Jan 14, 2026). Originally assigned to: @thdxr on GitHub. ## OAuth Marathon 🏃 Keep running when you hit the wall. Automatic credential rotation for OAuth providers - when one account hits rate limits or auth errors, opencode seamlessly switches to your next available credential **within the same provider**. > **Note:** This rotates between multiple accounts *within* the same provider (e.g., two OpenAI logins), not between different providers. Works for **all OAuth providers** — both core providers and plugins. > **For plugin authors:** Plugins that manage their own multi-account pools internally must register each account via `Auth.addOAuth()` to benefit from this feature. ### The Problem Using OAuth providers with personal subscriptions often means hitting rate limits mid-session. Currently, when this happens, your request fails and you're stuck waiting. ### Proposed Solution Register multiple OAuth accounts for the same provider, and opencode will automatically: - **Rotate on 429** - Rate limited? Next credential steps in - **Retry on 401/403** - Force token refresh, failover if still failing - **Recover from network errors** - Transient failures don't stop the run - **Track health** - Cooldown periods prevent hammering exhausted credentials - **All exhausted** - Returns the last error response gracefully ### How to Add Multiple Accounts Run `opencode auth login` multiple times for the same provider: ```bash opencode auth login # Login with first account opencode auth login # Login with second account (adds, doesn't replace) ``` ### Architecture Overview ```mermaid flowchart TD A[Provider.getSDK] --> B[createOAuthRotatingFetch] B --> C{fetchFn} C -->|429 Rate Limit| D[moveToBack + notifyFailover] C -->|401/403 Auth| E[markAccessExpired + retry] C -->|Network Error| F[recordOutcome + notifyFailover] C -->|200 OK| G[recordOutcome success] D --> H[Try Next Credential] E -->|Still fails| H F --> H H --> C ``` ### Use Cases 1. Multiple OAuth subscription accounts for the same provider 2. Resilience against transient auth failures and rate limits ### Configuration (Optional) Per-provider settings in `opencode.json`. Sensible defaults are used if omitted: ```json { "provider": { "openai": { "oauth": { "maxAttempts": 3, // default: number of accounts "rateLimitCooldownMs": 60000, // default: 30000 "authFailureCooldownMs": 300000, // default: 300000 "toastDurationMs": 5000 // default: 8000 } } } } ``` ### Demo ``` OpenAI Account 1 → 429 Rate Limited ↓ (automatic) OpenAI Account 2 → 200 OK ✅ ↓ Toast: "Rate limited on openai. Switching OAuth credential..." ```
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
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#6018
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?