Unable to log in: get_chatgpt_account_error during authentication in codex-cli
What version of Codex is running?
codex-cli 0.63.0
What subscription do you have?
Pro User
Which model were you using?
not login
What platform is your computer?
macos and windows
What issue are you seeing?
I’m unable to log into codex-cli.
When the browser-based login window opens, I consistently get the following error:
An error occurred during authentication (get_chatgpt_account_error). Please try again.
If this problem persists, contact the help center at help.openai.com and include the request ID db3778bec8d8454e6b628cbd91045bfc.
I can log into ChatGPT on the web without any issues using the same account.
The problem only occurs when trying to authenticate via codex-cli.
What steps can reproduce the bug?
What steps can reproduce the bug?
Install codex-cli (version 0.63.0).
Run the login command in a terminal:
codex login
(or any command that triggers the browser-based login flow, e.g. codex chat if it prompts for login)
A browser window opens to the OpenAI authentication page.
Complete the login in the browser.
Instead of completing successfully, an error page is shown with get_chatgpt_account_error, and the CLI never finishes authentication.
Explain the bug and provide a code snippet that can reproduce it. Please include session id, token limit usage, context window usage if applicable.
When I try to log in to codex-cli, the CLI opens a browser window for authentication. After I sign in, the browser shows an error and the CLI never gets authenticated. The same account can successfully sign in to ChatGPT on the web UI, so the issue seems specific to the CLI login flow.
Code snippet / command to reproduce:
codex login
or:
codex chat
(any command that triggers the browser login flow)
Observed error (from the browser page):
An error occurred during authentication (get_chatgpt_account_error). Please try again.
If this problem persists, contact the help center at help.openai.com and include the request ID db3778bec8d8454e6b628cbd91045bfc.
Session information:
Session ID (from the auth URL): authsess_WrqV00UqKhwa3DvTNkKmE6sW
Request ID (from the error message): db3778bec8d8454e6b628cbd91045bfc
Token limit / context window usage:
Not applicable. The error occurs during authentication, before any API calls, prompts, or context windows are used.
What is the expected behavior?
<img width="608" height="424" alt="Image" src="https://github.com/user-attachments/assets/42459752-b948-44a5-93b2-4861f5e89be6" />
Additional information
_No response_
8 Comments
One thing I suspect is that the payment method in Korea has recently been changed to billing in KRW (Korean won).
Also, the accounts that paid in KRW don’t seem to be able to log in to codex-cli.
Meanwhile, an account that was previously billed in USD can log in to codex-cli with its ChatGPT account without any problems.
I’m experiencing the same issue. I’m on a Mac environment, and both Codex CLI and the Codex VS Code extension fail to log in with the get_chatgpt_account_error message. I’m also in Korea with billing set to KRW, and I started the free trial yesterday.
I'm experiencing the same issue. My environment is WSL2.
I have the same issue.
My billing currency is KRW, and all authentication works fine except for the Codex CLI and OAI.
@azeek @junwoochoi @Rukkha1024 @Tocktock @Jaehyeon1020
I was able to resolve the issue using the following steps:
(Make sure the account you log in with here is the same one you want to use for Codex.)
(Codex opens the login window using the default browser.)
Thanks for the bug report. We think we have solved the problem. Please try logging in now. Let us know if you are still seeing the issue.
It seems that the OpenAI developers have finished their Thanksgiving holiday and have resumed work.
When I logged in this morning, I was able to log in normally.
Those who also experienced failures should try logging in again…
OpenAI developers, thank you for your hard work.
I'm glad to hear that it's working for you again.
@azeek, as you noted, many members of the codex team were taking a break over the past few days for the U.S. Thanksgiving holiday. Our regular service deployments were halted during this time, so it took longer than normal to resolve this issue. Apologies for any inconvenience this caused.
Happy coding!