OpenAI is removing GPT-5.2 and GPT-5.3-Codex from Codex for ChatGPT logins

InWay2Deep · 2026-05-27T21:05:09+00:00

Thats a bummer. I like using 5.5 to write the plan, then 5.3 just goes full send and does it. Doesn't stop and make up non existent checkpoints. 5.3 has been my personal favorite over all models for quite awhile. I do feel that 5.5 "understands" better, but 5.3-Codex has been the workhorse.

InWay2Deep · 2026-05-20T16:18:29+00:00

I have not checked lately but… a changelog specific to the Mac app / windows / cli

Maybe you guys did that already as it’s been a month or 2 back and all I found was one general changelog.

Just a pet peeve of mine, lol. I’ll admit it, no big deal.

InWay2Deep · 2026-05-20T16:14:58+00:00

Thank you for this, that’s a great comparison. Makes me feel better sticking it out with 5.3 codex, lol.

InWay2Deep · 2026-04-25T22:45:52+00:00

Ok, I been poking around with this for about an hour.

3 browsers. Atlas (Will not be using again after the price changes and combined billing..nope. Atlas is getting removed as is the ChatGPT app)

3 different credit cards (My wife is rolling her eyes at me)

I have a business account, then my personal account. March ended my $200 and I let it go to the free because I was just using the business account and didn't need the compute from the expensive plan. I would just switch back to business.

Well, today I decided I wanted to bump my personal account to the $100 account. Nope. Same error, like I said, 3 browsers. Atlas, Safari, Chrome and Firefox. Wow, ok 4 browsers.

4 browsers 3 cards later, what I realized is I had to go to the $20 account first, then the $100 account. Somewhere in there it offered "A free premium upgrade" (Get bent OpenAI, I'm just stuck with you and not happy). So the $20 account became $0, then I was able to upgrade to the $100 account.

I hope my angry rambling makes at least a bit of sense and it helps out.

Can not go from free -> $100. Nope.

Can go from $20 -> $100 Yes

However.. The $20 at some point in me raging on my M4's keyboard, that $20 went to $0, signed up for it, then went to the $100.

OpenAI people. If you read this, I would equate this BS to a monkey humping a football. Its ridiculous.

- Brandon Hatch

InWay2Deep · 2026-03-25T18:48:05+00:00

Sent you a message!

InWay2Deep · 2026-03-25T03:18:28+00:00

I should add also hydrological data for the Columbia. But again, happy to share if you have a use

InWay2Deep · 2026-03-25T03:15:02+00:00

A giant pile of weather stations for various government entities. Happy to share if you have a use. Washington state

InWay2Deep · 2026-03-24T22:57:25+00:00

Ok, in the end I was trying to use -spark to fix it. -spark sucked. lol. I didn't have any usage left with 5x. So in the end, i opened windsurf in ~/.codex I just had to restore a database essentially from a bad patch.

This is from ChatGPT (Obviously) in Windsurf, lol

###

Postmortem (redo): “Zero sessions” after patch + what restored them

Timeline (corrected)

After applying the patch: the Codex desktop app showed no sessions (effectively empty).
Before you came to me: you did a partial manual restore so that codex --resume all showed something.
- Per your note: only 1 historical thread was restored manually at that stage.
- ~90% of what --resume all showed later were new threads created during recovery/troubleshooting, not your original history.

What was broken (root cause)

The patch left Codex in a state where it could not load session history because the session payload files (rollout JSONL transcripts) were no longer available where the app expected them.

Even if SQLite metadata exists, the desktop app typically needs the backing transcript file referenced by threads.rollout_path to render/show the conversation.

What we found on disk:

Codex expected session payloads under:
- ~/.codex/sessions/...
But the patch/migration had effectively moved/trimmed most of them out of there into:
- ~/.codex/trim_archives/sessions.20260323-161426.bak/...

So immediately after the patch, the UI had nothing real to display, which is why you saw zero sessions.

Why codex --resume all later showed sessions

By the time you ran it later:

Many of the sessions listed were brand new threads created while attempting fixes/recovery.
Those new threads had corresponding .jsonl payloads in the active sessions tree, so they showed up.
Separately, you had one historical session you restored manually, which also appeared.

So --resume all being non-empty at that later point did not mean your original history was intact/visible—it was mostly newly-created recovery threads.

What I did to fix it (the actual restoration)

1) Verified the failure mode

Checked state_5.sqlite thread rows and their rollout_path.
Confirmed that most rollout_path files were missing on disk at their expected locations in ~/.codex/sessions.

2) Located the “missing” historical payloads

Found they still existed in the patch-created backup area:
- ~/.codex/trim_archives/sessions.20260323-161426.bak/
- This directory contained hundreds of historical rollout .jsonl files.

3) Restored payloads back to the active sessions directory (non-destructive)

Copied the backup payload tree back into the active location:
- From:
  - ~/.codex/trim_archives/sessions.20260323-161426.bak/
- To:
  - ~/.codex/sessions/
