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

Feature Request: Multi-Account Support with Automatic Failover #6464

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

Originally created by @mguttmann on GitHub (Jan 16, 2026).

Originally assigned to: @thdxr on GitHub.

Feature Request

Description

I would like to request a feature that allows users to configure multiple accounts for the same provider. When one account reaches its session or weekly rate limit, the system should automatically switch to the next available account.

Use Case

When using AI providers like Claude / Claude Code, accounts often hit rate limits (session limits, weekly limits, etc.). Currently, this interrupts the workflow and requires manual intervention to switch accounts.

With multi-account support and automatic failover:

  • Users could configure multiple accounts (e.g., personal + work accounts)
  • When the primary account hits a limit, the system automatically uses the next account
  • This ensures uninterrupted workflow and better utilization of available quotas

Proposed Behavior

  1. Allow configuration of multiple accounts per provider (e.g., multiple Anthropic API keys or Claude accounts)
  2. Detect when an account reaches its rate limit (session/weekly/monthly)
  3. Automatically failover to the next configured account
  4. Optionally notify the user when a switch occurs
  5. Rotate back to the primary account when limits reset

Example Configuration (conceptual)

[providers.anthropic]
accounts = [
  { name = "primary", api_key = "..." },
  { name = "secondary", api_key = "..." },
]
failover = "auto"

Benefits

  • Uninterrupted workflow during rate limits
  • Better utilization of multiple subscriptions/quotas
  • Improved developer experience

Thank you for considering this feature!

Originally created by @mguttmann on GitHub (Jan 16, 2026). Originally assigned to: @thdxr on GitHub. ## Feature Request ### Description I would like to request a feature that allows users to configure **multiple accounts** for the same provider. When one account reaches its session or weekly rate limit, the system should **automatically switch to the next available account**. ### Use Case When using AI providers like Claude / Claude Code, accounts often hit rate limits (session limits, weekly limits, etc.). Currently, this interrupts the workflow and requires manual intervention to switch accounts. With multi-account support and automatic failover: - Users could configure multiple accounts (e.g., personal + work accounts) - When the primary account hits a limit, the system automatically uses the next account - This ensures uninterrupted workflow and better utilization of available quotas ### Proposed Behavior 1. Allow configuration of multiple accounts per provider (e.g., multiple Anthropic API keys or Claude accounts) 2. Detect when an account reaches its rate limit (session/weekly/monthly) 3. Automatically failover to the next configured account 4. Optionally notify the user when a switch occurs 5. Rotate back to the primary account when limits reset ### Example Configuration (conceptual) ```toml [providers.anthropic] accounts = [ { name = "primary", api_key = "..." }, { name = "secondary", api_key = "..." }, ] failover = "auto" ``` ### Benefits - Uninterrupted workflow during rate limits - Better utilization of multiple subscriptions/quotas - Improved developer experience Thank you for considering this feature!
yindo closed this issue 2026-02-16 18:04:18 -05:00
yindo commented 2026-02-16 18:04:18 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 16, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #8591: OAuth Marathon - multi-account credential rotation
  • #5748: Provider Auth v2 proposal with multi-account OAuth and same-request rotation
  • #8145: Multiple account login with Codex OAuth and round robin load balancing
  • #5391: Multiple auth profiles per provider
  • #6217: Multiple instances of the same provider
  • #7602: Native Model Fallback/Failover Support (related failover functionality)

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 16, 2026): This issue might be a duplicate of existing issues. Please check: - #8591: OAuth Marathon - multi-account credential rotation - #5748: Provider Auth v2 proposal with multi-account OAuth and same-request rotation - #8145: Multiple account login with Codex OAuth and round robin load balancing - #5391: Multiple auth profiles per provider - #6217: Multiple instances of the same provider - #7602: Native Model Fallback/Failover Support (related failover functionality) Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 18:04:18 -05:00
Author
Owner
Copy Link
Copy Source

@mguttmann commented on GitHub (Jan 16, 2026):

Closing as duplicate of #8591 (OAuth Marathon - multi-account credential rotation), which already covers this use case with automatic failover on rate limits and auth errors. Thanks!

@mguttmann commented on GitHub (Jan 16, 2026): Closing as duplicate of #8591 (OAuth Marathon - multi-account credential rotation), which already covers this use case with automatic failover on rate limits and auth errors. Thanks!
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#6464
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?