← All guides

Codex says usage limit or upgrade to Plus despite available usage

Compare the same account’s usage page and client error to distinguish exhaustion from sign-in issues.

Updated

Start here

Check the usage dashboard first. If exhausted, wait for its reset time; if allowance remains, verify the account and sign in again.

On this page

1. Open the matching usage page

  1. Check the plan, remaining allowance and reset time. Match the client’s account and workspace.
  2. In CLI, run codex login status in the terminal and /status in the chat box. API-key users should check API billing and limits.

Open Codex usage →

2. Follow the displayed result

  1. If exhausted, save progress and wait for the displayed reset. For request-rate limits, retry when allowed.
  2. If allowance remains, save work, sign out and back in, then send “Reply only OK, without using tools.”

Sign in again →

3. Optional CLI startup comparison

  1. Run codex --help and confirm --no-daemon is listed. Exit the current CLI normally, then run the command below.
  2. Test a short message. This comparison is for interactive CLI; do not combine it with --remote or codex agents.
codex --no-daemon

4. Check the result

  1. After a successful short response, try a small task and check for further errors.
  2. Record both results if only one startup method works. Signing in again or changing startup mode does not replenish exhausted allowance.

5. Contact support

  1. Send screenshots of usage and the client error, plus the sign-in method and reauthorization result.
  2. Hide account details so support can help distinguish usage limits from client issues.

Contact support →

Useful links