Feature Request: Auto-resume CLI session when usage limit resets
### 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. <img width="548" height="219" alt="Image" src="https://github.com/user-attachments/assets/0fd2c533-1613-468f-8732-31499c642afb" /> I'd like Codex to **automatically continue the session at the reset time, without me being there**. **Behavior:** 1. Turn fails with usage limit reached. 2. Codex reads the reset time it already knows about (`resets_at` in `UsageLimitReachedError`). 3. Instead of erroring out, Codex sleeps until that time and then re-runs the same turn. 4. 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`: ```toml [usage_limits] auto_resume = true ``` That's it — that's the featur
Posted by ndycode on May 4, 2026, 8:34 PM
Tags
Related issues
- [BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
- Please deobfuscate the Python
- [Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
- # 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
- [FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
- Admin Materials and Surfaces
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
reliability (Software)
[BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
Feature Request: Auto-resume CLI session when usage limit resets
Please deobfuscate the Python
[Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
# 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
[FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Admin Materials and Surfaces
AMD Support
Feature Request: Auto-resume CLI session when usage limit resets
### 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. <img width="548" height="219" alt="Image" src="https://github.com/user-attachments/assets/0fd2c533-1613-468f-8732-31499c642afb" /> I'd like Codex to **automatically continue the session at the reset time, without me being there**. **Behavior:** 1. Turn fails with usage limit reached. 2. Codex reads the reset time it already knows about (`resets_at` in `UsageLimitReachedError`). 3. Instead of erroring out, Codex sleeps until that time and then re-runs the same turn. 4. 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`: ```toml [usage_limits] auto_resume = true ``` That's it — that's the featur
Comments (0)
No comments yet. Start the discussion.