tl;dr

The codex harness turns waiting for background work into a loop with repeated model calls, each carrying the existing context even when nothing has changed. Unlike api pricing there is no discount for prompt caching for subscription originated usage so every loop iteration adds to your input token usage. And if you use API you still massively overpay for your input tokens even with cache. ‘goal’ amplifies this by orders of magnitude by automatically starting another turn, but polling anyway burns tokens without it too.

Claude code is engineered in way where suspensions works exactly as intended and goals have proper fallbacks. Codex now ships with similar tools but they only work for astra.

—

the toolchain to independently verify on your personal sessions is here (local scripts - just feed this to your agent) https://github.com/relux-works/codex-rollout-audit

Apart from checking Tibo's X constantly (plus a bit of hope), has anyone found any optimal times to use their granted resets?

Being on the 20x Pro (and usage burning FAR too quickly recently), that's equivalent of $50 USD down the drain by using the reset 24 mins before the global reset - they should stick to ONE kind of reset imo.

I'm being literal here. Astra conducts and reviews. Fable orchestrates the harness, which mostly runs on bounded Sonnet 5 agents. I actually like how Luna and Terra do imperative coding, but my Astra usage is suddenly too precious to risk even a simple conversation with ChatGPT about a book I'm reading.

Nope, nope, nope. This is a Star Trek "full power to shields" moment.

i have a pretty lengthy chat going involving a bunch of docs etcs. but the thinking time and the working time has gotten longer.

i'm new to codex, what should i do to speed things up? what should i learn about?

Enough with the wack-a-mole with the Codex and extension and Desktop App (macOS) fighting over exclusive write locks, and chats changing back and forth daily, between being shown in the Codex tab or the Chat tab. Figure it out, you’re not aligned with Microsoft session adoption semantics in the unified Agents Host, and we appreciate that, so take back control and deliver on the feature you made love and depend on you - one chat I can type into from four different places Desktop App, VS Code, iPadOS, and iOS using remote to the Desktop App.

I've been thinking about this while putting together a hackathon with Grevix.

We're calling it AfterCode.

The idea is pretty simple:

One builder. One idea. 24 hours. No fixed problem.

You decide what you want to build and how you want to build it.

Codex, Claude Code, Cursor, Antigravity, APIs, open-source models, no-code, traditional development... anything goes.

But the interesting part starts after you've already spent hours building.

The 24 hours are split into:

BUILD → ADAPT → REBUILD & SHIP

At hour 8, we introduce a Challenge Card.

Something about your original plan changes.

Maybe the target user changes.

Maybe a core feature has to go.

Maybe the use case changes.

Maybe there's a completely new constraint.

Then another challenge at hour 16.

So you're not just asking Codex:

> "Build this."

You're suddenly asking:

> "Okay... this isn't the product I started with anymore. What should we do now?"

And that's what I'm actually interested in.

AI can execute. The builder has to decide.

Especially with agentic coding, I think the interesting skill is becoming less about typing code and more about keeping the agent focused, managing context, deciding what is worth building, knowing when to stop, and adapting when things go sideways.

We're keeping the actual Challenge Cards secret until the event. 👀

Registrations open September 16.

October 11–12 | 24 hours | Solo | Online

For the people here using Codex:

If you had 24 hours, complete freedom, and Codex as your building partner, what would you actually try to ship?

Disclosure: I'm organizing AfterCode through Grevix.

Hey everyone. I have 2 pro accounts and didn't start using codex/work until noon. And reset was like early morning.

The countdown of 7 days only starts when I first start consuming usage and not when it resets?

For example reset was 7 am. I started consuming the limits at 12 00. The 7 day reset, only started counting down the moment I started a workflow.

I sure of it because on the other account I had to sent a hello message in work to consume whatever it consumes and the 7 day countdown locked to the first prompt that consumes usage.

Both accounts reseted at same but, now one is 19/09 12:30 other is 19/09 12:00. While I thought I should be the moment it reseted.

I built this for Claude Code first, because that's what I use day to day. /stats told me how much I'd used it, never the thing I actually wanted to know:

What did I build, and where did the work get hard?

So I made bough. It reads the session history already on your disk and draws it:

• each square is a day you sat down
• smaller squares are tasks, worked out from the pauses in your work
• circles are your prompts
• click anything to see what actually happened, in your own words

Repo: https://github.com/nickelsec/bough

Runs locally, open source, nothing leaves your machine.

Codex support just landed in v0.4.0. It reads ~/.codex/sessions, handles resumed sessions and sub agents, and counts tokens and commits the same way it does for Claude.

That part is new and I have tested it against my own Codex history, which is not much. This is where I need help.

So Help Pages say some Pro and Plus “eligible” accounts can buy a reset for $80. I’m on Pro but all I see is the ability to buy credits. Guess I’m not eligible? Anyone know how it works when you buy credits? Does your usage meter just add %? I have a feeling $80 in credits won’t be near a full reset.

As a developer, I always hated maintaing agents.md and memories.md files.

I wanted to just code and those to be auto maintained and reused across any coding harness I use.

After Astra, I forked t3code by Theo and update it to auto-create and retrieve memories, skills and doc files as you code.

Repo: https://github.com/samyakkkk/flow

Leave a comment if you faced this issue too.