The short answer
ChatGPT Work and Codex share your plan’s allowance for the same account and workspace. Check the official usage screen for its recovery windows; Chat model limits may be separate.
What to do next
- Open your Codex usage view and confirm the active account or workspace.
- Record each exhausted window and the recovery time shown beside it.
- Check whether an available reset credit is actually listed for your account.
- If you are planning a long task, allow for uncertainty: task complexity changes usage.
Choose the situation that matches
Short window exhausted; weekly usage remains
Wait for the exhausted window or inspect the options offered in your account. Remaining weekly usage alone does not establish that you can continue.
Weekly window exhausted
Save that window’s displayed recovery time. Moving between Work and Codex does not provide a fresh allowance.
A saved reset is available
Read the affected windows and expiry before redeeming in the official app. Afterwards, recheck the usage screen and update any old timers.
Check the result
Return to the affected feature and try one appropriate request. If it works, resume gradually. If it fails, compare the new notice with the original before repeating a step.
Still blocked?
Prepare the exact error, affected feature, app or browser version, account workspace, and date with timezone. Send these only through the provider’s official support channel; omit passwords, keys and private content that is not needed.
Common questions
Can a public reset arrive before my weekly reset?
An announced extra reset is a separate event. Check its eligibility and then confirm that your own allowance changed.
Why did one task use more than another?
Model choice, task complexity and context can affect consumption. Message count alone is not a dependable budget.
Source & scope
Vendor documentation supports the product context. The checklist is LimitReset editorial guidance and cannot diagnose a private account.
OpenAI · shared Work and Codex allowance ↗