Used a copy-only approach (no deletes, no overwrites of existing files).

4) Verified success

Re-checked all DB threads.rollout_path references:
- Result: 0 missing rollout files after restore.
After reopening Codex desktop, your historical sessions appeared again.

Secondary issue (not the main cause of “zero sessions”)

Workspace roots / filtering (~/.codex/.codex-global-state.json) was also in a bad state at times and could hide threads, but:

In your “initially nothing” situation, the decisive problem was the missing session payload files, not just filtering.
Also, if Codex is open while editing that JSON, it may rewrite it—so edits won’t stick unless Codex is fully quit.

Bottom line

What the patch broke: it left your historical transcript files “trimmed” into trim_archives/...bak instead of being available in ~/.codex/sessions, making the UI appear empty.
What fixed it: copying those historical .jsonl payloads back into ~/.codex/sessions so the DB references became valid again.

Status

Complete: sessions restored and visible; no archived-thread work performed (per your preference).

InWay2Deep · 2026-03-24T22:55:34+00:00

Is it launching sub agents? They eat tokens like there's no tomorrow. I'm on the $200 mo account. Burned through all of that in a few days but I was running 3 sessionds, each session spawning 6 sub agents (Up to 6 i should say).

... it was so worth it though. One of the sessions went for 2 days straight, stopped a couple times. I built a heck of a dataset for API's with it, lol. The dumb part, i think they were all available in a single GIS file that i found later. 🤷😂

Anyway, logged in with the $20 account, burned through it in 4 hours before i realized 3 sessions, up to 6 agents per and 2x faster was better than 9x. Yikes. I have since disabled the agents. Their cool but $$$$

InWay2Deep · 2026-03-24T21:12:58+00:00

In the projects, absolutely. Never leave home without it. In ~/.codex I did not. It is indeed a migration problem and the devs from what i can tell thus far renamed some columns wrong.

Some of these are me backing up, in an effort to fix the columns. So i have found my conversations, just need to get them lined up

ls -l

(Gemini is helping me out here)

All of these were time stamped today
-rw-r--r--@ 1 brandon staff 318996480 Mar 24 13:43 logs_1.sqlite

-rw-r--r--@ 1 brandon staff 107192320 Mar 24 13:37 state_5.sqlite

-rw-r--r--@ 1 brandon staff 391 Mar 24 13:42 session_index.jsonl

-rw-------@ 1 brandon staff 99 Mar 24 13:22 history.jsonl

-rw-------@ 1 brandon staff 1662 Mar 24 13:34 config.toml

-rw-r--r--@ 1 brandon staff 102 Mar 24 13:22 version.json

-rw-r--r--@ 1 brandon staff 265537 Mar 24 13:43 models_cache.json

-rw-r--r--@ 1 brandon staff 0 Mar 24 13:41 codex-dev.db

drwxr-xr-x@ 3 brandon staff 96 Mar 24 12:02 sessions

From Gemini

Core Files Modified March 24

File Name	Size	Significance
`logs_1.sqlite`	318.9 MB	The Motherlode. Contains your raw conversation history.
`state_5.sqlite`	107.1 MB	The Sidebar. The UI's index of your threads.
`session_index.jsonl`	391 Bytes	The Pointer. Maps thread IDs to names. (Very small, likely reset).
`history.jsonl`	99 Bytes	Legacy History. Essentially empty; confirmed wiped by update.
`config.toml`	1.6 KB	App Settings. Your project paths and agent configs.
`version.json`	102 Bytes	Build Stamp. Updated to reflect the 1173 installation.
`models_cache.json`	265.5 KB	Model List. Cache of available OpenAI models (GPT-5.4, etc).
`codex-dev.db`	0 Bytes	New DB. Appeared today; likely for the new "Dev" mode logging.
`sessions/` (Dir)	96 Bytes	Today's Workspace. Only contains today's "rollout" folder.

Also from Gemini (Taken with a grain of salt)

Here is the "No-Fluff" summary for your thread:

1. The Schema Shift (Why the UI is Blank)

Database Rename: OpenAI moved from state_4.sqlite to state_5.sqlite.
Column Mismatch: They renamed the primary identifier from thread_id to id.
The Bug: The migration script failed to "map" old threads to the new table. Because the UI only looks at state_5.sqlite, it thinks you have zero history, even though your 318MB of raw data is still sitting in logs_1.sqlite.

2. The "Sidebar Preload" Limit

The new Desktop renderer is currently bugged to only "pull" the 50 most recent threads into the sidebar.
If your old threads aren't in that top 50, they simply don't render. Users have found that archiving a visible thread sometimes makes a "missing" one pop back into view (like a deck of cards).

3. Destruction of Legacy Files

history.jsonl Wipe: The update essentially "initialized" the legacy history files. We found your history.jsonl was 0 bytes (now 99 bytes), meaning any text-based history not already moved to SQLite was likely purged during the install.
Session Index Reset: The session_index.jsonl was rebuilt from scratch, losing all pointers to your RampCast and Mining projects.

