AI News

重置监控

盯着 OpenAI 的 Tibo 和 Andrew 公布的 Codex 额度重置和重置卡发放:什么时候生效、谁能用上、原话怎么说。

全部为北京时间 · UTC+8

上一次重置卡发放:11月13日(按预计时间)

当前没有等待生效的重置

预计 北京时间 11月13日 08:30–13:30

不预测尚未宣布的下一次重置。Tibo 和 Andrew 一旦宣布,这里会显示预计生效时间与原帖。个人额度请在 Codex 内查看。

Tibo@thsottiaux进展

我们今天为 dots 发布了一些不错的更新,banked reset 已经激活,应该很快就会到账到每个人的账户里!

引用 @ChatGPT

你的 dot 现在拥有…… ⚡️ 更快的回复 💬 更少的术语 🫡 更好的跟进执行 而且,它们现在可以遵循你的自定义指令。在对话线程里告诉你的 dot 诸如该如何表现、或哪些操作需要你批准之类的事情。 “always talk in lowercase.” “Show me a draft before sending any emails.” 你也可以在移动端的 Customize > Behavior 中设置自定义指令和规则,或通过网页端和桌面端 dot 的菜单进行设置。

英文原文

We shipped some good updates to dots today and the banked reset has been activated and should land in everyones accounts sometime soon!

近 90 天额度重置
21 次
近 90 天发重置卡
11 次
重置间隔中位数
2.1 天
上次额度重置
10月28日

重置日历

点任意日期查看当天的重置、发卡和原帖。

浏览 61 个历史记录日期
2026年6月

本月 5 次额度重置 · 3 次发重置卡 · 0 次等待生效 · 0 次待确认

已确认应已生效,未确认已过预计时间,待确认已宣布,等待生效
最近相关原帖132 条公开记录
Tibo@thsottiaux

@ah20im 这里彻底搞定了

回复 @ah20im

团队一直在非常努力地修复用户遇到的问题。请继续提供反馈! 重置快乐!

引用 @thsottiaux

Codex 用量额度将在接下来一小时内再次完全重置,并且我们会向你的 bank 中额外发放一次重置,供你在接下来 24 小时内自行使用。 我们调查了有关 Codex 用量消耗速度快于预期的报告。并不存在一个核心问题,而是几个较小的问题对部分用户叠加造成了影响。 以下是我们发现并做出的更改: - 实际用量:Auto-review 变得更加主动,另一项更改触发了更多 subagent 工作,后台建议可能会运行两次,或在失败后过于频繁地重试。我们回滚了这些更改,并修复了建议调度、重复生成和重试行为。这应能减少不必要的后台 token 消耗,同时保留用户明确请求的工作。 - 用量报告:Auto-review 被错误地显示为 GPT‑5.4 用量,失败或受速率限制的请求仍被显示为轮次。Auto-review 现在显示为独立类别,只有成功的请求才计入轮次图表。受速率限制的请求从未计费,但此前显示有误。 - 即时缓解:我们在推出修复的同时重置了用量额度,随后在 CLI、桌面应用和用量后端发布了热修复。 - 预期情况:新的用量数据应更清晰,实际消耗应更低。历史图表可能仍会将 auto-review 显示在 GPT‑5.4 下,因为旧的轮次数据未被重新标记。有意执行更多工作的功能,例如 /goal、subagents 和更高推理等级,仍会自然消耗更多容量。 所有修复现已部署,我们还增加了更详细的监控,以便更早发现后台用量回归。我们会继续密切关注结果。 感谢你用 Codex 构建各种东西。

英文原文

@ah20im @ah20im absolutely cooked here

Tibo@thsottiaux发卡预告

