Summary: The OAuth login flow for the ChatGPT dev community (and potentially other services) is experiencing a behavior where it automatically selects the wrong account based on prior sessions or logged-in services. This occurs even when the user is not logged into any Google services (e.g., Gmail) in the current tab but has an active session elsewhere.
Steps to Reproduce:
- Log into a Gmail account (or another Google service using the same OAuth provider) in one tab.
- Attempt to log into the ChatGPT dev community in another tab.
- The OAuth login process will default to the Gmail (or active OAuth service) account, even though the user is not actively logged in within the ChatGPT community.
Expected Behavior: The OAuth flow should prompt the user to manually select the account they wish to use, regardless of whether they are logged into that account in other tabs or services. The behavior should not rely on cookies or active sessions from other tabs, especially since the services being used (Gmail, etc.) are not connected to ChatGPT in any way.
Actual Behavior: The system automatically selects the wrong account, preventing the user from using the correct dev account. This creates confusion and friction in the login process, as the user cannot manually choose the correct account without additional workarounds (e.g., using an incognito window).
Additional Information:
- Clearing cookies and cache does not resolve the issue, as the auto-selection seems to be based on OAuth sessions across tabs.
- This issue occurs even when not logged into Gmail directly in the current tab.
Recommendation: The OAuth implementation should be improved to:
- Ask the user to select which account they would like to use at the point of authentication.
- Avoid auto-selection based on external sessions or cached data.
- Provide clear guidance or options when multiple accounts are detected.