Suspend and auto-resume at usage-limit reset instead of stopping the session

Open 💬 1 comment Opened Jul 19, 2026 by sadiq2697

What variant of Codex are you using?

CLI

What feature would you like to see?

When a session reaches the usage limit, the session stops. The reset time is shown, but the work is dropped, so I have to come back later, notice the limit has refreshed, and restart the task myself.

Instead of stopping, I would like the session to enter a suspended state that resumes on its own:

  1. Show a live countdown, e.g. Session resuming in 2:00:00, rather than ending the session.
  2. Hold the task state and context while suspended.
  3. At 0:00, resume automatically, continuing the same task without me having to restart it or re-explain what it was doing.

The countdown matters as much as the auto-resume. Seeing resuming in 1:47:22 makes it obvious the work is parked rather than lost, which is not clear today when the session simply stops.

This is most valuable for long unattended runs. Those are exactly the jobs most likely to cross a limit window, and exactly the ones where losing the run is most expensive. If my machine is still on, there is no technical reason the work cannot pick up by itself when the window refreshes.

Safety valve: this should be opt-in and bounded, for example "resume once" or a maximum number of windows, so an unattended session cannot spend a fresh limit window on work I would have cancelled had I been watching.

Additional information

Related to (but distinct from) #8310. That issue reports that when you resume after a rate limit, the session can lose task intent and continue on the wrong context. This request is about not requiring a manual resume in the first place. The two are complementary: keeping the session alive across the limit boundary, rather than tearing it down and rebuilding context afterwards, may well avoid some of the drift described there.

If the team prefers to treat this as part of #8310, that is reasonable, though I think the countdown-and-auto-resume behaviour is worth tracking as its own piece of work.

View original on GitHub ↗

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