Can't use Codex after sucsess log in via ChatGpt account, 2 weeks pro acc were wasted...

Resolved 💬 3 comments Opened Oct 23, 2025 by JMsource123 Closed Nov 25, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.47.0

What subscription do you have?

pro

Which model were you using?

gpt-5-codex

What platform is your computer?

Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 x86_64

What issue are you seeing?

<img width="1078" height="605" alt="Image" src="https://github.com/user-attachments/assets/4eea725a-03bb-4ac1-8ea9-da49a7d33eb0" />
Codex CLI: Cannot authenticate with my ChatGPT Pro account — CLI reports “Authorized” but does not actually work
Summary

For the past two weeks, I’ve been unable to properly use Codex CLI while logged in under my ChatGPT Pro account.
Although the CLI shows “Authorized” after running codex login, subsequent commands behave as if no valid session exists. Some commands fail outright; others require an API key and fall back to the BYO (Bring Your Own Key) mode, which bypasses Pro plan quotas and capabilities.

The issue persists even after multiple logout → login cycles.

What steps can reproduce the bug?

Uploaded thread: 019a11af-1f0f-7c20

What is the expected behavior?

Logging in via “Sign in with ChatGPT” (device-code flow) should authenticate the CLI with my ChatGPT Pro account.

After successful login, all CLI commands (codex exec, codex edit, integrations, etc.) should work normally and respect my Pro quotas and model access.

No need to supply a personal API key when I’m already a Pro subscriber.

Additional information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 10 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #5553
  • #5456
  • #5550
  • #5067
  • #5552

Powered by Codex Action

pakrym-oai contributor · 10 months ago

From logs I can see you have a proxy set up on http://127.0.0.1:3067/, can it be related?

riobah · 10 months ago

Had the same issue, doing logout & relaunch / login as recommended here fixed it