Codex: quota, approvals and replies
Codex, in its desktop app and its CLI, gets everything Agent HUD offers: its limits at the edge of your screen, its requests answered on the HUD, and every turn's tokens in your statistics.
Updated 2026-10-29
At a glance
| Feature | Codex |
|---|---|
| Tokens and sessions | ✓ |
| Quota | ✓ |
| Live status | ✓ |
| Approvals | ✓ |
| Questions | ✓ |
| Replies | ✓ |
| One click back | ✓ |
| Turns and calls | ✓ |
What you see on the HUD
The most used Codex limit sets Codex's colour in the glow. Each limit is named by its length, such as five hours or a week, as the service reports it. The hover lists the limits with their resets or burn rates, the resets your account still has available, and Codex's sessions, those waiting for you first.
Approvals from the Codex app and the CLI, and the questions the Codex app asks, are answered on the HUD. The CLI's approvals come through Agent HUD's hook, which Codex runs only after you trust it, and only for turns that ask for your review; what Codex reviews by itself stays in Codex. A request you leave goes back after 10 minutes.
Which account does it count against?
The account Codex is signed in to: its email in its workspace. The same email in two workspaces stays two accounts, and a matching ChatGPT sign-in through Pi counts once. Accounts signed in under other Codex homes on this Mac can be followed side by side; they add their limits, not their sessions.
Running turns and replies
The HUD shows Codex working, waiting for you or done. A finished turn brings a New reply reminder, and one click takes you back: to the thread in the Codex app, or to the iTerm pane a CLI session runs in outside tmux. Each session's page lists its turns and calls. Sub-agents count inside the session that started them.
Agent HUD's hook lives in Codex's own settings: the release writes it while client hooks are on and removes it when they are off. A build from the source on GitHub does not install it yet.
What does Agent HUD read?
Codex's session logs, its archived sessions and its session index, for tokens, turns and sessions. For the limits it asks the installed Codex through Codex's own app server, without starting a thread or a turn. No message goes to a model, and no credential is stored.
On iPhone, Apple Watch and with other agents
On the same network as the release, iPhone and Apple Watch show Codex's quota, tokens and sessions without a subscription. Agent HUD Remote adds the rest, anywhere: read its conversations, send it messages, answer its requests, and turn a note spoken to your watch into a new Codex session on your Mac.
Through the built-in MCP server in the release, Codex and Claude Code can message each other's sessions, for a review or to hand over a task.
Questions
Is the context fill my remaining limit?
No. Context fill is the space used in one conversation; the limits measure your account's use. A new conversation frees context, not quota.