Add a toggle to prevent automatic use of purchased Codex credits

even better (maybe additional to the local in app setting) a use credits toggle on the https://chatgpt.com/codex/cloud/settings/usage or now https://chatgpt.com/codex/cloud/settings/analytics page so it can be hard switched off

Please also cover banked Codex usage resets, not only whether purchased credits may be used.

A useful control would be a setting under Usage & billing such as:

When included usage is exhausted:

• Prefer a banked reset, then use purchased credits
• Use purchased credits and keep banked resets saved
• Ask me each time

The main use case is an in-progress, long-running task that starts when only a small amount of included usage remains—for example 14% or 2%. If “Prefer banked reset” is enabled, Codex should automatically redeem one available reset and continue the task before spending purchased credits. When disabled, the reset should remain banked.

The UI should clearly show which source will be used next and should not silently switch an active task to purchased credits contrary to the selected preference.

Didn't new such switch wasn't there till I saw half of my credits got used without notice from the vscode extension like it always being offered once the limits quota exhaustion.
The credits use switch is really a mandatory thing in both codex app and chatgpt work.

Thanks @nanderer — I agree that a global “Use purchased credits” switch on the Usage & billing/Analytics page would be useful, so credit spending can be completely disabled.

And @nos1609 — agreed. Since ChatGPT Work mode and Codex share usage, credits, and limits, this control should work consistently across ChatGPT Work, the Codex app, and the VS Code extension, without silently switching to purchased credits.

I think this could be expanded into a draggable priority control under Usage & billing:

When included usage runs out

Drag these actions into the preferred order:

• Pause the task
• Continue with purchased credits
• Redeem a banked reset and continue

Codex would evaluate the actions from top to bottom. “Pause the task” would be a stopping point, so anything placed below it would not be used.

For example:

1. Continue with purchased credits
2. Pause the task
3. Redeem a banked reset and continue

This would mean: use purchased credits first; if they cannot be used, pause the task and do not redeem a banked reset.

It would also be useful to let users purchase banked usage resets directly, rather than offering only credit purchases. Users could buy one or more resets, save them for later, and decide where they belong in the priority order.

When several resets are available, Codex should use the reset with the earliest expiration date first. If multiple resets have the same expiration date, the oldest one should be used first.

There could also be an optional setting such as:

Automatically redeem a banked reset shortly before it expires

This would prevent unused resets from being lost. It should be opt-in, and the interface should clearly explain whether it temporarily overrides the normal priority order.

The interface should clearly show:

• Which resource will be used next
• The number of banked resets available
• Each reset’s expiration date
• The remaining purchased-credit balance
• The price and exact usage allowance of a purchasable reset
• Whether purchased resets expire
• Whether automatic redemption before expiration is enabled
• The behavior that will occur when the current limit is reached

This would give users predictable control over their tasks, saved resets, and spending.

Longer-term, this could support configurable budget steps—for example, spend up to $10 in credits, redeem the earliest-expiring reset, and then pause—but the initial version could begin with the three basic actions above.

It seem it is intentionally, imagine this you are on 99% left and it applies automatically and only give you benefit of 1% while you wanted to redeem when you are almost at 50%, so you almost lost your reset limit - this is very much frustrating