ChatGPT Pro account is shown as Plus in Codex CLI/TUI
Summary
My ChatGPT account is a Pro account, but Codex CLI/TUI is showing the account as Plus. This makes it unclear whether Codex is using the correct subscription entitlement for long-running CLI sessions.
Environment
- Codex CLI:
codex-cli 0.142.5 - Platform: Linux x86_64 on an HPC login node
- OS reported by
codex doctor: Red Hat Enterprise Linux 8.8.0 - Auth mode reported by
codex doctor:chatgpt - Stored API key:
false - Stored ChatGPT tokens:
true - Model shown in TUI:
gpt-5.5 xhigh
What I checked
I verified two active Codex CLI sessions using different CODEX_HOME locations:
Session A:
CODEX_HOME=/scratch/.../algo_work
codex login status: Logged in using ChatGPT
Session B:
CODEX_HOME unset, so default ~/.codex is used
codex login status: Logged in using ChatGPT
The two auth.json files have the same SHA256 checksum, so both sessions are using the same stored ChatGPT login token. I did not inspect or print token contents.
codex doctor reports auth is configured, but it does not expose the subscription tier. The TUI/account banner is what appears to show Plus even though the ChatGPT account is Pro.
Expected behavior
If the authenticated ChatGPT account is Pro, Codex should either:
- show
Proin the CLI/TUI account/subscription display, or - provide a clear diagnostic if the CLI is intentionally using a different entitlement than the web ChatGPT subscription.
Actual behavior
The account appears as Plus in Codex CLI/TUI, despite the account being Pro.
Reproduction steps
export CODEX_HOME=/scratch/.../codex_home
codex login --device-auth
# Complete auth in browser using a ChatGPT Pro account
codex login status
codex doctor
codex
Then inspect the account/subscription indicator in the TUI.
Notes
- No
OPENAI_API_KEYis set in the active Codex process environment. - The sessions are using ChatGPT login token auth, not Platform/API-key auth.
- A useful improvement would be for
codex login statusorcodex doctorto print a sanitized account tier/plan field so users can verify whether Pro/Plus/Team entitlements are being applied correctly.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