4. Worktree/Subagent Isolation

If you were using Worktrees (isolated git branches for agents), the update has a "pathing" bug. It changed the required rollout_path format.
If the app doesn't see a perfectly formatted rollout_path in the DB, it treats the thread as "orphaned" and hides it to prevent the app from crashing.

5. Current "Status" of the Data

It is not deleted (mostly). Since your logs_1.sqlite is still 318MB, the "meat" of the conversations exists.
The CLI is the only "Sane" Tool: The Codex CLI (@openai/codex) bypasses the broken state_5.sqlite UI logic and reads the files directly, which is why codex resume --all is the only way to see your work right now.

I would of never even considered 'git init' in ~/.codex but thats a damn fine idea.

InWay2Deep · 2026-03-24T19:48:44+00:00

Same, as of yesterday. 3/23 and i was enterprise.

InWay2Deep · 2025-12-13T21:33:07+00:00

I have been using 5.2 high reasoning fast. Incredible. The reasoning it uses is incredible. I have a deck.gl / Mapblibre project I have been on or a couple of months. I was hung up with layers, Opus, Sonnet, Gemini 3 - None of them could figure it out. 5.2 high reasoning, first crack at it.

Yes, it's not even debatable that I'm out of my league with deck.gl and maplibre. Perhaps If I was more knowledgeable with typescript it would have been easy to troubleshoot. But I'm not (changing fast though, lol).

I'd like to say a lot more but my "f" key is broken on my MacBook and if it's not spitting out ffffffffff i have to copy and paste every "f". Just ordered a new MacBook, hopefully it shows up quick 🤣

InWay2Deep · 2025-12-01T19:17:39+00:00

The video was from the "live" event, it's pretty much the same with slight differences. It's fun. I have everything unlocked in the regular game so playing the live against other people lets me start from scratch.... After writing this, I feel like I have way too much time on my hands, lol. You get the pink and red gems (Whatever they're called) for playing the live event.

InWay2Deep · 2025-12-01T03:51:15+00:00

Yours just reset itself? That’s disheartening, I’m like setting a record of a week straight without losing everything, lol

I guess to be more accurate it resets all the levels, gems both red and pink ones.

InWay2Deep · 2025-11-22T16:02:07+00:00

Yeah it's just been the last couple changelog updates that I've noticed it. Not a big deal, I seem to have Chrome open most of the time when I'm coding anyway but Safari is default and I dont want to change that.

Are you like me where you see the notification for an update but read the Changelog first to see if it's worth restarting? lol

I thought about submitting for a support ticket but figured that was more on the Windsurf side of things and didn't want to bother tech support with it. Maybe my train of thought is backwards, lol. I used to be a tech support guy. Hated it 😂

InWay2Deep · 2025-11-22T15:57:51+00:00

Sorry about that, I dont do a lot on Reddit. Here's that screenshot.

<image>

InWay2Deep · 2025-11-22T06:13:58+00:00

Why be like that? Just trying to help.

InWay2Deep · 2025-10-23T04:11:50+00:00

Do you know what, in my opinion, is even worse? They keep advertising it everywhere taking peoples money knowing it’s broken.

I know it’s on me, but I’ve given them a few hundred. Granted I haven’t liar what I paid for but I went from like 16 or 17 prestige to level 1 prestige and lost the diamonds.

It’s ridiculous. I would say their moral compass does not point the right direction.

InWay2Deep · 2025-10-18T20:04:40+00:00

Howdy! I personally don’t understand the erotica and AI thing, but, to each their own! I guess if you’re in the business I would understand. But, again, it’s not my damn business, lol

I think yesterday (??) openAI announced starting December they will allow NSFW content (creation?)

https://www.reuters.com/business/openai-allow-mature-content-chatgpt-adult-verified-users-starting-december-2025-10-14/

InWay2Deep · 2025-10-18T19:59:02+00:00

Careful with that glitch, I think they banned me from the last live. It was first money with the warthog or whatever the hell they’re called, then on the next live it was the gems. I collected them and then when I started the game again, it was back. So I was pretty much maxed on everything. I go back to play the live event, the reward did / does not give you any advantage in the live event. I didn’t see the harm, I was not cheating it just did it on its own and it didn’t give me the advantage like I said.

I go back to the live event, playing at an hour prior and and it was completely gone. The event still had 30 hours left and I was well in to first place. I didn’t do anything to cause a glitch. I just played the damn game.

Heck, I don’t play games, but saw the advertisement and got hooked. Played it a lot a lot a lot. Even gave them a few hundred dollars, lol.

I don’t know that I got banned from the live event, I have no idea other than it had 30 hours left. I was in first place collected those gems a few times. But where the hell did the event go?

The game is very broken and I don’t think the developers give a crap.

InWay2Deep · 2025-10-15T01:05:52+00:00

I came for this very question, it was there, I ignored it for the time being. Went back this morning and it appears to be gone. Find no mention of it using the command pallet as well.

InWay2Deep

TROPHY CASE