So, I was updating some of our local dev tooling yesterday,
and I- I noticed Codex CLI quiet- quietly pushed version 0.143.0
out.
And, uh, there's a pretty massive architectural shift in how they're handling
plugins now.
By default, it's now pulling remote plugins directly from the npm marketplace.
It just, you know, auto-resolves them.
Wait, wait, wait.
It pulls them by default?
Like, without an explicit opt-in first?
Because npm is...
I mean, we've all seen the typosquatting and dependency confusion attacks on there.
That sounds like a massive supply chain risk out of the box.
Yeah, it is.
They- they do show this really nice, clean, rich local versus remote versioning
comparison right in the terminal now, which is, uh, helpful for debugging.
But the underlying reality is that if you run a command that triggers a plugin you
don't have locally, it's gonna go fetch it.
Huge thanks to Jellypod, by the way, for helping us get this daily analysis out to
everyone.
But, yeah, if you're in an enterprise environment with strict compliance,
this default-on remote plugin behavior is probably going to trigger some security
alarms.
Oh, absolutely.
If I'm an IT auditor, I'm- I'm losing my mind over this.
You can't just have dev machines pulling arbitrary execution code from public
registries at runtime.
Is there an easy way to, like, lock this down?
Like a- a kill switch?
There is.
Actually, two ways.
If you're just running one-off commands and you want to be safe,
you can pass the --safe-mode flag.
That completely blocks any remote plugin resolution.
But if you want to set a permanent policy for your project,
you'll want to drop into your local .codex/config.toml file and set the
remote_plugins key to false.
Okay, so setting remote_plugins to false in .codex/config.toml is
basically the corporate compliance team's best friend here.
It's good they gave us the config file override, but I still- I still really don't
love that they made "on" the default.
It feels like they prioritized a seamless hobbyist experience over enterprise
safety.
It's a classic product tension, right?
Frictionless onboarding versus zero-trust security.
But at least the fix is a simple, single line in a config file.
Now, speaking of corporate environments, did they do anything to address the
nightmare of enterprise firewalls?
Because normally, when you lock down outbound traffic, these developer CLI tools
just break catastrophically.
Actually, yes, and this is a huge win.
Version 0.143.0 now natively respects system proxy settings on
both macOS and Windows.
And I'm not just talking about reading the standard HTTP_PROXY environment
variables.
It actually integrates with PAC-- proxy auto-config-- and WPAD,
the Web Proxy Auto-Discovery protocol.
Oh, wow.
PAC and WPAD support is actually a big deal.
Usually, you have to manually parse those files or feed the proxy IP directly into
the tool.
If it's routing Auth and Responses API traffic natively through the system proxy...
that- that genuinely saves a lot of setup headache.
Right.
It just works behind the firewall now.
And speaking of API traffic, they also expanded their LLM integrations.
Remember back in July when we talked about how they were bringing Bedrock into the
mix?
Well, this update officially adds first-class support for the new Amazon Bedrock
GPT-5.6 Sol, Terra, and Luna models.
Ah, the Sol, Terra, and Luna models.
And these actually expose the "max reasoning effort" controls,
right?
For those deep-thinking, multi-step planning tasks.
Exactly.
You can set the reasoning effort directly in your requests now,
so the model knows how much compute to burn on a complex planning path before
returning the response.
It's fully native in the Codex config now.
Perfect.
And I saw there were some terminal fixes too?
Because Windows users always seem to get the short end of the stick with interactive
CLI tools.
Yeah, they do.
But they finally fixed the ConPTY terminal input bug on Windows.
It used to drop characters or choke on certain key sequences during interactive
sessions, but that's resolved.
Plus, they added a new command: codex remote-control pair.
It lets you manually pair the background daemon if the auto-discovery fails.
Nice.
Sounds like a really solid utility release, even with the security caveat.
Well, that's our quick look at Codex CLI 0.143.0.
Good chatting, Ethan.
Yeah, catch you tomorrow, Maya.