Nick

Technical Director. Engineer. Agent Builder. Automating everything, one step at a time. AI is the future! Codex is better than Claude, any day.

[Nick @nickcrow_]

@thsottiaux I’m a codex user ❤️ can I have my reset back

[Nick @nickcrow_]

"design me, using autodesk fusion, a 3d printable figure of the openai codex logo, anthropomorphized" @thsottiaux

[Nick @nickcrow_]

@thsottiaux Fix resets - my one expiring tomorrow is missing? Had 4 this morning now it’s 3

[Nick @nickcrow_]

@thsottiaux @thsottiaux seems like banked resets are broken, my reset expiring on the 12th is just missing

[Nick @nickcrow_]

@thsottiaux My usage limit reset that's supposed to expire on the 12th went away? Now I only have 3 remaining -- it's stil the 11th. Any idea what's up?

[Tibo @thsottiaux]

Introducing... another usage limit reset for all our ChatGPT Work and Codex users. Should land over next 30 minutes. Hope you have an awesome weekend.

Thank you for pushing our systems to the absolute limit, we have never seen traffic increase so quickly. Keep the feedback coming and we'll keep shipping.

[Tibo @thsottiaux]

Join us for a few unexpected things!

[OpenAI @OpenAI]

Today. 10am PT.

[Nick @nickcrow_]

@thsottiaux Excited

[OpenAI @OpenAI]

GPT-5.6 Sol, along with Terra and Luna, will launch publicly this Thursday.

We’re expanding preview access globally now.

[Nick @nickcrow_]

@thsottiaux When?

[Nick @nickcrow_]

@MatthewBerman @theo Actually doing this too! Fable planning and orchestrating, codex implementing except for the little pretty bits

[Nick @nickcrow_]

@theo What format of tasks do you give to fable?

[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.

[OpenAI @OpenAI]

Introducing a limited preview of GPT-5.6 Sol, our next generation frontier model, as well as GPT-5.6 Terra, a balanced model for efficient, everyday work, and GPT-5.6 Luna, a fast and affordable model for high-volume work.

https://t.co/OoM83SyISN

[Nick @nickcrow_]

@thsottiaux The puns, I know what this is lol

[Nick @nickcrow_]

@thsottiaux pretty sure there’s a usage bug, I should still have 10x limits and I just ate through 40% in an hour?

[Nick @nickcrow_]

Went back to an old codex chat (same model as a couple weeks ago, 5.5 xhigh) and got this:

Your input exceeds the context window of this model. Please adjust your input and try again. @thsottiaux any ideas?

[Nick @nickcrow_]

@sama lol

[Nick @nickcrow_]

@thsottiaux Did codex write this?

[Nick @nickcrow_]

@thsottiaux lol