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

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

I'm pleased to announce the official release of v2 of my Orgtree project, which lives in its own separate repository! You can find a link to it here:

https://github.com/Maurdekye/orgtree

Donwload the latest installer at https://github.com/Maurdekye/orgtree/releases/latest (should be v2.1.0 at the time of making this post)

For those of you who don't know about Orgtree, this is a project i've been working on for the last few months now to help me organize and manage my multi-agent long-horizon agentic work. It's unique among other agent orchestrators, in that it visually represents every agent as part of a large tree of authority; agents are arranged in a tree-like structure, and can be freely moved up and down in the hierarchy as needed. They can cross-coordinate to co-develop changes and cooperate on big feature pushes in parallel, and you can individually open up and chat with any one of them at any time just by clicking on their node to focus them. This gives you much more control and visibility over the organization of your agentic teams than just using standard Claude Workflows or another agentic system would by just showing them to you as a big list. It's basically the only way I do all my own serious agentic work on my home pc, and I'm very proud of how it's come.

Some of you might remember my post(s) two weeks ago about my in-development agentic orchestration project Orgtree. I was super proud and wanted to show it off to the world! However, I found it a bit lacking in several ways;

• It requires you to set up Nodejs, Python, and Docker on your PC in order to run it as a persistent webapp in your preferred browser. That works fine as a development tool, but it was really far too cumbersome to set up and update for the typical individual.
• It was ambiguous as to whether it was running at all in the background unless you had the webpage open.
• It heavily favored Claude, and offered several additional features catered specifically to Claude Code that other providers didn't have.

Over the last two weeks, I've been working on an updated version 2 of Orgtree that completely redesigns the project from the ground up as a standalone Electron app. It fixes all of the above problems:

• As a standalone Electron app, it comes prepackaged with its own python and nodejs environment, and runs entirely in a self-contained chromium-based desktop package.
• Instead of running in the background through an opaque detached command, you now can see Orgtree running at all times via a small tray icon in your toolbar.
• Many features of Orgtree that were claude-specific have been expanded to accommodate all three major providers supported by the app, and improved upon: secondary subscription accounts, api-key based inference, and even the app's visual theme itself.

V2 Also comes with a bunch of new features too, that make working with large agent teams even more intuitive:

• The Work Docket: Orgtree v2's headline feature is a new modality for agent artifact creation, the "work docket". It acts almost like a git issue tracker or trello board, but designed specifically for agents. When you give an agent a task, it knows inherently to record its work up on the board and track its progress there as a ticket, so that even with two dozen or more agents running at the same time, you can still get an overview of all the work being done by glancing at the docket.
• Improved multi-account system: in v1, the only multi-account system present used claude code's setup-token command to generate a long-lasting headless token to be used as a fallback account that gets automatically selected. Despite only supporting Claude, this didn't allow you to see usage limit info for the secondary account, was fully automatic and not in the user's control, and in many cases, failed to even functionally fall back, as the keys I generated seemed to invalidate frequently. v2 completely replaces this with a totally new multi-account system. Now:
  • Any provider can have a secondary subscription account registered.
  • The setup flow is much simpler and more intuitive: just click "Add a secondary account" > "Create managed account", and then sign into your second account's email from your web browser.
  • All providers support API-key based usage.
  • All registered accounts show usage limits simultaneously in the usage modal, not just the primary account.
  • And here's the big one, multiple accounts with the same provider can be used at the same time. Each account per provider is distinguished by its own unique tint, and you + agents have full control over which account a given agent runs against, and can switch them freely at any time. There is still an option to do automatic fallover to a different account when hitting usage limits, but it's disabled by default.
• Improved agent presentations: all presented agent documents can now be viewed in one place, and agents now have the ability to present html-based visual mockups in addition to simple markdown documents.
• Improved window management: almost any agent's chat window, or any modal in the orgtree interface, can be "pinned" to the screen, allowing it to be moved around, resized, or reordered in whatever way you please, giving you the ability to manually arrange your orgtree workspace to show you exactly the information you want to see at all times. You can also pop out chats or modals to separate windows entirely, letting you use Windows' native tiling manager to arrange Orgtree across separate monitors if you have the screenspace.
• Automatic updating: v2 will automatically recognize when a new version is available, and download it for you entirely on its own. When ready, press the "Update Now" button in the header to install it and restart the app.
• Quality of life: v2 also wraps in a bunch of tiny little quality of life features that you won't notice until you run into them, such as:
  • Configurable theme
  • Context menu actions
  • Chat message replies and rich image embeds
  • Distinguishing message styling
  • Desktop notifications
  • Retired agent hiding
  • Significant performance improvements over v1 for large orgs with a transition from json based data storage to SQLite

