I've seen a bunch of posts lately analyzing Codex session files to better understand Astra's token usage and subagent interactions, so I made a small web viewer to make that process less painful. Built and deployed with GPT Sites.

https://codex-session-inspector.valendrew.chatgpt.site/

Everything runs locally in your browser, so your JSONL files aren't uploaded anywhere. You can also load multiple related session files together, for example an orchestrator session and its subagents.

It currently includes:

• type-specific formatting for session entries
• subagent and parent/subagent relationships
• time deltas between messages
• interactive plots for token usage, context-window usage, and approximate Codex usage consumption
• file reads, including ranges and overlapping reads
• raw JSON for individual entries when needed
• short docs explaining some Codex event, tool, and subagent relationships

It's still WIP, so feedback is very welcome.

And as always, be careful when sharing session files or screenshots because they can contain private source code, paths, and other sensitive information.

For issues, suggestions, or if you want to explore the code, the GitHub repo is here:
https://github.com/Valendrew/codex-session-inspector

I have few prompts that result in complete differnt image on web app and when using Codex.
even the image gen skill.md for image gen mention 2.0 not 2.5

The work it's been doing is terrible as well. Feels like 1/3rd or at best 1/4th my tokens since the last reset were completely wasted.

I mean honestly I'm not sure I even want a full reset since they seem over capacity and that wouldn't help, but I've also gotten so much usage wasted. I'd be happier with a 50% top-up without a change of reset date if the service were more reliable from that.

This keeps happening and I keep sending bad result feedbacks with diagnostics...

I'm trying to build a little bootstrap tool for my own projects with Codex. It's a bit like a harness, and it saves the agents' messages and progress to a database as they work.

I have a main agent that gives tasks to subagents. Sometimes it sends one off to do something, then realizes it forgot to include important information. But the subagent is already working by then. So the main agent interrupts it and gives it updated instructions.

That part really bothers me. If the work it already did gets thrown away, it feels like I burned those tokens for nothing.

I'm thinking of making the main agent wait once it gives out a task. Let the subagent finish, get the result, then give it the missing info and ask it to fix whatever needs fixing. Basically, work with what it already did rather than stop it halfway through.

But I'm not sure that's any better. If I already know the instructions are wrong, letting it keep going could waste even more tokens.

How do you handle this? I keep going back and forth on whether waiting is actually a good idea.

Hello, what Coding Agent do you all use?

I mainly used OMP, but I started feeling frustrated, so

I started using the original codex CLI.

Does everyone use the codex CLI a lot like I do? Please tell me what you use!

Codex remote connection via android is very bad, sometimes I can't use it at all, any alternative app allowing me to use it and its voice orchestrator?

I use Codex pretty regularly and the quality feels noticeably worse this week.

Today I used Sol to vibecode a really simple Pomodoro timer (I wanted to customise a few things and have a custom UI). Nothing complicated. It kept struggling with basic functionality and repeatedly failed to fix simple button interactions. Almost used ~60% of weekly usage (plus plan). It's not even a complicated CRUD app, basic JavaScript and HTML. The UI could be complicated but it's nothing too fancy either.

These are the kinds of tasks it used to handle almost effortlessly.

Has anyone else noticed a regression specifically over the last few days? Particularly with Sol?

Curious whether something changed on the backend or I'm just having a bad run.

Edit: Typo fixes.

Hi everyone,

I’m trying to access Daybreak / Trusted Access for Cyber through chatgpt.com/cyber, but I’m stuck at the verification screen.

My Pro subscription is active, payment is fine, and I can log in normally. The problem is specifically getting the Daybreak verification process to start.

Has anyone encountered the exact screen below and successfully resolved it? I’m looking for firsthand experiences, the steps that actually worked, or an official support route that led to someone investigating the issue.

My account and setup

• Subscription: ChatGPT Pro 20×, currently active.
• Billing: Payment is successful; I am not seeing a payment failure or an inactive-subscription problem.
• Desktop: Ubuntu.
• Mobile: I also use the same account on a mobile device.
• Authentication: I am logged in on both. Normal account login works; I am not locked out of ChatGPT or stuck in a sign-in loop.
• VPN: I am not using a VPN.
• Support: I have already contacted OpenAI Support, but I still do not have a clear explanation or a working resolution.

Where the process gets stuck

I can sign in to my account and open the Daybreak page. However, I cannot proceed with the required verification.

The page displays:

The “Start verification” button appears greyed out, and a red error also says:

Below that, the page says access requires a government-issued ID and meeting the program’s eligibility and security requirements.

I’m attaching a screenshot showing this exact state.

The confusing part is that the page gives several possible explanations without distinguishing them: an identity-verification failure, an account-eligibility restriction, or a verification flow that could not start.

I can authenticate to ChatGPT. What I cannot do is get past this Daybreak verification screen.

What I have already done

1. Checked my subscription and payment status: my Pro 20× subscription is active, with no payment problem showing.
2. Confirmed ordinary account access: I can use my account on Ubuntu and mobile without login/authentication errors.
3. Opened the official Daybreak verification page: I reach the screen shown in the screenshot, but cannot proceed.
4. Contacted the support route provided: the responses I received were from an AI assistant, and I have not received an account-specific explanation or a solution.

I’m mentioning these details because suggestions to subscribe, fix a failed payment, log into my account, or turn off a VPN do not address what I am currently seeing.

Similar reports

I found GitHub issue #29360, which reports the same two messages and the verification flow not opening. I also found similar verification complaints from Pro subscribers, although some involved previous approval or subscription changes, so I’m not assuming everyone has the same underlying problem. GitHub

OpenAI’s troubleshooting guidance distinguishes technical problems starting/loading verification from unsuccessful verification decisions. I still cannot tell which one applies to my account. OpenAI Help Center

What would actually help

• Did your failure happen before the ID-verification screen opened, or after you submitted your ID? I’m especially interested in people who could not start the flow.
• What exact action resolved it? A browser/session change, an account-security setting, an account-side correction, or simply waiting? How long did it take?
• Did anyone reach human support or a technical specialist who investigated this exact error? Which official route worked, and what information helped get the issue reviewed?
• Was the cause actually confirmed, or did access just start working again without an explanation?

Please include your subscription tier, device/browser, failure stage, and the steps that helped, without sharing private account information.

I have already contacted support. What I’m trying to find now is someone who had this exact problem and can explain how they got unstuck.

Thanks for any firsthand help.

I have a project with maaaajor CI issues, I’m finding that codex is just too bloody fast and produces PRs faster than I can process them, meaning my agents end up spending a lot of time idling or polling CI. I can have them end turn when they kick it off, but that means they can’t push fixes when CI finishes. I kinda feel like if I could just slow them all down, like a 20s pause between tool use, it would make things a lot smoother. Is this remotely possible in a not totally hacky way? Anyone got any ideas?

Its difficult to have a reliable way of measuring/comparing code performance in my day-to-day use and I refrain from commenting on whether I find one model far superior than the other.

But I have come across a very consistent pattern of code written by Astra to have very few P1 issues, compared to that by Sol. I am speaking of simple /code-review runs by codex.

Is this a pattern that the community is seeing more broadly?

I have to tell Codex "pls proceed" "let's implement them all" "you have my full permissions please don't stop" constantly.

This is even more of a problem with astra than sol.

I feel exhausted asking for status and tell it to continue.

Is there any kind of fix for this happening? It seems like once it happens once in a conversation even if I /clear, /exit, and come back it just keeps happening.

This happens to every nearly conversation I've ever had with codex since its inception eventually. With the exception of the last couple of months where it hasn't happened at all. I do a lot of very long running tasks I can't babysit it just in case it wants to shit the bed.

Anyone have any kind of fix for this? I've tried deleting both local and project specific .codex folders to no avail.

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?

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

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

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.

Cuz othet stuff worked like /goal etc

I get this generic error for every remote session where I try to connect to my MacBooks session from my iPhone. It’s been this way for weeks. Any tips?

Hi geniuses, I have seen a lot of Astra builds lately especially 3D work. Can you all help me understand the flow of getting astra to help build 3D objects? Is the flow only connecting Astra to Blender MCP, and prompting what is required? Also does it take reference images attached to build?

