openclaw - 💡(How to fix) Fix Feature: Support multiple OAuth profiles per provider:email (e.g., Business + Pro Individual plans)

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Discussed in agent session on 2026-05-18. This would significantly improve resilience for power users who maintain multiple OpenAI subscriptions.

Root Cause

Discussed in agent session on 2026-05-18. This would significantly improve resilience for power users who maintain multiple OpenAI subscriptions.

Code Example

auth-profiles.json:
  "openai-codex:[email protected]": { "chatgptPlanType": "team", "accountId": "xxx" }
  "openai-codex:[email protected]": { "chatgptPlanType": "team", "accountId": "xxx" }
RAW_BUFFERClick to expand / collapse

Use Case

Some users have multiple ChatGPT/OpenAI plans tied to the same email address:

  • A ChatGPT Team/Business plan (workspace account)
  • A ChatGPT Pro Individual plan (personal subscription, same email)

Currently, OpenClaw stores OAuth profiles keyed by provider:email (e.g., openai-codex:[email protected]). When re-authenticating, the new profile overwrites the existing one for the same email, even if it targets a different plan/workspace.

Current Behavior

auth-profiles.json:
  "openai-codex:[email protected]": { "chatgptPlanType": "team", "accountId": "xxx" }
  "openai-codex:[email protected]": { "chatgptPlanType": "team", "accountId": "xxx" }

Both profiles above share the same Business accountId. There is no way to register a third profile for the Pro Individual plan under [email protected].

Desired Behavior

Allow multiple OAuth profiles per provider+email, differentiated by chatgptPlanType or accountId. This would enable fallback rotation across:

  1. openai-codex:[email protected] (Team/Business)
  2. openai-codex:[email protected] (Team/Business)
  3. openai-codex:[email protected] (Pro Individual)

When one plan hits subscription limits or rate limits, the agent rotates to the next available profile.

Suggested Approach

Option A: Key profiles by provider:email:planType or provider:email:accountId instead of just provider:email.

Option B: Allow an array of profiles per provider:email, with the OAuth flow presenting a workspace/plan picker.

Environment

  • OpenClaw: 2026.5.12
  • Provider: openai-codex
  • Auth: OAuth (Codex harness)

Context

Discussed in agent session on 2026-05-18. This would significantly improve resilience for power users who maintain multiple OpenAI subscriptions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Feature: Support multiple OAuth profiles per provider:email (e.g., Business + Pro Individual plans)