Confirmed live on Plus now. This isn’t just an announcement anymore — my Usage page now shows the restored 5-hour limit, alongside the weekly limit, shared across Codex, Work, Workspace Agents and ChatGPT for Excel.
This creates a particularly bad situation for long-running work.
I’m separately investigating an ordinary-Chat execution regression where my preserved historical GPT-5.6 Chat had worker-routed execution lasting 102m26s, while current genuine GPT-5.6 Thinking turns repeatedly land around 1541–1564 seconds (~25–26m) with work unfinished.
Work still receives the durable worker execution path on the same Plus account. But now that route is back behind the 5-hour gate.
So for heavy Plus workflows the practical choice is becoming:
ordinary Chat → long tasks currently hit the ~26m foreground execution class
Work/Codex → proper worker execution, but now the 5h gate is back
Separate issue, separate evidence, but together they make genuinely long autonomous work much harder on Plus.
I’d also really like OpenAI to clarify the current active-task behavior at the 5h boundary. Codex previously had a grace behavior where an already-running task could continue beyond the nominal limit. Current user reports indicate quota exhaustion can now strand active work instead.
If the 5h limit is needed for compute smoothing, please at least make it optional against the weekly allowance, or guarantee that an already-running task can reach a clean stopping point.
My ordinary-Chat execution evidence is here: