Urgent.News

What's breaking now, across thousands of outlets.

AI

OpenAI restores 5-hour Codex and Work limits for ChatGPT Plus users

Following several weeks during which ChatGPT users were subject only to a weekly usage cap, OpenAI announced today that it is restoring a five-hour limit on Codex and ChatGPT Work for Plus subscribers. Here are the details.

OpenAI restores 5-hour Codex and Work limits for ChatGPT Plus users

OpenAI has decided to reinstate a five-hour usage limit for Codex and ChatGPT Work on ChatGPT Plus subscriptions, effective tomorrow. Engineering lead Thibault "Tibo" Sottiaux announced the change, stating that users will have to wait for their usage to reset or purchase additional credits once they hit either the five-hour or weekly limit.

OpenAI has also occasionally reset users' limits for free through promotions and referral offers. The five-hour limit was temporarily lifted for several weeks, during which only a weekly cap was in place. OpenAI mentioned the need to bring the five-hour limit back due to the need to manage load on their compute while keeping the plan generous in terms of weekly usage.

The company also explained that casual and new users on the Plus plan were accidentally exhausting their weekly usage and causing confusion. For now, the five-hour limit will not apply to Pro $100 and Pro $200 subscriptions. It is unknown if Enterprise or Edu accounts will be affected. Readers are encouraged to share their thoughts in the comments section.

Written by urgent.news from 9to5Mac's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at 9to5mac.com →

More in AI

My agent inflated its own state file to 49MB. Every check passed for three days.

I run an agent that wakes every four hours, does one thing, and writes its state back to STATUS.md . That file is its entire memory across sessions — without it, every wake starts from nothing.

  • Agent's state file inflated to 49MB due to code bug
  • Issue persisted undetected for three days despite daily checks
  • Three fixes implemented: size check, section ordering assertion, and structure verification

More from Tuesday 25 August →