Skip to content

[status] Account plan displays "Free" despite active Plus subscription #4115

Closed

Description

@tm-iands

What version of Codex is running?

codex-cli 0.40.0

Which model were you using?

gpt-5-codex

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What steps can reproduce the bug?

  1. Sign in to Codex CLI with an OpenAI account that has an active Plus subscription.
  2. Open the Codex console and run /status.
  3. In the Account section, check the Plan value.

What is the expected behavior?

/status should display the correct subscription tier for the signed-in account. For a Plus subscriber, it should show Plan: Plus (or the accurate plan name), not Free.

What do you see instead?

/status reports Plan: Free under Account → Plan even though the signed-in account has an active Plus subscription.

Additional information

No response

Activity

  1. noessonlab commented on Sep 28, 2025

    @noessonlab

    same

  2. msjuck-cell commented on Oct 14, 2025

    @msjuck-cell

    Same Here,

    OpenAI Codex (v0.46.0)
    Ubuntu 24

    I logout both vscode and cli, but not working.

  3. scopendo commented on Oct 27, 2025

    @scopendo

    Similar but mine says Plus when I have a Pro subscription -- I had Plus at the time of logging in to the CLI.

  4. added
    authIssues related to authentication and accounts
    and removed
    windows-osIssues related to Codex on Windows systems
    on Nov 2, 2025
  5. etraut-openai commented on Dec 10, 2025

    @etraut-openai
    Contributor

    This should be fixed as of 0.66.0.

  6. perim commented on Dec 30, 2025

    @perim

    The problem persists with codex 0.77, just signed up for a Plus personal account, connected it with codex CLI and it keeps complaining about not having a ChatGPT plan. Signed out and in again multiple times. There are so many tickets on this issue, I really don't want to make yet another one.

  7. etraut-openai commented on Dec 30, 2025

    @etraut-openai
    Contributor

    @perim, if you're seeing this with the latest version of the CLI, then it's a different bug from the one that was fixed earlier. I'm going to lock this issue to prevent additional posts. Please attempt to log out and log back in, use the the /feedback slash command to upload your logs and create a new bug report that includes the thread ID. That will help us investigate the issue you're seeing.

  8. locked as resolved and limited conversation to collaborators on Dec 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    authIssues related to authentication and accountsbugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions