Codex CLI: /usage “redeem/reset limit” shows applied, but “usage limit reached” persists (macOS, codex-cli 0.145.0)

Open
#34,865 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
api, cli

Research direction

Start by reproducing the /usage “redeem/reset limit” flow in codex-cli 0.145.0 and inspect how the account/rateLimits/read refresh is handled. Compare the CLI and web state after the reset; done means an applied reset is reflected consistently and the usage block is cleared.

Written by the indexing model from the issue text.

Description

bug CLI rate-limits
What version of Codex CLI is running?

codex-cli 0.145.0

What subscription do you have?

Pro x20

Which model were you using?

gpt-5.6-sol

What platform is your computer?

Mac OS Tahoe

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

cmux

Codex doctor report

What issue are you seeing?

When I run /usage in Codex CLI and choose “redeem/reset limit …”, the CLI indicates the reset was applied, but I still see “usage limit reached” in the CLI and on web even after ~1 hour. Logging in on the web does not change the state, so it doesn’t look like a session cache issue.

What steps can reproduce the bug?

Open Codex CLI

Ensure you are in a “usage limit reached” state

Type /usage

Choose the option to “redeem/reset limit …”

Observe the “applied/success” message

Attempt to use Codex again (still blocked). Also check the web UI (still blocked).

What is the expected behavior?

After consuming an earned reset, the eligible Codex rate-limit window should be reset, and after refreshing limits (via account/rateLimits/read) the CLI/web should reflect that usage is no longer blocked.

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.