Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Solved
Issue with autofill and sign in automatically on ChatGPT/OpenAI
I've noticed an issue with autofill and sign in automatically on the login page for ChatGPT/OpenAI. Steps to reproduce Go to https://auth.openai.com/log-in/ Use 1Password to autofill the email ad...
tengl and Backspaze
I'm sorry that 1Password is selecting the wrong option when autosubmitting your login credentials on ChatGPT's website. This is a known issue that our development team is currently tracking, hopefully it will be fixed soon.
For the time being, you can workaround the issue by turning off autosubmit for ChatGPT:
- Click the 1Password icon in your browser's toolbar.
- Search for the login item.
- Click the three vertical dots in the top right of the window and choose Don't sign in automatically.
I hope that helps.-Dave
#37322
AJCxZ0 that's interesting and weird.
Yesterday, I could sign in manually by either typing, copy/pasting, or drag-and-drop the email address from 1Password.
Today, I get the same error 409 as you, no matter which of the manual methods I use. And it's the same on both https://auth.openai.com/log-in/ and https://auth.openai.com/log-in.
The original issue still remains for me though. If I re-enable auto-login, 1Password still just "clicks" the phone number button instead of the continue button.
The issue happens in Chrome, Firefox, Edge and on different devices running both Windows 10 and 11. However, Firefox on iOS does not have this issue, so it might only affect Windows devices.
I'm running the latest versions of Windows and the web browsers mentioned above.
The 1Password desktop app is running version 8.10.75 (81075001).
The browser plugin is using version 8.10.72.25 in Firefox and 8.10.72.27 in Chrome.
The message about error 409 is clearly on OpenAI's side, but the auto-login feature using the wrong button to continue on the login page, seem like a 1Password issue. I've never got the error 400 message about the password being too long, so that issue does not apply to my case.
