[Feature]: Multi-Account Session Rotation for Claude & ChatGPT Subscriptions with Automatic Failover

[Hassan220022]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/desktop

Problem or use case

Claude Pro/Max and ChatGPT Plus/Pro subscriptions have per-account usage limits (e.g., Claude's hourly message cap, ChatGPT's GPT-4o usage window). When a user hits that limit mid-session, t3code completely stops working until the cooldown resets — which can be 1–5 hours. Users who have multiple Claude or ChatGPT accounts (personal, work, family) have no way to register all of them and let t3code automatically continue on a different account without any manual intervention.

Proposed solution

Add a subscription account pool per provider (Anthropic Claude, OpenAI ChatGPT) that allows users to add multiple logged-in accounts. When the active account's session hits a rate limit or usage cap, t3code silently switches to the next available account and continues the request transparently.

Key behaviors:

1. Account pool per provider — Users add multiple Claude accounts and/or multiple ChatGPT accounts in Settings. Each account is authenticated via OAuth / session cookie (same flow as the current single-account login), just repeated for each added account.
2. Automatic failover on limit detection — When the active session receives a "You've reached your limit" / 429 / usage-exhausted response, the proxy intercepts it and retries the identical request using the next healthy account in the pool. The user never sees a limit error unless all accounts are exhausted.
3. Per-account cooldown tracking — Once an account hits its limit, it's marked as cooling down with a timestamp. t3code periodically checks if it has recovered (e.g., hourly reset) and automatically returns it to the active pool when ready.
4. Status dashboard in Settings — A clear list of all added accounts per provider showing:
   • 🟢 Active — in use right now
   • 🟡 Cooling down — limit hit, resets in ~2h 14m
   • 🔴 Session expired — needs re-login
5. Graceful total exhaustion — If every account across the pool is cooling down, show a clear message like "All Claude accounts are currently rate-limited. Next account resets in 1h 42m." with a countdown, instead of a cryptic error.
6. No interruption to context — The switch happens at the request level. Chat history and in-progress context are preserved — the user's coding session continues as if nothing happened.

Why this matters

This is the most common pain point for power users of AI coding assistants. Claude's hourly cap is aggressively low during peak usage, and a 2–4 hour forced break mid-feature is genuinely damaging to developer flow. Users who pay for multiple accounts (e.g., a personal Claude Max and a work Claude Pro) currently get zero benefit from that investment inside t3code — they have to manually log out, log in as a different account, and re-establish context. Automatic rotation would make t3code the most resilient AI coding assistant available for subscription users, with zero extra cost to the user beyond what they already pay.

Smallest useful scope

• Add up to 3 accounts per provider in Settings via the existing auth flow
• On any rate-limit / usage-cap response, retry the request with the next account in the list
• Show which account is currently active with a simple indicator in the UI (e.g., "Claude – Account 2 of 3")
• No cooldown timer, no auto-recovery check needed for v1 — just linear fallback through the list

Alternatives considered

• Manual account switching — Current workaround. Requires logging out, logging in, and fully re-establishing context. Completely breaks flow.
• Waiting for the limit to reset — 1–5 hours of forced downtime. Unacceptable for professional use.
• Using raw API keys instead — Bypasses the subscription entirely. Users who pay for Claude Max/ChatGPT Pro subscriptions shouldn't have to also pay API rates separately just to get uninterrupted access.

Risks or tradeoffs

• Session storage security — Multiple session tokens need to be stored with the same security care as the current single session (OS keychain, never logged or synced).
• Provider ToS — Anthropic and OpenAI's terms should be reviewed to confirm that automated session rotation across owned accounts is permissible. This is different from credential sharing — each account would be legitimately owned and paid for by the same user.
• Session expiry — OAuth tokens expire. The UI must clearly flag when an account needs re-authentication so the pool stays healthy without silent failures.

Examples or references

• This mirrors how some power users manually use session token rotation in browser extensions today — this would just make it native and automatic inside t3code.
• Similar request patterns exist in the Claude community for tools like Cursor and Windsurf where users have asked for the same capability.

Contribution

• I would be open to helping implement this.

[juliusmarminge]

it is possible to do this today, but we are not sure how okay anthropic are with this so we're not encouraging it as a first party feature. but you can add 2 claude providers in a way to satisfy your requirement