Spike

NextJS. Full-stack developer. Swift 练习中

[Spike @zucchiniEvader]

@LinearUncle 刚充值了 500，正式版最好给我来个多模态

[Spike @zucchiniEvader]

@LinearUncle 那我暂时也不会给 codex 访问 superpower 了

[Spike @zucchiniEvader]

@LinearUncle 我也 out 了，这都啥呀，我咋都不会知道这种热梗

[Spike @zucchiniEvader]

在使用 macOS 27 Beta3 的时候总感觉 CPU 占用有些高，尤其是在我空闲使用期间。从监视器上看感觉是 chrome 的占用，但是我只开三两个页面，于是找到了 chrome 的设置里有个 CPU：The nominal performance tier，默认选择是ULTRA，我把它改成了MID，从监视器上看 CPU 的占用立时就下去了

[Spike @zucchiniEvader]

@LinearUncle 对呀我从20刀升级到100刀的时候重置次数都在，现在猛猛用

[Spike @zucchiniEvader]

已经收到了。早知道我昨晚不睡了

[Tibo @thsottiaux]

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.

[Spike @zucchiniEvader]

为什么我的周额度重置时间到了，还是不能用呢？非要等到5h重置额度到了才会重置？

[Spike @zucchiniEvader]

@suohawking 女朋友不如AI的，别想太多

[Spike @zucchiniEvader]

更新了macOS Golden Gate Beta2 感觉发热没Beta1严重了

[Spike @zucchiniEvader]

Kimi为什么这么慢啊，在token用完以前，我的耐心就先用完了。就一个小小的样式修改要研究很久呢

[Spike @zucchiniEvader]

@molezz @LinearUncle 嗯嗯，我说的就是omp搭配deepseek

[Spike @zucchiniEvader]

@LinearUncle 我只知道在下还没有相关产出🤡

[Spike @zucchiniEvader]

人挪死，树挪活（是我）

[Spike @zucchiniEvader]

我去真是不想再写ci/cd了

[Spike @zucchiniEvader]

@vereisyaps 我开了你的网页几分钟后电脑发热风扇狂转

[Spike @zucchiniEvader]

卧槽我开了docker（colima）忘了关了。dammit

[Spike @zucchiniEvader]

电脑烫的很，我不知道是什么原因导致的，我有几个猜想：
1. codex gui客户端
2. ghostty + omp（看到说ghostty比较费电，可能有关联）
3. 我在杭州

[Spike @zucchiniEvader]

电脑烫的很，我不知道是什么原因导致的，我有几个猜想：
1. codex gui客户端
2. ghostty + omp（看到说ghostty比较费电，可能有关联）
3. 我在杭州

[Spike @zucchiniEvader]

因为x的自动翻译，现在看推文都变得有意思了。各种语言都被翻译成了中文出现在timeline。