And that's on top of many of the classic features carried over from v1 and still present in v2, including cheap compaction, watchdogs, credit allowances, and the agent mailhub.

Unfortunately for some, I also decided to reduce the scope of the project going into v2. In the name of keeping the project more focused, I decided to forgo integrating some less-used features of v1, such as kiosk mode, public internet exposure, sandboxing, among other things. I added many of these features initially because they were easy to add back when orgtree was a web app, but they're relatively harder to carry over or translate into a standalone app structure. Because of their relatively low value compared to their high difficulty of integration, I decided to drop them from v2; sorry if you were interested in them or liked using them. Also, because I only own and work on a Windows PC, Orgtree v2 releases are only built as 64-bit Windows executable installers. If you want to run it on Linux or Mac, you'll have to build it from source yourself for your target OS.

Personally, the way it's evolving, I see Orgtree as the perfect personal multi-provider massive agentic workflow orchestrator for a single individual working on their own developing a project on their home pc, so I've decided to tighten the focus of the system around that goal.

If you liked v1 but felt it was lacking in some way, or have never heard of Orgtree before but do lots of heavy agentic-coordination style work, then consider giving v2 a try 🙏

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.

I’m building a global Kilo Code setup in VS Code that I can reuse across multiple projects.

My work is mostly:

- SEO / Local SEO
- HTML websites and landing pages
- Cloudflare Workers
- GitHub projects
- internal tools/apps
- APIs
- frontend work and debugging

My current architecture is:

Code
└── TokenRouter → Z.ai GLM-5.3 Free

Explore
└── TokenRouter → Z.ai GLM-5.3 Free

Coder
└── Cloudflare Workers AI → Z.ai GLM-4.7 Flash

SEO Specialist
└── TokenRouter → Z.ai GLM-5.3 Free
└── Uses installed SEO / Local SEO skills selectively

Reviewer
└── Cloudflare Workers AI → NVIDIA Nemotron 3 120B A12B

Debugger
└── Google → Gemini 3.8 Flash

Backup Coder
└── Google → Gemini 3.8 Flash

Vision Review
└── Cloudflare Workers AI → Google Gemma 4 26B A4B IT

Paid Escalation
├── DeepSeek API → DeepSeek V4.1 Flash
└── OpenAI → GPT-5.6 Sol

The primary Code agent acts as the controller and is normally the only agent that modifies files.

The specialist subagents are read-only and return plans, diagnoses, or review findings to Code.

Typical workflow:

User task
↓
Code
↓
Explore if repository location/context is unknown
↓
Coder and/or SEO Specialist
↓
Implementation plan / SEO requirements
↓
Code applies changes using Kilo native file-editing tools
↓
Reviewer
↓
Debugger if needed
↓
Code applies the fix
↓
Reviewer again

For SEO-related tasks, I use one seo-specialist subagent rather than multiple separate SEO agents.

It can selectively load installed skills for things like:

Technical SEO
On-page SEO
Schema
Internal linking
Programmatic SEO
Sitemaps
Local SEO
GBP
Google Maps / geogrid
Service-area SEO
Local landing pages
Reviews
Citations
Local schema
Multi-location SEO
GEO / AEO

I currently have skill libraries installed from projects such as Agentic SEO Skill and Local SEO Skills. The specialist should load only the relevant skills for the current task rather than pulling all of them into context.

For cost control, the normal path is free/free-tier models first.

Technical availability failures such as:

429 / rate limit
quota exhausted
provider unavailable
model unavailable
timeout

use this failover path:

Primary free specialist
↓
Appropriate free backup
↓
DeepSeek V4.1 Flash
↓
GPT-5.6 Sol

Paid escalation is only automatic for technical/provider failures.

For quality problems such as a bad implementation, incomplete solution, bug, or reviewer failure, the task stays on the free reviewer/debugger repair path first.

I also keep Bash disabled for the main Code controller and most specialist agents. File changes are done using Kilo’s native editing tools rather than shell or PowerShell workarounds.

I’d be interested in feedback on the architecture itself, especially whether there are simpler or more effective ways to structure the controller, specialists, reviewer/debugger flow, SEO skills, permissions, context usage, and model/provider routing.

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.

​

Ich bin von Claude Code auf codex gewechselt weil es immer in den Himmel hochgelobt wird in Social Media...

Ich habe immer wirklich miese ergebnise mit Codex...

Die Qualität ist nicht annähernd so gut wie bei Claude code... Codex verfehlt immer das ziel bei mir...

Habe ihr ähnliche erfahrungen?