/status shows stale usage limits on first run, requires a second /status to display correct values

Open 💬 1 comment Opened Apr 20, 2026 by TabanAziz

What version of Codex CLI is running?

codex-cli 0.122.0

What subscription do you have?

plus

Which model were you using?

gpt-5.4-high

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

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

PowerShell

What issue are you seeing?

When I run /status, the usage limit remaining values shown are stale. They reflect a previous state rather than my actual current usage. To see the correct, up to date values I have to run /status a second time.
Expected behavior: the first /status invocation should display the current usage limits.
Actual behavior: the first /status displays outdated usage limits. Only a second consecutive /status shows the real values.
No error message is produced. The command returns successfully, the numbers are just wrong on the first call.

What steps can reproduce the bug?

1.Start Codex (or use an existing session) and send a few prompts so that usage is consumed.

2.Run /status. Observe the usage limit remaining values displayed.

3.Immediately run /status again without doing anything else.
The displayed usage limit remaining values are different from step 2 and reflect the actual current state.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