[FEATURE] Add Multi-Account Support and Round Robin Request Method

[shahid0]

Feature Description
Add support for configuring multiple accounts (OpenAI API keys/users) in the authentication backend. Implement a round-robin method so that incoming API requests are distributed evenly across all configured accounts.

Use Case
This feature will allow users to:

• Load-balance requests to OpenAI APIs across several accounts
• Reduce rate-limiting issues by spreading requests
• Use multiple API keys for increased throughput

Proposed Implementation

• Extend configuration to accept an array/list of API credentials/accounts.
• Refactor the request dispatch logic to rotate through available accounts using a round-robin algorithm.
• Ensure account selection is thread-safe (if applicable to the platform).
• Optionally allow prioritizing or weighting accounts if desired.

Compliance Consideration

• This feature is for personal development use
• This feature does not violate or circumvent OpenAI's Terms of Service
• This feature is not intended for commercial resale or multi-user access

Alternatives Considered

• Manually switching out API keys
• Simple failover without true load balancing

Additional Context
Would provide more resilient and efficient API utilization, especially under high-load scenarios.

[fjanicki]

How would that work with context caching if you round-robin all your requests? The load balancing should be chat/session-based, not per-message.

[shahid0]

How would that work with context caching if you round-robin all your requests? The load balancing should be chat/session-based, not per-message.

we can have an option for configuration (just like we have with anitgravity-auth-plugin).

and i forgot about caching thats my fault. i was thinking about rate limits that narrowed my POV, thanks for reminding. really appreciate your reply.

[Hobeom]

In my case, I have both a personal Pro subscription and a Team Plus subscription under a single account.

Would the proposed multi-account login support this kind of setup, where multiple subscription tiers are associated with one account? Or is this feature strictly intended for handling multiple separate API keys/accounts?

I’m particularly curious how account/session separation would work in this scenario.