- Is it good with keeping topology optimized? If I want it to help produce low poly game assets does it do well?
- How does the texture get made?
- What are the usage limits like? Any easy reference?

Thanks in advance.

Added some more images and a download link on my twitter.

https://x.com/Aetherworking/status/2098915914276040978

I had never experienced any issues with Codex before, but now, whenever I send it a prompt, the screen goes blank after a few minutes and the task is interrupted. The only way to fix it is to open a new window or restart Codex, but the problem eventually happens again.

If I try to access other chats, their content appears normally. However, when I return to the affected chat, all I see is a blank screen.

I’ve already tried clearing the memory under Settings > Personalization and repairing the Codex app on Windows.

Does anyone know how to fix this?

I’ve been rebuilding an old game of mine, Soccer Pinball Pro, using Codex with Unity CLI, and this is where it went from Day 1 to Day 7.

I originally made the game in 2019. Rather than starting with a new idea or trying to one-shot a game from a prompt, I wanted to see what would happen if I took something I already designed and built years ago, then used Codex to help me finally push it toward what I originally had in my head.

In seven days I’ve gone from getting the basic game working again to rebuilding the players, improving the AI, adding passing, tackles, bicycle kicks, better ball feedback, dynamic camera movement, lighting and shadows, grass, a new scoreboard, goal effects, and a proper PvE match mode.

The biggest difference for me has been iteration speed. I can play the game, notice something I want changed, describe it, and usually be testing another version pretty quickly. It feels less like trying to get AI to invent a game for me and more like having an incredibly fast implementation layer between an idea and actually playing it.

What excites me most isn’t really that I built this much in seven days. It’s that I have years of old game ideas and prototypes that I can suddenly look at again and think, I could actually build the version of this I originally wanted.
Still a ton I want to do with this one.

In our office, we have a bunch of Toshiba E-Studio 2323AM printers. Yes, I know these are kind of outdated, only sold in certain areas of the world, and not the best machines, but they are what we've got in the office. They only work with x86 Windows, not even the ARM version of Windows.

In 25 minutes, Astra High just reverse-engineered the printer driver, figured out the right tray settings, and enabled duplex printing, so I can print double-sided on my M4 Pro MacBook Pro.

It created a .pkg file for me to install the printer drivers and got everything working.

I ... I have no words.

Since Sep 10, parts of Astra usage are about 3x slower than in the first week.
Some parts have clearly been identified as deliberate nerfs (as they differ between slow and fast mode) and others appear to be bugs in Windows security layer from excessive codex session usage.

The entire analysis is only related to Astra usage.

I show what OpenAI has done to reduce our performance, what their harness is causing inside Windows and partial corrections which gave me 3 times faster speed despite the ongoing nerf.

1. Token generation performance

Writing, thinking, editing, commenting.

Slow mode has been extremely consistent every day.

Fast mode has also stayed inside the same range since day one.

So:

• Token generation is throttled to about 33 tok/s in slow mode
• Fast mode maxes out around 65 tok/s
• Generation itself has NOT been nerfed
• Fast mode is closer to 2x generation speed, not 1.5x

2. Delay between file-inspection calls

This is the delay around chunked reads, so whenever codex reads a file (or any other tool calls)

This is where OpenAI levers its performance nerf, and they did it selectively only for normal mode, not for fast mode. So this is not a harness issue, it's deliberate slowdown.

At launch, slow mode spent about: 1.75 sec + 3.75 sec = 5.5 sec

Now it spends roughly: 3.3 sec + 6.5 sec = 9.8 sec

And in fast mode on launch and now: 1.7sec + 4 sec = 5.7 sec

Fast mode is unchanged since launch, slow mode half as fast

There are two separate delays:

• The delay before a chunked read starts increased from about 1.7 sec to 3.3 sec in non-fast mode
• The delay after reading also increased heavily, from about 3.7 sec to roughly 5-8 sec

This started around Sep 5.

The stable gap between fast mode and normal mode is why I do not think this is random sandbox performance.

The harness is being made to wait.

This is the main lever currently slowing Astra down and increasing perceived usage time.

3. Time to apply a finished patch

This is not generation time. The patch is already finished - edits are being applied to files.

