So I was, uh, looking through my local setups yesterday, and,
yeah, Jellypod is making this daily episode possible today,
shout out to them, but honestly, this new update in Codex CLI zero point one five
three point zero, it, it, it caught my eye immediately.
Let me guess.
Is it the Model Context Protocol stuff?
It is!
It totally is.
Because before this, right, if you authorized an MCP server,
say a custom database query tool or a cloud script, and you clicked remember
approval, that permission just lived globally on your machine.
Wait, so if you switched from your personal side project over to a client or team
account in the same CLI workspace...
It just carried over!
The remembered approval was global.
So if your model wanted to run a deployment script, it could execute that tool under
the wrong environment without asking you again.
That is classic cross account tool leakage.
Wow.
That is, uh, that is definitely a messy security surface.
So how does zero point one five three point zero handle it now?
Well, according to the release notes, remembered MCP tool approvals are scoped to
the selected app account.
It binds them directly to your active account ID and app link config.
So if I hop from my personal profile to my work profile, even if it is the exact
same MCP binary on my disk...
You have to re approve it.
Exactly once per connected account.
It will prompt you again because the active account ID changed.
That makes so much sense from a testing perspective.
I mean, back when I tested developer tools, permission leakage across profiles was
one of those subtle bugs that would bite you right when you least expected it.
But wait, what about relative paths on macOS?
Did they tweak that too?
Yeah, they did!
On macOS, if you were using relative executable paths for MCP servers,
starting them up could be pretty flaky.
In zero point one five three point zero, relative MCP executable paths start more
reliably on macOS now, so running codex mcp under multi tenant setups is much
smoother.
Okay, so relative binaries launch reliably, but you just have to give that explicit
approval one time when you switch accounts.
Right.
Exactly.
Okay, what else dropped in this release?
I saw something about rollout compression and session history?
Oh, yeah.
Under the hood, rollout compression now includes shared histories.
So all those saved transcript rollouts on disk get compressed,
which keeps your codex home directory size down.
Wait, if the rollouts are compressed on disk, does codex exec resume still work if
you select by directory?
Yep!
They specifically fixed that.
codex exec resume handles compressed rollouts when selecting by working directory,
so your background tasks and thread forks do not break even when disk compression is
active.
Nice.
And speaking of background tasks, there is a pretty noticeable change for Plus and
Team users on usage limits, right?
Oh, huge quality of life fix.
Previously, you might be deep in a long coding run and suddenly hit the wall.
Now, Plus and Team users get an earlier warning when less than half of their
allowance remains in an approximately five hour usage window.
Oh, I love that!
Getting warned at fifty percent left in a five hour window gives you actual time to
pause, review your agent's queue, or wrap up before you get cut off mid execution.
Exactly.
No more surprise rate limit brick walls while your subagent is halfway through a
massive refactor.
And what about configuration settings?
Any breaking changes or deprecations we should update in our config files?
Just a clean migration for TUI settings.
The old top level disable paste burst setting is officially moved under the TUI
block, so now it is tui point disable paste burst.
The old top level key still works as a fallback for now, but you should move it
over.
So, looking at the big picture here, Ethan, between account scoped approvals and
earlier quota warnings, it feels like OpenAI is really hardening Codex for serious
enterprise multi account workflows.
But do you think developers are going to complain about the extra approval prompts
when switching accounts?
Honestly?
Maybe a tiny bit of friction at first.
But when the alternative is accidentally running a production deployment tool using
your client credentials while thinking you are on a sandbox account...
I, I, I think re approving a tool once per account is a very small price to pay.
Yeah, I am with you on that.
Safety over silent leakage any day.
Well, that wraps up our quick look at Codex zero point one five three point zero.
Thanks for tuning in, everyone, and we will catch you next time!
Take care, everybody!