Codex 0.163.0: Configure Settings Without Guesswork

Ethan Park

So Codex 0.163.0 is out of prerelease. Thanks to Jellypod for helping make this daily show a reality. Last time we were poking at the Program Status Protocol signals in alpha 11, while stable was still sitting on 0.162.1. As of October 15th, 0.163.0 is the stable release, and the 0.164.0 alpha 1 tag already showed up this morning. The headline feature in this one is the new interactive /config command.

Maya

The way I'd frame it is this. Until now, changing a setting meant opening config.toml, remembering the exact key name, saving, and then wondering whether the running session ever noticed. Now you type /config inside a session and it opens a preferences manager. According to the release notes, you can search preferences across categories, change supported settings immediately, and see which changes require a restart. Those are the three things that used to be guesswork. Pull requests 52990 and 53429 are the ones to look at.

Ethan Park

The phrase to hold onto is "supported settings." Not everything applies live. The release notes say the interface tells you which changes need a restart, so the first habit to build is reading that indicator instead of assuming. If a setting applies immediately, you flip it and keep working in the same thread. If it doesn't, you know before you waste ten minutes wondering why nothing changed.

Maya

And that's where the companion piece matters. 0.163.0 also adds a restart action under /daemon. It restarts a managed background server. The changelog says Codex warns you about work the restart could interrupt, and then reconnects automatically. So the workflow looks like this: open /config, search for the setting, change it. If it's flagged as needing a restart, run /daemon, read the warning, and confirm. You come back to the same session without relaunching the terminal UI.

Ethan Park

Let me make that concrete, because the warning is the important part. Say you've kicked off a long task and you decide you want a different configuration. Before this release, you might have killed a process from another shell and lost the thread of what was running. Now the restart flow tells you up front that in flight work could be interrupted. Our research notes also suggest that subagents or child processes spawned by tools would be aborted on restart. That detail isn't spelled out in the release notes, so test it before you rely on it. The safe move is to let active turns finish first, then restart.

Maya

Which brings us to caveats, and I want to separate what's confirmed from what's worth verifying. Confirmed: the release notes describe search, immediate changes, and restart indicators, plus the daemon restart warning. Our notes also say that enterprise managed configuration stays authoritative, so settings set by an administrator policy would show as locked, and that flags you pass at startup, like a model or a search flag, override file values for that session. Those make sense given how Codex has treated precedence before, but check them in your own setup. One more thing. The notes say changes get written to the active profile's config file. If you use named profiles, look at which file changed after your first edit.

Ethan Park

A practical test is cheap. Run /config, change one setting, then open your config file in another pane and see what landed where. If you keep your config in version control, that diff also tells you whether the tool wrote what you thought you set. And if you've been maintaining a pile of notes about which keys hot reload and which don't, this is the release where you can start deleting those notes and trusting the interface instead.

Maya

Now the smaller items, and a few of these will change your day more than you'd expect. First, steering. You can send a follow up while Codex is still responding, and it steers the turn immediately. Interrupting a turn now also stops active Code Mode cells and their nested tool calls. The changelog lists instant interrupts and Code Mode interruption as enabled by default, so you don't opt in.

Ethan Park

Second, the keymap. /keymap now lets you configure a leader key. The default is Ctrl+X, shortcut hints stay open until you choose or cancel, and voice mute moves to F9. If you had muscle memory or a terminal binding on Ctrl+X, check for a collision. Our notes say the F9 move was meant to avoid clashes with multiplexers like tmux, but that's an inference, not something the release notes state.

Maya

Third, performance. Codex can now run independent read only tools in parallel, including skill, memory, and conversation history lookups. That's the context gathering phase, so you'd mostly notice it at the start of a turn. Fourth, resuming a saved thread restores its permissions and network approvals, while still respecting explicit overrides and current managed policy. That means fewer repeated approval prompts when you pick up yesterday's work.

Ethan Park

On security, the network proxy got three fixes. It now checks hostname permission before a DNS lookup, it rejects duplicate Host headers, and it stops credential aliases from bypassing inspection hooks. If you run sandboxed sessions with a network allowlist, that's worth knowing is in the stable channel now.

Maya

Two housekeeping items. Codex no longer bundles a patched zsh and uses its standard shell executor instead. If your config still uses the retired shell flags, you'll get a migration notice, so read it rather than dismissing it. And on Windows, Ctrl+V and Shift+Insert now paste text as well as images, while WSL reuses the clipboard reader and copy attempts time out instead of hanging.

Ethan Park

So here's what to do today. Update to 0.163.0, open /config, search for one setting you normally edit by hand, and watch whether it says it needs a restart. If it does, use /daemon only when nothing important is running. Then check your config file to see which profile took the change. That's ten minutes, and you'll know exactly how this behaves on your machine.