There is a phone number that we do not own linked to our company chatgpt account, we can login to our various seat accounts and owner account but when we try to o auth via hermes command line it asks to do an o auth auth .openai.com/codex/device (we have done this often before when the session logs out) but NOW it’s re-directing to auth .openai.com/phone-otp/select-channel and asking to send a code to a cell phone that we do not have and we have never had associated with our account.
When I go to the same account via .chatgpt.com/#settings/Security Text message is off and Authenticator app is off.
How can we once again link our hermes bot to our codex seat via chat gpt o auth?
Hey @jordatech Just checking in - are you still running into this issue, or has it been resolved? Let us know, and we'll be happy to take another look if you're still having trouble.
It is clear there’s an issue with Codex misfiring and forcing users into the dead end sms verification loop. What is happening over there and what is the ETA when this is addressed and Codex becomes accessible to users. What is driving a need to have Codex user a separate authentication scheme while ChatGPT another? Why duplicate the efforts and why not roll back whatever thing that’s been introduced in May that’s slowly bumping people off?
Hello, unfortunately, we have the exact same error whenever we try to authorize anything codex related with our chat gpt subscription.
Yes, we would appreciate human assistance with this issue.
As a company we have actively started moving away from open AI subscriptions because of this issue.
When we reached out to open AI through the help center, we only were able to speak with a robot, which said it had no authority to help with anything, which was rather laughable.