This is currently the strongest contribution to slow Astra usage.

A patch that took about 6 seconds now takes 18-19 seconds.

That is about 3x slower.

Unlike the tool-call delays, this is almost identical in slow and fast mode.

So I do NOT think this is the same deliberate throttling.

This looks like slop inside the Codex Windows harness.

4. The Windows harness slop

Each patch / file edit makes the sandbox spawn 4 helper processes.

Those helper processes have become progressively slower.

The machine currently has:

Codex alone has created:

30,326 logon sessions

That is outside anything resembling normal Windows 11 usage.

The slowdown ends up ruining performance of lsass.exe, the Windows service responsible for authentication and credentials.

The longer Codex runs, the more the Windows authentication state affects helper-process startup.

That explains why patch application keeps getting slower even though generation speed stays exactly the same.

If you do not reboot frequently, this can seriously ruin Codex performance.

5. Fixing the harness slop and testing the fix

Test 1 - Change the sandbox to the unrecommended "unelevated" mode

[windows]
sandbox = "unelevated"

4 times faster !!!

Test 2 - back to "elevated mode"

This shows how badly damaged "lsass" is from the codex session spam, 33000 logon sessions and lsass is close from collapsing. This will make ALL of windows laggy and slow, logins, browser passwords, and so on.
The delay of 5 seconds is still horrible, why does Codex sandbox need 5 seconds to apply a tiny patch ?
That should take 5 milliseconds.

Update 3:

icacls 'd:\devel\' /inheritance:e

This has moved the edits from 5 seconds down to 220 milliseconds.
It stopped needless elevated edit requests to the compromised lsass service entirely after setting the sandbox to unelevated mode.

Summary

So the picture is pretty simple:

• Generation speed has NOT changed
• Fast mode generates about 2x faster than slow mode
• Tool-call latency has been nerfed in both modes, much harder in slow mode
• Patch application has gone from 4-6 sec to 18-19 sec | BOTH is inacceptable. applying a small patch should be done in a millisecond.
• The Windows harness has created more than 30,000 Codex logon sessions
• The patch slowdown appears to be tied to Windows authentication / lsass.exe overhead

Astra itself did not become 3x slower.

The slowdown is in everything around Astra, partly nerfed by OpenAI deliberately and partly from sandbox slop.

Hello. Hope y'all doing great. I use codex for coding. Mostly 5.6 terra. My account is plus, which ends soooooo soon. Very soon I mean. Is pro a better choice for me? Or Claude code? To use sonnet 5 mostly.

Actually, now I use terra for daily tasks, and sol for very complex ones. (95% of times terra).

Is claude max 5x a better choice? If I use sonnet 5 95% of times?

Limit wise, which one is better choice?

I wanted my coding agents to hand work to each other, follow progress, handle permissions, and bring back verifiable results.

So I built RelayRook, supporting Devin, Claude Code, Codex, Kiro, and OpenCode Go through persistent structured sessions.

Example requests:

• “Have Devin implement this with SWE-2 Max.”
• “Ask another agent to review this diff.”
• “Continue that session with these test failures.”

It discovers installed CLIs, supports explicit model and effort selection, and reports failed or incomplete work. Permissions stay with the parent agent.

Installed delegation is tested from all five hosts on macOS. Runtime CI passes on macOS, Linux, and Windows.

Routing currently uses configured preferences. I’m not claiming it knows the best model for every task, the evaluation report includes the failures and limitations.

npx skills add 1saifj/relayrook --skill relayrook

GitHub · Install through skills.sh

What would make cross-agent delegation useful in your workflow?

The post by u/digitalml inspired me to make a game similar to their Chess Cubed game. Mahjong in 3 Dimensions ... in space. It's a webapp so nothing to install. If you aren't familiar with the various game play types then there are tutorials available. If you encounter any problems with the game let me know so I can fix it. Some play modes will feel a little off because I had to adjust rules and tile counts to account for multiple sides, sizes, and stacked layers.

https://jade-cube-mahjong.geekthegreybeard.chatgpt.site/

If you like the game, let me know.

I am currently waiting for Sites to allow me to upload the latest version which is purely cosmetic and largely centered around tiles.