Changing a setting in a terminal tool usually means remembering where it lives, and then finding out whether it applies now or after a restart. Codex CLI 0.163.0 takes on that friction with a searchable /config. The same release lets you steer a response mid-flight, remap shortcuts around a leader key and run read-only lookups in parallel.
This update covers October 15, 2026, with a single release, 0.163.0, and 14 changelog entries. Below are the four main features and two smaller changes that matter if you manage configurations.
Find a preference in /config and know if it needs a restart
Search replaces browsing. Open /config and you can search preferences across categories. You no longer need to know which category holds a setting before you find it.
Most changes apply on the spot. Supported settings change immediately when you edit them in /config. The UI also shows which changes require a restart, so you find out before you wonder why nothing happened.
What it does not tell you. The changelog says supported settings change immediately, which implies some are not supported there. The entry gives no list, so expect to meet the boundary by trial. The restart markers are the part I would trust most, since they save you from guessing.
Changes for everyday work
Steer while Codex is still answering. Send a follow-up during a response and it steers the turn immediately. You no longer have to wait for the turn to finish or cancel it first. Interrupting a turn now also stops active Code Mode cells and their nested tool calls, so an interrupt reaches the work running underneath the response.
Set a leader key in /keymap. You can configure a leader key in /keymap, and the default is Ctrl+X. Shortcut hints stay open until you choose an option or cancel, so you do not have to race a disappearing prompt. Voice mute moves to F9. If you had muscle memory for the old voice mute binding, this is the one to relearn.
Read-only lookups run side by side. Codex can run independent read-only tools in parallel. The changelog names skill, memory and conversation-history lookups. Nothing in the entry promises a specific speedup, and the gain depends on how many independent lookups a given turn needs.
Technical notes
Background server restarts. You can restart a managed background server from /daemon. Codex warns you about work the restart could interrupt, then reconnects automatically. Read the warning before you confirm if you have long-running work in flight.
Shell executor. Codex now uses its standard shell executor and no longer bundles a patched zsh. Configurations that use the retired shell flags get a migration notice. The notice is your cue to update those configurations. Check any shared dotfiles or team templates that set shell options.
What to take away
If you work in the terminal:
- Try searching for a setting in
/configinstead of editing files by hand, and note which changes the UI flags as needing a restart. - Send a follow-up in the middle of a response and see how the steering feels for your usual tasks.
- Open
/keymap, look at the leader key (Ctrl+Xby default) and relearn voice mute onF9.
If you run parallel sessions:
- Interrupt a turn that has active Code Mode cells and confirm that the nested tool calls stop with it.
- Watch sessions that lean on skill, memory or conversation-history lookups, since those can now run in parallel when they are independent.
If you administer integrations and company deployments:
- Search your configurations for the retired shell flags. A migration notice means a setting needs updating.
- Confirm that nothing in your setup relies on the bundled patched
zsh, which is gone. - Before using
/daemonto restart a managed background server, read the warning about interruptible work. Codex reconnects automatically afterward.
Sources: the Codex CLI changelog, version 0.163.0 (October 15, 2026). No documentation pages were cited for these changes, so details beyond the changelog wording may differ in the current documentation.