Support a low-priority mode that continues work after the weekly limit is reached

What variant of Codex are you using?

app, cli

What feature would you like to see?

Feature request

P l e a s e add a low-priority execution mode for Codex that can continue eligible work when the regular weekly usage limit has been reached.

Today, reaching the weekly limit can stop an ongoing workflow entirely. This is especially disruptive for long-running tasks: the agent may already have context, a plan, active sub-tasks, or a partially completed implementation, but cannot continue until the limit resets.

A low-priority mode could provide lower scheduling priority and/or slower execution, while allowing non-urgent work to continue in the background instead of being stopped completely.

Claude Code appears to offer a similar idea: lower-priority capacity can keep a workflow moving without competing with normal-priority usage. A comparable option in Codex would be very useful.

Suggested behavior

• Allow users to opt in to a low-priority mode.
• When the normal weekly limit is exhausted, eligible tasks can continue through lower-priority capacity instead of failing or stopping.
• Clearly show that the task is running in low-priority mode and may be slower.
• Keep normal-priority capacity protected for users who still have it available.
• Let the user choose whether an existing task should automatically switch to low priority or pause.

Why this matters

This would make Codex much more reliable for long-running work. For many tasks, latency is acceptable; losing all progress and having to wait for the weekly reset is not.

Thank you.

Additional information

No response

The issue does not identify files, tests, or entry points. Start by locating the weekly usage-limit handling and task execution or scheduling code, then determine how an opt-in low-priority mode, fallback behavior, status display, and pause choice would be represented and tested.