CLI thinks I'm on a Lite plan (I am on 20x and have never seen "Pro Lite" marketed anywhere)

Resolved 💬 5 comments Opened Jul 11, 2026 by kendonB Closed Aug 4, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

0.144.1

What subscription do you have?

Pro 20x

Which model were you using?

NA

What platform is your computer?

Windows

What terminal emulator and version are you using (if applicable)?

Windows Terminal (Powershell)

What issue are you seeing?

<img width="529" height="18" alt="Image" src="https://github.com/user-attachments/assets/841c1904-296c-4196-bc51-2edf98de00bc" />

What steps can reproduce the bug?

Open Codex CLI, run /status

What is the expected behavior?

My Pro 20x account is ID'd correctly by the CLI

Additional information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 1 month ago

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

  • #31055

Powered by Codex Action

kendonB · 1 month ago

WSL CLI shows "Pro" in that spot

OneFreemanWill · 1 month ago

<img width="1121" height="1173" alt="Image" src="https://github.com/user-attachments/assets/ab376283-eff1-4a05-967d-6f67b0abba70" />

Same issue observed on two different Win 11 machines. One shows as Plus and the other as Pro Lite despite me having a full Pro (20x) account

Suhaibinator · 1 month ago

I’m seeing the same /status plan mismatch. My account is subscribed to the $200/month ChatGPT Pro plan, but Codex reports Pro Lite.

This may be more than a display issue: lately, my Codex limits have felt closer to the lower-tier plan I previously had. I do not yet have precise usage measurements to prove that the wrong quota is being enforced, so this is an observation rather than a confirmed calculation.

Could the maintainers confirm whether Pro Lite is only an incorrect label in /status, or whether the CLI/backend may be resolving my account to the wrong entitlement and applying reduced usage limits?

Uploaded diagnostic thread: 019f906a-d38c-76b0-a361-cf9ecc3f9e66

kendonB · 23 days ago

fixed