Codex 用量额度将在接下来一小时内再次完全重置,并且我们会额外向你的 bank 中存入一次重置,供你在接下来 24 小时内自行使用。 我们调查了有关 Codex 用量消耗速度快于预期的报告。并不存在一个核心问题,而是几个较小的问题叠加影响了部分用户。 以下是我们发现并做出的更改: - 实际用量:Auto-review 变得更加主动,另一项更改触发了更多子代理工作,后台建议可能会运行两次或在失败后过于频繁地重试。我们回滚了这些更改,并修复了建议调度、重复生成和重试行为。这应能减少不必要的后台 token 消耗,同时保留用户明确请求的工作。 - 用量报告:Auto-review 被错误地显示为 GPT‑5.4 用量,失败或被限流的请求仍被显示为轮次。Auto-review 现在显示为独立类别,只有成功的请求才会计入轮次图表。被限流的请求从未计费,但此前显示有误。 - 即时缓解:我们在推出修复的同时重置了用量额度,随后在 CLI、桌面应用和用量后端发布了热修复。 - 预期情况:新的用量数据应更清晰,实际消耗应更低。历史图表可能仍会将 auto-review 显示在 GPT‑5.4 下,因为旧的轮次数据未被重新标记。有意执行更多工作的功能,例如 /goal、子代理和更高推理等级,仍会自然消耗更多容量。 所有修复现已部署,我们还增加了更详细的监控,以便更早发现后台用量回归。我们会继续密切关注结果。 感谢你用 Codex 构建并做各种事情。

引用 @thsottiaux

Codex team is in a warroom on a Sunday combing through logs and checking whether there is anything that could lead to increased usage drains for some users. Taking it very seriously and won't rest until we get to the bottom of it.

引用 @nicdunz

i think openai has gotten a bit too loose and funny acting. i think its time to get a little serious

英文原文

Codex usage limits will be fully reset again in the next hour and we will credit one additional reset into your bank for your own usage over the next 24 hours. We investigated reports that Codex usage was being consumed faster than expected. There wasn't one central issue, but a few smaller problems compounded for some users. Here's what we found and changed: - Actual usage: Auto-review had become more proactive, another change was triggering more subagent work, and background suggestions could run twice or retry too frequently after failures. We reverted the changes and fixed suggestion scheduling, duplicate generation, and retry behavior. This should reduce unnecessary background token consumption while preserving the work users explicitly request. - Usage reporting: Auto-review was incorrectly appearing as GPT‑5.4 usage, and failed or rate-limited requests were still shown as turns. Auto-review now appears as its own category, and only successful requests count toward the turn graphs. Rate-limited requests were never charged, but they were being displayed incorrectly. - Immediate relief: We reset usage limits while rolling out the fixes, then shipped hotfixes across the CLI, desktop app, and usage backend. - What to expect: New usage data should be clearer and actual consumption should be lower. Historical charts may still show auto-review under GPT‑5.4 because older turn data was not relabeled. Features that intentionally perform more work; such as /goal, subagents, and higher reasoning levels will still naturally use more capacity. All fixes are now deployed, and we've added more detailed monitoring so we can detect background-usage regressions sooner. We'll continue watching the results closely. Thank you for building and doing all sorts of things with Codex.

Tibo@thsottiaux

你觉得它有一个重置按钮吗?

引用 @OpenAIDevs

Your favorite Codex shortcuts are getting an upgrade. July 15th. https://t.co/xZ1ydZyt94

英文原文

Do you think it has a reset button?

Tibo@thsottiaux发卡预告

如果你恰好在之前几个小时内用掉了你上一次的重置,而额度还没用完,别担心,在我们结束调查后,你会获得更多手动重置。

回复 @thsottiaux

As we are still investigating, I have reset everyone's Codex usage limits. This is a hard reset given some users had stacked up to three banked resets already that they can apply on their own schedule. Funnily enough, this week at OpenAI is called the RESET week, which is meant for folks to relax a bit. However it will be a different kind of RESET week. Enjoy.

引用 @thsottiaux

Codex team is in a warroom on a Sunday combing through logs and checking whether there is anything that could lead to increased usage drains for some users. Taking it very seriously and won't rest until we get to the bottom of it.

英文原文

If you happened to have used your previous reset in the few hours before and didn't go through your usage, do not worry, you will get more manual resets after we conclude the investigation.

