[ENHANCEMENT] OpenAI (ChatGPT Plus/Pro OAuth): support multiple accounts / account switching

[loject]

Problem (one or two sentences)

When using the OpenAI provider via "Sign in with ChatGPT" (Plus/Pro OAuth, no API key), Roo Code effectively supports only a single logged-in account. Switching between personal/work accounts requires manual logout/clearing sessions outside the extension, which is slow and error-prone.

Context (who is affected and when)

Affects users who have multiple OpenAI/ChatGPT accounts (e.g., personal + work / different orgs) and need to switch between them during normal development. This comes up whenever you need different billing, org/workspace access, or you test behavior across accounts.

Desired behavior (conceptual, not technical)

Allow using multiple OpenAI/ChatGPT accounts in Roo Code and switching between them without manual browser/session cleanup.

Two acceptable options:

1. Support multiple saved accounts for the OpenAI (ChatGPT OAuth) provider and let the user quickly switch the active account.
   OR
2. Allow creating multiple OpenAI provider configurations (profiles) where each configuration can be authorized with a different OpenAI account, so different projects/workspaces can use different accounts.

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan:

Approach: Profile-Scoped OAuth Credentials

The current implementation uses a singleton OpenAiCodexOAuthManager with a single storage key for OAuth credentials. All OpenAI Codex profiles share the same OAuth session, making it impossible to use multiple accounts.

Proposed Solution

Associate OAuth credentials with individual provider profiles, allowing each "OpenAI - ChatGPT Plus/Pro" profile to be authorized with a different OpenAI account:

Changes Required

1. Modify OAuth credential storage (src/integrations/openai-codex/oauth.ts):

• Change from a single global key (openai-codex-oauth-credentials) to profile-scoped keys (e.g., openai-codex-oauth-credentials-{profileId})
• Update OpenAiCodexOAuthManager to accept a profile ID parameter for credential operations
• Add methods to manage credentials for specific profiles

2. Update API handler (src/api/providers/openai-codex.ts):

• Pass the active profile ID to the OAuth manager when getting/refreshing tokens
• Ensure each profile uses its own OAuth session

3. Update webview message handler (src/core/webview/webviewMessageHandler.ts):

• Include profile context when handling sign-in/sign-out messages
• Ensure sign-out only clears credentials for the current profile

4. Update UI components (webview-ui/src/components/settings/providers/OpenAICodex.tsx):

• Show which account is linked to the current profile (display email from credentials)
• Allow re-authenticating a profile with a different account

User Workflow

1. User creates a new provider profile and selects "OpenAI - ChatGPT Plus/Pro"
2. User clicks "Sign in with ChatGPT" - this authorizes THAT specific profile
3. User can create additional profiles and sign in with different ChatGPT accounts
4. Switching profiles automatically uses the correct OAuth credentials
5. Each profile shows its linked account email for clarity

Benefits

• Leverages existing profile infrastructure
• Each project/mode can have a different ChatGPT account
• Clear UX showing which account is linked to which profile
• No need for a separate "account switcher" UI

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[loject]

@roomote

[roomote-v0]

Thanks for the approval! I will proceed with implementing the profile-scoped OAuth credentials for OpenAI ChatGPT Plus/Pro. I will open a draft PR to share progress shortly.

[roomote-v0]

Implementation Complete

I have implemented the profile-scoped OAuth credentials feature for the OpenAI Codex provider.

PR: #11098

Key Changes

1. Profile-scoped credential storage: OAuth credentials are now stored with profile-specific keys using the pattern openai-codex-oauth-credentials-{profileId}. This allows each provider profile to have its own OAuth session.

2. In-memory caching per profile: Added Map-based caching to efficiently store credentials per profile, with de-duplication of concurrent token refresh requests.

3. UI updates: The settings page now shows "Signed in as {email}" when authenticated, and passes the profile ID to sign-in/sign-out operations.

4. Backward compatibility: Legacy global methods are maintained and delegate to profile methods with no profileId for compatibility with existing code.

How it works

• When a user signs in with OpenAI Codex, credentials are stored under a key specific to the current profile
• When switching profiles, the authentication state updates to reflect that profile's credentials (or lack thereof)
• Users can have multiple OpenAI accounts - one per profile - without conflicts

All tests pass and the implementation follows the approved design from the earlier discussion.

[Erotemic]

Would this also allow for effectively adding multiple different providers? I have multiple ollama servers I can use, and it would be really nice to have one vscode session talking to on server and a second one talking to a different one. Or just having the ability to switch between different preconfigured providers via a dropdown box. That UX seems like it would satisfy this feature request as well as what I'm looking for. Does the current PR already do that?

[saintlabs]

Hi, does this help to switch between chatgpt profles when you run out of tokens?