--- title: OpenAI resets Codex and ChatGPT Work usage limits after... description: OpenAI reset usage limits for all paid Codex and ChatGPT Work users after fixing a series of bugs that were causing overconsumption of allowances. Root causes... canonical: https://daily.dev/posts/openai-resets-codex-and-chatgpt-work-usage-limits-after-fixing-multiple-overconsumption-bugs-ftkpeycch twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: OpenAI resets Codex and ChatGPT Work usage limits after fixing multiple overconsumption bugs | daily.dev og:description: OpenAI reset usage limits for all paid Codex and ChatGPT Work users after fixing a series of bugs that were causing overconsumption of allowances. Root causes... og:url: https://daily.dev/posts/openai-resets-codex-and-chatgpt-work-usage-limits-after-fixing-multiple-overconsumption-bugs-ftkpeycch og:image: https://api.daily.dev/og/posts/FtkpEyCCH.png og:image:alt: OpenAI resets Codex and ChatGPT Work usage limits after fixing multiple overconsumption bugs og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # OpenAI resets Codex and ChatGPT Work usage limits after fixing multiple overconsumption bugs **[Collections](https://daily.dev/sources/collections)** · 2 min read · 2 upvotes · 1 comments ## Summary OpenAI reset usage limits for all paid Codex and ChatGPT Work users after fixing a series of bugs that were causing overconsumption of allowances. Root causes included compaction retaining old images, memory workers looping on stop hooks, goals continuing past their stop condition, automations running too frequently, subagents escalating unnecessarily, redundant computer history summarization, unneeded rolling task summaries, and MCP tool results being double-encoded. Depending on usage patterns, allowances should now stretch 10% to 50% further. OpenAI also added architectural safeguards and internal alerts to catch regressions, and is building in-app usage breakdowns. ## Content OpenAI has reset usage limits for all paid Codex and ChatGPT Work subscribers, and this time the reset comes with a round of bug fixes that should make those limits stretch further going forward. Depending on how you use Codex, you should see your usage go 10% to 50% further than before. The team went through thousands of user reports to track down what was eating through allowances faster than expected. Here's what they found: **Compaction** was keeping old images around, sometimes bloating context enough to trigger compaction again. After the fix, usage dropped around 10% for users who work heavily with images. **Memory workers** could inherit Stop hooks and keep running when the hook wouldn't let them finish. This hit fewer than 1% of users, but the worst cases were pretty bad - one thread checked whether it could stop 15,000 times. **Goals** could finish and then keep going past the intended stop condition, or the model would retry broken tools indefinitely. Some examples consumed between 15% and 70% of a weekly allowance in a single session. **Automations** with custom schedules were sometimes running more frequently than configured. **Subagents** - smaller models like Luna were occasionally pulling in more capable helpers without being asked. The orchestrating model could also request sub-agents to run in /fast mode even when it wasn't running that way itself. **Computer History** was repeatedly summarizing overlapping activity. In some cases this consumed up to a fifth of the weekly allowance on its own. **Rolling task summaries** were triggering extra background requests on ordinary turns, adding about 1% to token usage each time. **MCP** had two issues: some tool results were being encoded twice, and tool instructions were getting cut off and fetched again. All of the above are fixed. OpenAI also says it has made architectural changes to prevent regressions and set up alerts if these patterns reappear. The team is also working on in-app usage breakdowns so you can see where your allowance is actually going. The reset landed at 6pm PST. OpenAI noted the timing coincides with the platform hitting 25 million active users. ## Questions this post answers ### Why did my Codex or ChatGPT Work usage limit get reset recently? OpenAI reset usage limits for all paid Codex and ChatGPT Work users after identifying and fixing multiple bugs that caused overconsumption of allowances. Depending on usage patterns, allowances should now last 10% to 50% longer. Fixes covered compaction, memory workers, goals, automations, subagents, computer history summarization, rolling task summaries, and MCP tool result encoding. _Track fixes like this as they roll out so Codex usage limits don't catch you off guard, via daily.dev._ ### What bugs were causing excessive token usage in OpenAI Codex? Several bugs caused excess token consumption: compaction retained old images and could re-trigger itself, memory workers got stuck looping on stop hooks, unfinished goals kept running past their stop condition (costing some users 15-70% of weekly allowance), automations ran too often, subagents escalated to more capable models unprompted, and computer history summarization consumed up to a fifth of some users' weekly allowance. _Developers debugging unexpected AI usage spikes can follow issues like these on daily.dev._ ### How much extra Codex usage allowance can I expect after OpenAI's bug fixes? Codex allowances should stretch roughly 10% to 50% further after OpenAI fixed multiple overconsumption bugs, depending on how a user relies on features like image-heavy compaction, goals, or computer history. OpenAI also added architectural safeguards with internal alerts to prevent these issues from recurring, plus upcoming in-app usage breakdowns. _Keep tabs on Codex allowance changes like this through daily.dev before they affect your workflow._ ## Community take How the wider developer community reacted, aggregated from 1 discussion and 846 comments across x (as of 2026-08-31). **TL;DR:** Reaction is dominated by frustration that the reinstated 5-hour rolling limit on Plus plans makes the weekly usage reset largely meaningless, since users hit the short-window cap long before they can burn through their weekly allowance. **Sentiment:** 10% positive · 15% mixed · 75% skeptical **The case for** - A few users appreciate that the reset is a free bonus and see it as OpenAI subsidizing compute for cheap plans. - Some note Pro/higher-tier plans aren't affected by the 5-hour limit and work fine. **The pushback** - Many Plus users say the 5-hour limit stops them from meaningfully using the weekly reset, calling it a bait-and-switch. - Some argue banked/delayed resets would be fairer than a fixed-time reset that not everyone can use. - Complaints that cheaper plans are being squeezed while OpenAI pushes users toward pricier tiers. - A subthread devolves into arguing over whether $20/month users have any right to complain given subsidized pricing. **By community** - x (heated): Replies swing between people excitedly planning to burn usage and a larger, more vocal group angry that the 5-hour limit undermines the reset, with side arguments about fairness and pricing. **Hottest debate:** Whether the reintroduced 5-hour rolling cap makes the weekly reset pointless, and whether Plus-tier users have grounds to complain given the subsidized price. **Open questions** - Will OpenAI remove or adjust the 5-hour limit for Plus users? - Could resets be banked/delayed so users can choose when to use them? **Highlights** > @thsottiaux Yeah kinda hard to do when the 5H Limit Bullshit only allows it to work for 10 mins and spend 15% actual usage before I have to wait 5 hours each time. Then the project resuming consumes 15% of the 5H rate. Literally ruined codex. > — [jackatlas942 on x · 4 points, 3 comments](https://x.com/jackatlas942/status/2094168452818710843) > @thsottiaux Do you guys really hate plus subs this much? Most won't even hit %50 of their limit because of 5hr. Why not a banked reset? You guys are literally punishing people who can't afford to pay monthly 100 or 200$. Clade is evil for what they're doing but at least they're openly doing > — [dorukisb on x · 6 points, 2 comments](https://x.com/dorukisb/status/2094151777679720919) > @thsottiaux It’s been no more than 10 minutes. 5h went from 96% to 0% on Ultra only using 2 sub agents and the task failed. Codex is useless for hard problem with the way 5h limits just completely cuck you. Even xHigh will tank your usage so you have to wait or risk a task failure. > — [ilostmy\_fish on x · 2 points, 3 comments](https://x.com/ilostmy_fish/status/2094162640885154227) > @thsottiaux Wouldn't it be better to give delayed resets so that people could choose when to do the reset? But in any case, thanks, since this is not necessarily Openai in front of people, but simply a gift for users > — [pparik\_\_ on x · 4 points](https://x.com/pparik__/status/2094150936352469180) > @GraemeVIP @OhioValleyEV @thsottiaux The 5 hour limit does nothing to lower monthly usage by the way…it’s just there to stabilize peak hours. Which is what i’d say if they didn’t already prove that inference is flawless even with the 5 hour limit completely removed. > — [blex1\_ on x](https://x.com/blex1_/status/2094176439293669534) **Source threads** - [x](https://x.com/thsottiaux/status/2094144275957350900) · 0 points · 846 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#openai](https://daily.dev/tags/openai), [#chatgpt](https://daily.dev/tags/chatgpt), [#openai-codex](https://daily.dev/tags/openai-codex) [View this post on daily.dev](https://daily.dev/posts/openai-resets-codex-and-chatgpt-work-usage-limits-after-fixing-multiple-overconsumption-bugs-ftkpeycch) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"OpenAI resets Codex and ChatGPT Work usage limits after fixing multiple overconsumption bugs","url":"https://daily.dev/posts/openai-resets-codex-and-chatgpt-work-usage-limits-after-fixing-multiple-overconsumption-bugs-ftkpeycch","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/openai-resets-codex-and-chatgpt-work-usage-limits-after-fixing-multiple-overconsumption-bugs-ftkpeycch"},"datePublished":"2026-08-29T20:53:05.345Z","dateModified":"2026-08-31T11:48:53.728Z","description":"OpenAI reset usage limits for all paid Codex and ChatGPT Work users after fixing a series of bugs that were causing overconsumption of allowances. Root causes...","image":"https://pbs.twimg.com/media/HQ6vpUIWwAAYdLI.jpg","thumbnailUrl":"https://pbs.twimg.com/media/HQ6vpUIWwAAYdLI.jpg","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/openai-resets-codex-and-chatgpt-work-usage-limits-after-fixing-multiple-overconsumption-bugs-ftkpeycch","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"ai-agents,openai,chatgpt,openai-codex","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"OpenAI resets Codex and ChatGPT Work usage limits after fixing multiple overconsumption bugs"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/openai-resets-codex-and-chatgpt-work-usage-limits-after-fixing-multiple-overconsumption-bugs-ftkpeycch#faq","mainEntity":[{"@type":"Question","name":"Why did my Codex or ChatGPT Work usage limit get reset recently?","acceptedAnswer":{"@type":"Answer","text":"OpenAI reset usage limits for all paid Codex and ChatGPT Work users after identifying and fixing multiple bugs that caused overconsumption of allowances. Depending on usage patterns, allowances should now last 10% to 50% longer. Fixes covered compaction, memory workers, goals, automations, subagents, computer history summarization, rolling task summaries, and MCP tool result encoding. Track fixes like this as they roll out so Codex usage limits don't catch you off guard, via daily.dev."}},{"@type":"Question","name":"What bugs were causing excessive token usage in OpenAI Codex?","acceptedAnswer":{"@type":"Answer","text":"Several bugs caused excess token consumption: compaction retained old images and could re-trigger itself, memory workers got stuck looping on stop hooks, unfinished goals kept running past their stop condition (costing some users 15-70% of weekly allowance), automations ran too often, subagents escalated to more capable models unprompted, and computer history summarization consumed up to a fifth of some users' weekly allowance. Developers debugging unexpected AI usage spikes can follow issues like these on daily.dev."}},{"@type":"Question","name":"How much extra Codex usage allowance can I expect after OpenAI's bug fixes?","acceptedAnswer":{"@type":"Answer","text":"Codex allowances should stretch roughly 10% to 50% further after OpenAI fixed multiple overconsumption bugs, depending on how a user relies on features like image-heavy compaction, goals, or computer history. OpenAI also added architectural safeguards with internal alerts to prevent these issues from recurring, plus upcoming in-app usage breakdowns. Keep tabs on Codex allowance changes like this through daily.dev before they affect your workflow."}}]} ```