Tibo@thsottiaux

Codex 团队可能真的已经修复了一直困扰你的“模型容量已满”错误。https://t.co/EgS0HkOATY

英文原文

Codex team might have actually fixed the "model at capacity" errors that have been pestering you. https://t.co/EgS0HkOATY

Tibo@thsottiaux进展

我们今天为 dots 发布了一些不错的更新,banked reset 已经激活,应该很快就会到账到每个人的账户里!

引用 @ChatGPT

你的 dot 现在拥有…… ⚡️ 更快的回复 💬 更少的术语 🫡 更好的跟进执行 而且,它们现在可以遵循你的自定义指令。在对话线程里告诉你的 dot 诸如该如何表现、或哪些操作需要你批准之类的事情。 “always talk in lowercase.” “Show me a draft before sending any emails.” 你也可以在移动端的 Customize > Behavior 中设置自定义指令和规则,或通过网页端和桌面端 dot 的菜单进行设置。

英文原文

We shipped some good updates to dots today and the banked reset has been activated and should land in everyones accounts sometime soon!

Tibo@thsottiaux发卡预告

对我来说,周四很有 codex 的感觉。也许也是发放一张重置卡的好时机。

回复 @thsottiaux

It’s been a while without resets. Maybe I should come back out of the basement

英文原文

Thursday is feeling codexy to me. Perhaps also a good time for a banked reset.

Tibo@thsottiaux

@Tech_girl 我们把 Pro 套餐和 Business 100 的用量翻倍了。

回复 @Tech_girl

Has anyone else noticed that ever since Tibo stopped giving out resets, Codex usage limits seem to last longer? Or is it just me?

英文原文

@Tech_girl We doubled the usage on Pro plans and Business 100

Tibo@thsottiaux发卡预告

第 28 天/ 存起来的重置 2/2

英文原文

Day 28/ Banked 2/2

Tibo@thsottiaux发卡预告

已存入 1/2

英文原文

Banked 1/2

Tibo@thsottiaux发卡预告

第 26 天/ 你现在可以在移动端轻松切换多个账户,桌面端也即将支持。接下来两天会有重置……存起来的那种……随你怎么用 👀。 https://t.co/iQxsqbuk0f

英文原文

Day 26/ You can now easily switch between multiple accounts on mobile, and coming soon to desktop too. Next two days will be resets… banked… do with this what you may 👀. https://t.co/iQxsqbuk0f

Tibo@thsottiaux

@claudeai 最好宣布 28 天的重置

回复 @claudeai

We’re renaming our Max plans: Max 5x → Max Max 20x → Ultra Max is still $100/month, and Ultra is still $200. If you’re a subscriber, there’s nothing you need to do. We’re also removing the 5-hour limit for verified Ultra accounts, starting today with most existing subscribers. Newer accounts keep a temporary limit until they’re verified, which helps us prevent fraud and abuse. You'll get an email when it's removed. Weekly limits remain unchanged. View our plans here: https://t.co/niRpyGF5Me

英文原文

@claudeai Better announce 28 days of reset

时间是怎么推算的?来源与规则

有原话就按原话。原帖写了钟点、next hour、end of day 等时间时,按美国太平洋时区换算为北京时间,并保留有限的传播延迟。

Codex 只写日期时按历史常见的太平洋时间傍晚窗口估计;未写时间时才使用历史时段。

预计结束后六小时内显示待确认,之后显示应已生效,仍不代表官方确认。确认帖日期不代表精确到账时间。

重置卡与直接额度重置分开记录,发卡不代表额度已经恢复。

监控计划每 10 分钟检查公开帖子。是否已完成检查以监控状态为准;适用范围以原帖为准,个人额度请在产品内查看。

历史记录始于 2026-04-01
需要关注 · 最近检查 11/16 22:55AI News 整理 · 非 OpenAI 官方页面
上次尝试读取
11/16 22:55
上次读到帖子
11/16 14:14
上次完整检查
11/16 22:55