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

OpenAI has officially announced that it is bringing back a five-hour usage limit for Codex and ChatGPT Work specifically tailored for ChatGPT Plus subscribers. This update comes after several weeks during which users were restricted solely by a weekly usage cap.

During the preceding weeks, subscribers had to navigate their usage under a broader weekly limitation, which posed challenges for professionals relying heavily on these advanced tools for continuous coding and workspace tasks.

• 5-hour usage limits restored for ChatGPT Plus users
• Previously, users faced strict weekly-only usage caps
• Updates apply directly to Codex and ChatGPT Work tools
• The change aims to ensure fairer system resource distribution

Context behind the usage limit adjustments

Over the past several weeks, OpenAI implemented a broader weekly restriction model instead of shorter operational windows. While designed to manage capacity, this policy created hurdles for heavy users.

Professionals who rely on continuous coding assistance and workspace features found it difficult to budget their usage efficiently under a single sprawling weekly cap.

Benefits of the 5-hour window restoration

The reintroduction of the five-hour window aims to provide a more balanced distribution of platform resources and help active users better manage their workflows throughout the day without exhausting their allowances too quickly.

By bringing back these granular intervals, OpenAI helps developers maintain steady pacing throughout their workday while keeping platform infrastructure stable.

Implications for software developers and tech industry

For tech professionals and developers globally who integrate OpenAI models into their daily pipelines, predictable rate limits are essential for maintaining steady productivity and smooth integration of AI assistants into software development lifecycles.

Predictable limits remove friction from daily engineering workflows, ensuring that developer teams can rely on AI tooling without unexpected capacity bottlenecks during critical sprints.