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.
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
- Check the plan, remaining allowance and reset time. Match the client’s account and workspace.
- In CLI, run codex login status in the terminal and /status in the chat box. API-key users should check API billing and limits.
2. Follow the displayed result
- If exhausted, save progress and wait for the displayed reset. For request-rate limits, retry when allowed.
- If allowance remains, save work, sign out and back in, then send “Reply only OK, without using tools.”
3. Optional CLI startup comparison
- Run codex --help and confirm --no-daemon is listed. Exit the current CLI normally, then run the command below.
- Test a short message. This comparison is for interactive CLI; do not combine it with --remote or codex agents.
codex --no-daemon4. Check the result
- After a successful short response, try a small task and check for further errors.
- Record both results if only one startup method works. Signing in again or changing startup mode does not replenish exhausted allowance.
5. Contact support
- Send screenshots of usage and the client error, plus the sign-in method and reauthorization result.
- Hide account details so support can help distinguish usage limits from client issues.