58% to 0% in Eight Seconds: Codex Users Say Their Weekly Allowance Vanished on the Same Night

说明与用途

至少三位 Codex 用户报告其每周额度在 10 月 16 日 UTC 当晚数秒或数分钟内归零。一位开发者记录显示 58% 在约八秒内变为 0%；另一位显示 77% 到 10% 在 38 秒内发生；第三位显示 48% 到 0% 在约九分钟内发生，随后被扣除了额外额度。此前五月的类似投诉促使一位 Codex 团队成员表示部分用户的使用限额不同步；未在十月的 GitHub 问题上找到公开的 OpenAI 回复。

问题

Codex weekly usage allowance collapsed within seconds or minutes on the evening of 16 October UTC, with no public OpenAI server-side reply.

结果

Three Codex users reported their weekly allowance collapsed within seconds or minutes on 16 October UTC; one developer logged 58% to 0% in roughly eight seconds, another 77% to 10% in 38 seconds, and a third 48% to 0% in about nine minutes with extra credits charged. A prior May complaint led a Codex team member to acknowledge usage limits were 'out of sync for some Codex users'; no public OpenAI reply was posted on the October issues.

工作流

• Developer opens GitHub issue on openai/codex repo reporting weekly allowance collapsed within seconds or minutes on 16 October UTC
• Developer submits local logs showing time-stamped percentage drop (e.g., 77% to 10% between 21:10:43 and 21:11:21 Moscow time, or 58% to 0% in roughly eight seconds)
• Developer requests server-side check from OpenAI
• OpenAI community forum member posts that usage limits were 'out of sync for some Codex users'
• No public OpenAI reply posted on the October issues

证据

Issue #54718: about 58% remaining became 0% 'in roughly eight seconds', the developer says, during overnight client work.

来源

Issue #54677: 77% to 10% between 21:10:43 and 21:11:21 Moscow time, with the weekly reset time unchanged, per the developer's local logs.

来源

Issue #54767: 48% to 0% in about nine minutes, then 295.8 credits charged, per the developer.

来源

Similar complaints in May led a Codex team member to post that usage limits were 'out of sync for some Codex users' (quoted on OpenAI's community forum). We found no public OpenAI reply on the October issues.