The short answer
Run /status in an active Codex CLI session to see your remaining limits, or open the usage dashboard at chatgpt.com/codex/settings/usage for the current limits and reset times. To keep the numbers visible on your Mac without opening either, use a usage tracker that reads them for you, such as Edith's Codex usage limits tracker, Usage, which shows them in the menu bar next to Claude and Cursor.
How Codex limits work
When you sign in to Codex with a ChatGPT plan, local Codex messages and Codex cloud tasks share your plan's allowance. OpenAI's Codex pricing page gives estimates in local messages per 5-hour period, and says weekly limits may also apply. The real number depends on the model and on how much each task reads and writes, so a percentage is more useful than a message count.
If you reach a limit in the middle of a turn, OpenAI says the agent can finish that turn. After that you wait for the reset, buy more credits on plans that offer them, or run Codex with an API key billed at API rates.
Method 1: /status in the Codex CLI
Built into Codex
Type /status during a session
Inside a running codex session, type /status. OpenAI documents it as the way to view your remaining limits from the CLI. It also confirms which account and model the session is using, which matters if you switch between a personal and a work plan.
Method 2: the Codex usage dashboard
Official, in the browser
Open chatgpt.com/codex/settings/usage
Sign in with the same ChatGPT account Codex uses and open chatgpt.com/codex/settings/usage. It lists your current limits and when each one resets, and it covers cloud tasks as well as local CLI work.
Where the built-in methods fall short
- They answer only when asked. A long Codex run can use most of a 5-hour window while you are in a meeting, and nothing tells you until the next turn fails.
- /status needs a session. You cannot glance at it from another app.
- The dashboard is a browser tab. It is easy to forget, and it shows nothing about which repository used the tokens.
- Codex is rarely the only agent. If you also use Claude Code or Cursor, you end up checking three places.
The Edith way: Usage
Usage asks the Codex CLI on your Mac for its rate limits, so it needs Codex installed and signed in, and nothing else. It shows the 5-hour window and the weekly window as rings with a reset countdown, in the app and in the menu bar. Separately, it reads the session history Codex keeps on your Mac to show tokens and cost by day, model and repository.
- 1
Install Usage
The same Usage extension covers Codex and Claude, so if you already have it for one, skip this step.
- 2
Make sure Codex is signed in
Usage reuses the Codex CLI's own sign-in. If
codexruns and is logged in, there is nothing else to set up. - 3
Read the limits
ed usage limitsprints Codex first, then Claude, Cursor and Grok, with the percent used and the time until each window resets. Add--refreshto poll again with Edith open. - 4
Get warned before the cap
Turn on limit alerts in Usage settings. Edith warns when a window is nearly full and when your current pace would reach the cap before the reset, and tells you when a window that reached 90 percent has reset.
Codex history is stored under the source id codex, so you can pull Codex-only numbers into a script:
ed usage sources
ed usage summary --range week --source codex
ed usage daily --source codex
ed usage limits --json | jq -r '.[] | select(.provider == "codex") | .weekly.percent'Reading the numbers well
The weekly percent is the one to plan around. A 5-hour window resets within the same working day, but a weekly window that is 70 percent used on a Tuesday changes how you schedule the rest of the week. Usage's alerts watch the pace, not just the total: an alert fires when the rate of the last stretch would hit the cap before the reset, and stays quiet after a short burst followed by a pause.
If you run several Codex sessions at once, the coding agent dashboard shows which ones are working, blocked or done, so you can stop the one burning the most before the window runs out. The Codex on Mac page collects everything Edith does for Codex, and the Claude Code usage limits guide covers the Claude side.
Common questions
Does Edith need my OpenAI password or an API key?
No. It talks to the Codex CLI that is already signed in on your Mac.
Why does the weekly window show but the 5-hour one does not?
Edith shows what Codex reports. OpenAI's pricing page says Pro plans currently have no 5-hour limit, and when Codex reports no 5-hour window the row shows as not reported instead of a guessed number.
Can I turn off Codex limits but keep the rest?
Yes. ed config set codexLimitsEnabled false stops polling Codex limits while Claude and Cursor keep working.