Codex CLI 0.153.0: Remote Plugins, Faster Guardian
We break down the latest Codex CLI release, including direct remote plugin marketplace management, enterprise source enforcement, and app server reconciliation for consistent tooling across projects. The episode also covers Guardian latency improvements, TUI cleanup options, and earlier usage warnings for Plus and Team accounts.
Chapter 1
Managing Remote Plugin Marketplaces Directly from the CLI
Ethan Park
Managing custom developer tools across a whole engineering org, um, it used to be a total nightmare of manual repo clones and local folder hacks. First off, a huge shoutout to Jellypod for making this daily show possible! Today we are looking at Codex CLI version zero point one five three point zero, which totally changes how we handle plugin marketplaces.
Maya
Yes! I, I mean, as a former software tester, state drift with plugins was basically the bane of my existence. You think everyone is running the same setup, and suddenly half the team is on a broken local fork.
Ethan Park
Exactly. So in zero point one five three point zero, the CLI adds direct remote marketplace commands. You can literally just run codex plugin list, codex plugin install, or codex plugin remove, and it queries remote registry endpoints directly.
Maya
Wait, so no more manually cloning plugin repos into your local codex folder or pointing to arbitrary file paths?
Ethan Park
None at all. It hits the remote marketplace endpoint, fetches the catalog, handles installation, and even formats remote sources with their version and auth policies in JSON output if you need to script it.
Maya
That is huge for automation. But, um, what about security? If anyone can just pull from a remote marketplace, doesn't that open up enterprise environments to unvetted third party code?
Ethan Park
That is where pull request four one nine five three comes in. They introduced a feature called enforce marketplace source policy for curated plugins. If your enterprise policy mandates curated sources, the CLI outright blocks installing non compliant or unverified remote plugins across team environments.
Maya
Oh, I love that. So admins get governance without locking down the CLI completely. And from the testing side, there is another piece in this release that caught my eye, pull request four one nine four nine, app server plugin reconciliation.
Ethan Park
How does that work when jumping around codebases?
Maya
So, imagine you are switching between git feature branches or totally different project trees. In the past, active plugin versions could get out of sync with what the project expected. Now, the app server constantly reconciles installed plugins against the active environment specs, so your tools stay consistent without restarting your session every time you context switch.
Chapter 2
Cutting Latency with Targeted Guardian Rules and TUI Housekeeping
Ethan Park
That level of predictability makes a huge difference. Speaking of making things smoother, let us talk about latency in zero point one five three point zero, specifically around Guardian safety reviews.
Maya
Guardian is great for safety, but yeah, running background checks on every single turn was definitely adding overhead and burning tokens.
Ethan Park
Right. So in this release, pull request four two one four seven changes how Guardian behaves depending on your approval mode. If you run in Full Access mode, Guardian now completely skips review for confirmation only actions.
Maya
Oh, wow! So if an action does not actually require explicit user approval anyway, it does not waste time scoring it?
Ethan Park
Exactly. And if you are in User Approval mode, it goes even further, it disables background Guardian scoring and prewarming entirely. You still get sensitive action checks and input prompts, but you drop all that background overhead, which cuts down turn latency and saves token consumption big time.
Maya
That is a massive speedup for daily terminal workflows. What about configuration updates in config dot toml?
Ethan Park
A couple of nice TUI housekeeping fixes there. Pull request four two one zero one lets you set tui dot auto recap equals false. That suppresses automatic recaps during idle turns, though you can still run slash recap manually whenever you want one.
Maya
Thank goodness. Sometimes you just want your transcript to stay clean without the agent summarizing things every time you pause to think. What happened to the old disable paste burst setting?
Ethan Park
That was moved under the tui table via pull request four one nine seven six. It is now tui dot disable paste burst, though the top level key still works as a fallback so your existing config won't break.
Maya
And I saw something about usage tracking for Plus and Team tier accounts?
Ethan Park
Yes! Zero point one five three point zero gives Plus and Team users an earlier warning when less than half of their rate allowance remains inside a five hour usage window. Instead of surprising you at ninety percent, it gives you a heads up right at the fifty percent mark so you can pace your work.
Maya
That is so practical. When you combine remote marketplace governance with leaner Guardian approval checks and earlier rate warnings, you get a much faster, far more predictable workflow. Really solid update overall.
Ethan Park
Absolutely. That is our quick take for today, thanks for listening and see you next time!