Stop Hiding Weekly Usage: ChatGPT Work Now Drains the Codex Quota Without Warning #35166

What variant of Codex are you using?

Web - Firefox

What feature would you like to see?

Feature request

For years, users understood a simple distinction: normal ChatGPT usage on the web did not consume the same weekly allowance used by Codex. Then, practically overnight, OpenAI introduced the artificial distinction between “Chat” and “Work” inside the same ChatGPT interface, without clearly warning users that Work consumes the shared Codex allowance while Chat does not.

That distinction is not obvious, intuitive, or properly disclosed. To the average user, both modes are simply ChatGPT on the web. There is no prominent warning before using Work, no clear explanation that every request is draining the same limited weekly pool used by Codex, and no persistent indicator showing how much allowance remains.

Users are therefore encouraged to keep using the product normally until, without meaningful advance warning, the interface suddenly refuses to respond and displays:

“You’re out of Work usage for now.”

Only at that point does the interface prominently offer the user the option to buy credits or upgrade.

This is unacceptable. OpenAI changed the practical meaning of web usage by introducing “Work vs. Chat,” concealed the most important consequence of that distinction, and then failed to display the remaining allowance anywhere in the main web interface. A paying customer should not have to discover a hidden Usage Dashboard after access has already been blocked.

Whether intentional or not, the current design feels deliberately opaque: the mechanism that consumes the allowance is poorly explained, the remaining balance is hidden, and the purchase buttons become highly visible only after the user has exhausted what was included in the subscription.

The main problem is that there was no clear, persistent indication in the normal interface showing:

• How much of the weekly allowance had already been consumed
• How much usage remained
• Which products were consuming the shared allowance
• When the allowance would reset
• That exhausting Codex usage would also disable Work on the ChatGPT website

The percentage is available only inside a separate Usage Dashboard. Requiring paying customers to find and repeatedly open a hidden dashboard is not adequate for a quota that can disable an important part of the service.

The interface prominently displays buttons to purchase credits or upgrade after the allowance is exhausted, but it does not provide equally prominent information about the included usage that the customer has already paid for.

Expected behavior

ChatGPT, Work, Codex Web, the desktop app, and the IDE extension should display a persistent usage indicator such as:

“Weekly usage: 82% used — resets Tuesday”

or:

“Weekly usage remaining: 18% — resets Tuesday”

The interface should also provide warnings at reasonable thresholds, for example:

• 50% used
• 75% used
• 90% used
• Nearly exhausted

When the allowance is shared across products, the UI should explicitly state that Codex and Work consume the same usage pool.

Ideally, the usage page should also provide a clear breakdown showing how much usage was consumed by Codex, Work, the desktop app, and other relevant surfaces.

Why this matters

Customers cannot manage a limited weekly allowance when its status is hidden from the main product interface. Discovering the limit only after the service has stopped working creates unnecessary confusion and makes the usage system feel opaque.

Usage limits on a paid subscription should be transparent before they are reached, not only after access has already been blocked.

Additional information

• Subscription: ChatGPT Plus
• Usage source: Codex
• Affected surface: ChatGPT Work on the web
• Observed result: Work became unavailable after the shared weekly allowance was exhausted