So, uh, thanks to Jellypod to help make this daily show a reality.
Yesterday we talked about those really messy CLI 0.142.5 regressions,
but if you upgraded your Codex CLI or Desktop to 0.142.5 this morning and
opened a remote SSH project...
man, you might have had a mini heart attack.
You open the sidebar and it's just...
empty.
"No chats" found.
Oh, no.
That is...
I mean, if you have weeks of context in those threads, that's a nightmare.
Are they actually gone, or is this another path-handling bug?
Thankfully, your thread history is perfectly safe.
It's not deleted.
What's happening under the hood is a pretty aggressive path-normalization change
they introduced in 0.142.5.
Basically, the client now resolves symlinks to their canonical,
absolute paths on the remote server.
So if you're on, say, a Lustre-backed absolute mount or any symlinked directory,
Codex grabs the fully resolved target path and saves the thread's cwd-the current
working directory-using *that* canonical path.
Ah, okay.
Let me see if I get this.
The thread itself gets tagged with the newly resolved absolute path,
like /mnt/lustre/user/project, but what is the sidebar actually looking
at?
Is it still pointing to the original symlink path you used to connect,
like ~/my-project?
Exactly.
The sidebar is still bound to the symlink path you initialized the workspace with.
Because of that exact path mismatch, Codex's UI filter fails to pair them up.
It splits your thread history into a silo, making it look like your conversations
just vanished into thin air, when they're actually just sitting there,
grouped under that newly resolved canonical path in the local database.
It's always the path-normalization bugs, isn't it?
Classic issue #30808 stuff.
So, if the data is still there, how do developers actually get their sidebars to
display those threads again without downgrading?
It's actually a pretty straightforward workaround once you know what's happening.
All you have to do is find the absolute resolved path on your remote server-you can
just run readlink -f on your project directory-and then add that exact canonical
path as a second saved remote project inside Codex.
Once the workspace root matches that resolved path, boom, all your old threads
populate right back into the sidebar.
Oh, that's a lifesaver.
So you don't have to manually edit any SQLite databases or local config files.
You just...
map the real path.
But speaking of regressions, I saw some really nasty reports from people on older
Intel Macs-specifically running macOS 26.3.2.
They were getting flat-out hard crashes, right?
Like a SIGTRAP?
Yeah, the SIGTRAP crash when invoking the built-in exec tool.
That one was tracked in issue #30706.
It turns out it's a V8 heap reservation failure on those specific x86_64
architectures running macOS 26.3.2.
If you're hitting that, the workaround is to hop off the stable release channel and
move to the 0.143.0 alpha branch, where they've backported a fix that relaxes those
memory constraints on initialization.
Huh.
Good to know they've got an alpha fix.
But what about the api side?
Because I've been seeing some weird chatter on Discord about OpenAI quota tracking.
People are complaining that their ChatGPT Plus quotas are just...
evaporating.
Like, jumping from seventy percent used to one hundred percent in under six minutes
without them running massive batch jobs.
Yes!
That is issue #30918, and it's a massive headache for anyone running automated
pipelines.
There's a regression in the prompt-caching logic that causes the client to send
redundant system prompt tokens on every single turn instead of utilizing the cache.
If you think you're getting hit by this, you can actually verify it locally.
Go into your project directory and inspect the local JSONL session logs.
Look at the prompt token usage metrics in those entries-if you see the token count
scaling linearly with every message instead of staying flat,
you're experiencing #30918.
Right, because it's re-sending the whole history every time.
Well, at least the JSONL logs don't lie.
That's a lot of useful debugging info for one morning.
Definitely.
Keep an eye on those paths and those logs.
Talk to you tomorrow, Maya.
Yep, talk then.