What variant of Codex are you using?
CLI
What feature would you like to see?
When Codex hits the usage limit mid-task, the error already tells me exactly when the quota resets (e.g. "try again at 6:34 AM"). If that reset time falls while I'm asleep, the information is wasted — the task just dies and waits for me to wake up, find the session, and re-issue the prompt.
I'd like Codex to automatically continue the session at the reset time, without me being there.
Behavior:
- Turn fails with usage limit reached.
- Codex reads the reset time it already knows about (
resets_at in UsageLimitReachedError).
- Instead of erroring out, Codex sleeps until that time and then re-runs the same turn.
- I wake up to a finished or in-progress task instead of a frozen one.
Why this is basically free to implement:
The reset timestamp is already structured data in the protocol (codex-rs/protocol/src/error.rs → UsageLimitReachedError.resets_at) and the session already updates rate limits on this error (codex-rs/core/src/session/turn.rs ~line 1075). Today we just throw the timestamp away and crash the turn. The ask is: use it.
Make it opt-in so nothing changes for existing users:
codex --auto-resume-on-limit
or in ~/.codex/config.toml:
[usage_limits]
auto_resume = true
That's it — that's the feature.
Additional information
The screenshot shows the exact message in question: "try again at 6:34 AM". I was asleep at 6:34 AM. The agent could have just kept going.
Related: #15788 covers the App-side queueing of new prompts on usage limit. This is the CLI/session-resume sibling — same idea, different surface.
What variant of Codex are you using?
CLI
What feature would you like to see?
When Codex hits the usage limit mid-task, the error already tells me exactly when the quota resets (e.g. "try again at 6:34 AM"). If that reset time falls while I'm asleep, the information is wasted — the task just dies and waits for me to wake up, find the session, and re-issue the prompt.
I'd like Codex to automatically continue the session at the reset time, without me being there.
Behavior:
resets_atinUsageLimitReachedError).Why this is basically free to implement:
The reset timestamp is already structured data in the protocol (
codex-rs/protocol/src/error.rs→UsageLimitReachedError.resets_at) and the session already updates rate limits on this error (codex-rs/core/src/session/turn.rs~line 1075). Today we just throw the timestamp away and crash the turn. The ask is: use it.Make it opt-in so nothing changes for existing users:
or in
~/.codex/config.toml:That's it — that's the feature.
Additional information
The screenshot shows the exact message in question: "try again at 6:34 AM". I was asleep at 6:34 AM. The agent could have just kept going.
Related: #15788 covers the App-side queueing of new prompts on usage limit. This is the CLI/session-resume sibling — same idea, different surface.