Skip to content

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

Closed

Description

@mguttmann

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!

Activity

  1. github-actions commented on Jan 16, 2026

    @github-actions
    Contributor

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

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

  2. mguttmann commented on Jan 16, 2026

    @mguttmann
    Author

    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 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