Codex CLI 0.163.0, Explained: Daybreak On by Default, Instant Interrupts, /config Search

The 0.163 preview line closed into the stable release rust-v0.163.0 on 2026-10-15 (UTC). It is openai/codex's next stable release after 0.162.1 (10-09), and the follow-up to our Codex CLI 0.156–0.162, Explained: Voice by Default, GPT-6.1 Sol as Default Model, Worktrees and Command Center. The most notable thing about 0.163.0 is not any single feature but two flipped defaults: Daybreak goes from explicit opt-in to on by default for eligible accounts, and instant steering while Codex responds goes from opt-in to default. Both change what you get out of the box.

1. Release timeline and distribution status

The GitHub release rust-v0.163.0 was published at 2026-10-15T21:30 UTC (checked 2026-10-16). The last batch of prereleases visible on the preview line in this check: alpha.8 and alpha.9 (10-13), alpha.10 (10-13), alpha.10.1 (10-14), alpha.11 (10-14), and alpha.10.2 (10-15) — earlier alphas up to alpha.5 were existence-checked in our 2026-10-13 batch, and this article does not parse prerelease contents; the stable release notes are the sole source.

All three distribution channels kept pace the same day (checked 2026-10-16):

The release notes give the cumulative comparison range as rust-v0.162.0...rust-v0.163.0. Everything below comes from that release notes text.

2. The six new features at a glance

The next two sections expand the two default flips; the other four are in section 5.

3. Default flip one: Daybreak on for eligible accounts

The 0.163.0 release notes, verbatim: "Daybreak is enabled by default for eligible accounts. codex exec can also select it with an OpenAI API key when the server offers access." (#53701/#53717)

For contrast, the previous line: the 0.161 (10-07) release notes stated verbatim that Daybreak is opt-in — requiring --enable cli_daybreak or features.cli_daybreak=true, with daybreak=true alone insufficient, controls and indicators hidden by default, /daybreak unavailable, and automatic Cyber routing omitted (0.161 notes text, re-verified via the GitHub API on 2026-10-16). In other words, within eight days (2026-10-07 to 10-15), Daybreak's default state flipped from opt-in (established in 0.161) to enabled by default for eligible accounts (0.163.0).

Three things the official text leaves open, and we won't answer for: first, what makes an account eligible; second, whether the 0.161-era switches remain or changed meaning; third, the codex exec API-key path is premised on "when the server offers access," and what happens when it doesn't is not stated. If your automation depends on Daybreak behavior, verify against what the product actually shows after upgrading.

4. Default flip two: instant steering and interruption by default

The 0.163.0 release notes, verbatim: "Send a follow-up while Codex is responding to steer it immediately. Interrupting a turn also stops active Code Mode cells and their nested tool calls." (#51812/#51835)

The two PRs behind this feature are titled Enable instant interrupts by default and Enable code mode interruption by default — the mapping is explicit: instant_interrupt, introduced as an opt-in in 0.159 (letting new input steer Codex during a model response or a long-running Code Mode call, #48135), became the default in this release, and interruption now also cleans up Code Mode cells and their nested tool calls.

The practical difference in feel: on 0.156–0.162, input typed during a response did not steer by default (you had to opt in); from 0.163.0, it takes effect immediately. Scripts and CI setups that drove Codex and relied on the old queue-and-wait behavior during responses should be revisited.

5. The other four new features

• /config preference search (#52990/#53429): open /config to search preferences across categories, change supported settings immediately, and see which changes need a restart to take effect. For the full layering story of the config file, see Codex CLI config.toml: The Complete Guide to Models, Approvals, MCP and Layered Config.
• Leader key (#52273): configurable in /keymap, default Ctrl+X; shortcut hints stay open until you choose or cancel; voice mute moves to F9. If you remapped keys, watch for the hint placement change after upgrading.
• /daemon restart of the managed server (#53173): restart the managed background server from /daemon; Codex warns about work the restart could interrupt, then reconnects automatically.
• Parallel read-only tools (#52245): independent read-only tools run in parallel, with official examples of skill, memory, and conversation-history lookups. How parallelization interacts with permission approvals is not expanded in the release notes.

6. Security and networking fixes

• Permission restore on thread resume (#53150/#53419/#53424): resuming a saved thread restores its permissions and network approvals, while respecting explicit overrides and the current managed policy.
• Network proxy hardening (#51650/#52661/#53506): the proxy checks permission before a DNS lookup; rejects duplicate Host headers; prevents credential aliases from bypassing inspection hooks.
• /side conversations (#52184/#53436): after switching threads, /side returns to an existing side conversation; answers to pending prompts also go back to the thread that asked.
• Windows paste and WSL (#53224/#52967/#53453): Ctrl+V and Shift+Insert now paste text as well as images; repeated pastes on WSL reuse the clipboard reader; copy attempts time out instead of hanging.
• Command completion (#52652/#53331/#53622): local commands finish promptly when a child process keeps an output pipe open; remote commands preserve late-arriving output so the final poll can still collect it.
• codex exec output fix (#53444): no longer prints the same file diff again after an unrelated command.

7. Documentation and packaging changes

• GPT-6 family migration guidance updated (#51768): the bundled OpenAI Docs guidance was updated for migrations to the GPT-6 family, covering model-specific reasoning, tool use, and data residency considerations. For the family's API-side picture, see The GPT-6 family grows: gpt-6-sol, gpt-6-luna, gpt-6.1-sol land in the official SDKs.
• Linux sandbox docs clarified (#52610): explains how the Linux sandbox uses bubblewrap for filesystem isolation and seccomp for syscall filtering.
• No more bundled zsh (#52160/#52213): Codex now uses its standard shell executor and no longer bundles a patched zsh; configurations using the retired shell flags receive a migration notice.
• Smaller packages (#52178): Linux and macOS release packages strip symbols to shrink, while the original build outputs keep them.

8. Upgrade notes

New installs can take the latest tag from any channel (0.163.0, checked 2026-10-16). Coming from 0.156–0.162, walk through three default changes: Daybreak (on for eligible accounts), instant steering while responding (on by default), and the key placements — leader key (Ctrl+X) and voice mute (F9). For install and daily-use flow, see Getting started with OpenAI Codex CLI: from install to daily use.

9. Next steps

• The previous line, feature by feature (including the original 0.161 context for Daybreak's opt-in): Codex CLI 0.156–0.162, Explained: Voice by Default, GPT-6.1 Sol as Default Model, Worktrees and Command Center.
• Config layering and how Daybreak-style feature switches are written: Codex CLI config.toml: The Complete Guide to Models, Approvals, MCP and Layered Config.
• The GPT-6 family on the API and SDK side: The GPT-6 family grows: gpt-6-sol, gpt-6-luna, gpt-6.1-sol land in the official SDKs.
• The latest SDK-side news (Browser/Computer toolsets): Browser and Computer Toolsets (1/4) Land in the OpenAI SDKs: BrowserToolset Turns Driver Methods into Function Tools.