Codex 什么时候重置？
分两件事，别混在一起：
你自己的额度窗口。官方按 5 小时窗口给用量估计，周限额也可能适用。每个账户的恢复时间都不一样，没有「每天几点」「每周一」这种统一时钟。看你自己的：打开 Codex 官方用量页，或在 Codex CLI 里输入 /status。
官方送的额度。OpenAI 不定期给所有付费用户「全员重置」或发「重置卡」，只在 X 上宣布，事先不预告。本站时间线记录每一次，「下次」永远写「尚未公布」，因为官方确实没公布过。
最近的官方动态
-
Claude提额Claude Code 云端会话正式上线，现有订阅者一次性送试用额度：Pro 送 $100、Max 送 $250，10 月 7 日前领适用：Pro / Max 现有订阅者 · 额度独立于用量限额，只能用于云端会话；本地触顶可转云端继续。CLI 输入 /claim-credit 领取，需连接 GitHub。 · @ClaudeDevs · 原帖 ↗ 原帖 2 ↗ 原帖 3 ↗
原帖
ClaudeDevs@ClaudeDevsCloud sessions are officially available and out of research preview! They let you keep Claude Code working, even when your laptop is closed. Existing subscribers get a one-time credit to try them: $100 on Pro, $250 on Max.
-
Codex重置卡GPT-6 Sol 与 Luna 发布，Plus/Pro/Business 全员存入一张重置卡适用：Plus / Pro / Business · API 价格永久降 50%。 · @thsottiaux · 原帖 ↗
原帖
Tibo@thsottiauxGPT-6 Sol and Luna are out. Not only are they a very significant improvement across the board, but also in writing and general "you know when you try it" quality. We are also permanently reducing the API price by 50% making both of them viable for a ton of new usecases and making your usage go further too, even on the subscriptions. And one more thing. We are loading a banked reset into all accounts of our Plus, Pro and Business users. Let's go! https://openai.com/index/introducing-gpt-6-sol-and-luna/
-
Claude重置卡Opus 5.5 发布：5 小时限额上调 20%，Pro/Max/Team 各得一张随时可用的重置卡适用：Pro / Max / Team · Opus 5.5 更便宜，同样额度多用 25%。 · @ClaudeDevs · 原帖 ↗
原帖
ClaudeDevs@ClaudeDevsOpus 5.5 performs at the level of Fable 5.1. It's ~30% faster and ~40% cheaper than Opus 5 per task. In Claude Code: - 5-hour session limits increase 20% today - Opus 5.5 is priced lower, so it goes 25% further within limits - Pro, Max, and Team users get a reset to use anytime
-
Codex全员重置重置已全部生效适用：全部 · @thsottiaux · 原帖 ↗
原帖
-
Codex全员重置修复多项质量问题，Astra 用户重置适用：Astra 用户 · 禁用了一个影响约 4 到 5 千人的实验。 · @thsottiaux · 原帖 ↗
原帖
Tibo@thsottiauxHi Astra users. A reset and a quick update on quality issues that have been posted around. Working with some of you, we have found and fixed the following issues: - Some skills written for previous models were triggering too often or preventing the model from checking its work. - An opt-in context management experiment that could cause early stops or replies to older messages. We've disabled it. Our rough estimate is that 4-5k users were affected by this experiment. - We've also removed some badly configured engines that resulted in a measured quality degradation for a long tail of traffic flowing through them. We’ve also made some more minor improvements and things should feel significantly better across the board. More consistent follow-through, better tracking of your latest message, and better checks on the work as it’s going through the motions. The examples posted and all the users who worked directly with us were incredibly useful in helping fix things quickly. Always grateful for this incredible community. And of course, a reset is also landing by midnight today.