Ignore It, Change Cadence, or Pay $100? A Freelance Guide to ChatGPT's 5-Hour Codex Window

The five-hour Codex and ChatGPT Work window that returned for ChatGPT Plus on 25 August 2026 is not a verdict on the whole $20 plan. It is a session limit layered on top of a weekly allowance. For a freelancer whose work arrives in one or two packed days, that distinction is the decision.

Use this test:

Ignore the window if you rarely empty a session allowance, or if the reset lands while you can do other paid work.
Change cadence if you can split a sprint across several five-hour cycles without missing a client deadline.
Move to Pro if one forced pause costs more than the upgrade and the work cannot wait.

Pricing, limits, and plan copy below were checked against the linked pages on 28 August 2026. Confirm the current plan shown to your account before buying; prices and limits can move.

What returned on 25 August

9to5Mac reported on 24 August that OpenAI would restore a five-hour usage limit for Plus subscribers across Codex and ChatGPT Work the next day. The report says that after either the session or weekly limit is reached, the user can wait for a reset or purchase additional credits.

The article embeds an announcement from Thibault “Tibo” Sottiaux, OpenAI’s engineering lead for Codex and ChatGPT. He said the five-hour limit helps smooth compute load and reduces the chance that Plus users accidentally consume a full week at once. His time-bounded Pro statement was that the limit would remain disabled “for the upcoming months” on the $100 and $200 Pro subscriptions. That is not a permanent promise. Check the current limit on the exact Pro tier before upgrading.

OpenAI’s current US pricing page lists expanded Codex usage and ChatGPT Work on desktop, web, and mobile for Plus. It lists Pro as having 5x or 20x more usage and “Maximum Codex tasks.” The separate Plus help page confirms the US monthly Plus price is $20, while OpenAI’s Pro-tier help page identifies $100 and $200 Pro tiers with 5x and 20x the Plus usage allowance respectively.

The practical change is therefore not “Plus lost Codex.” Plus still includes it. The change is that a burst user can hit a session stop while weekly allowance remains.

Two user reports show the burst problem — not an average

An r/OpenAI thread created on 25 August UTC contains two specific reports worth treating as anecdotes:

One user said a five-hour allowance was exhausted within 20 minutes while 87% of the weekly limit remained. The same comment described a previous pattern of using Codex for a few hours on one day each week, then continuing the following week.
Another said 15 minutes on Sol High exhausted the session allowance while 83% of the weekly limit remained.

These are not a sample of all Plus accounts and do not establish a typical burn rate. They prove only that a session bucket can run out in minutes for some workloads while most of a weekly allowance remains. The two reports imply that those particular session fills represented roughly 13% and 17% of the weekly allowance. Do not turn that range into a published quota: model choice, task shape, context, and account limits can differ.

For a burst freelancer, the useful observation is simpler. A “five-hour limit” does not promise five hours of active coding. It names the reset window for a usage allowance. The Sol High comment reports consumption moving much faster than wall-clock time for that user; confirm how the live meter behaves on your own workload.

Worked example (hypothetical arithmetic, not a rate survey)

Replace these assumptions with your own rate, blocked time, and live plan prices:

Plus: $20 per month.
Pro $100: $100 per month.
Upgrade gap: $80 per month.
Billable rate: $100 per hour.
Client sprint: two days at six billable hours per day when unblocked, or $1,200 in billable time.

Path 1 — ignore it. You hit the session limit no more than once a month, and the reset overlaps email, review, meetings, or another paid job. Your true idle cost is $0. Paying another $80 for unused headroom does not clear the cost test, so Plus wins.

Path 2 — change cadence. You divide agent work into shorter blocks and put review or client communication between them. Suppose forced switching still creates 45 minutes of genuinely unusable time on each sprint day. Across two days that is 1.5 hours, or $150 at the assumed rate. Two such sprints in a month create $300 of modeled idle cost. If the pauses can be filled with paid work, that cost falls back toward $0.

Path 3 — move to Pro. At $100 per hour, recovering 48 minutes of billable time in a month covers an $80 upgrade gap. At $60 per hour the break-even is 1 hour 20 minutes; at $150 per hour it is 32 minutes. Those are calculator results, not promises that Pro will recover the time. Confirm that the current Pro tier removes the session constraint that is actually blocking you.

Credits are a fourth payment mechanism, but not a fourth working style. OpenAI’s credit help page says eligible Plus and Pro users can buy credits after included limits and may be able to enable auto top-up. Because the live credit rate and your task cost determine whether overflow beats an $80 upgrade, compare them in the Usage dashboard rather than guessing.

How to choose without plan hopping

Stay on Plus when session limits rarely stop paid work. The $20 subscription still includes expanded Codex and Work access, and a reset that overlaps other billable work has little economic cost.

Change cadence when the weekly allowance is valuable but cannot be pulled into one sitting. Checkpoint agent work before a likely stop. Put human review, tests, client messages, and specification work between usage windows. This is workflow design, not a way to evade limits.

Move to Pro when work is deadline-bound and the modeled monthly stall exceeds the upgrade gap. Recheck the $100 versus $200 tier, the current session rule, and the usage multiple. Sottiaux’s five-hour exemption was explicitly framed as applying for upcoming months, not forever.

Do not try to recreate a weekly burst by cycling accounts or gaming reset edges. OpenAI’s Pro help page prohibits sharing credentials and abusive access patterns, and a second account is not a dependable client-delivery control.

Use credits as a relief valve only after setting a budget. If overflow becomes weekly, compare the measured credit spend with the fixed plan gap again. If a pause becomes rare, move back to the cheaper plan at the normal billing boundary rather than changing plans around individual resets.

Decision checklist

Stay on $20 if the five-hour window rarely stops you or every wait can hold paid work.
Change cadence if a one- or two-day sprint can be split across reset cycles without missing the client clock.
Consider $100 Pro if one blocked stretch a month costs more than $80 and the current Pro tier removes the constraint.
Use credits carefully when overflow is rare and the measured credit cost is below the upgrade gap.

Sources checked 28 August 2026: 9to5Mac’s report, the r/OpenAI thread, ChatGPT pricing, Plus help, and Pro-tier help.