Codex CLI 0.163.0 Guide: Steer Active Turns, Search Settings, and Verify Security

OpenAI released Codex CLI 0.163.0 as a stable build on October 15, 2026. This is more than a model refresh. It changes how you control a running agent, find settings, restart managed services, and resume saved work without losing the permission context that belonged to the thread.

The most visible addition is immediate steering: you can send a follow-up while Codex is still responding instead of waiting for the turn to finish. The release also introduces a searchable /config panel, configurable leader shortcuts, a managed-server restart flow, parallel read-only lookups, and security fixes around resumed permissions and the command network proxy.

What matters most

• Steer an active response with a follow-up message.
• Search settings in /config and see whether a change is live or needs a restart.
• Configure a leader key in /keymap and restart a managed server from /daemon.
• Resume a saved thread with its permissions and network approvals restored, subject to current policy and explicit overrides.

Before you upgrade

Start with a reversible repository state. Commit current work or create a separate branch, then check that git status shows only the changes you expect. Codex normally limits local work to the active workspace, but the effective boundary depends on the sandbox, approval policy, project trust, and any managed requirements applied by your organization.

• Identify the installer: standalone installer, npm, Homebrew, or a downloaded release binary.
• Create a checkpoint: save a commit or branch before testing the new behavior.
• Choose the narrowest useful permission mode: use read-only for inspection and workspace-write only when edits are required.
• Define network needs: know which destinations a command actually needs before enabling outbound access.

Codex CLI, the IDE extension, and the desktop app share concepts but do not always expose the same interface at the same time. If you are comparing terminal sessions with IDE-hosted agents, see the VS Code 1.140 Agent Host guide.

The six headline changes in 0.163.0

Change	What it changes	What to verify
/config search	Find preferences across categories and change supported settings in the UI.	Check whether the setting applies immediately or requires a restart.
Active-turn steering	Send a follow-up before the current response or task finishes.	An interrupt also stops active Code Mode cells and nested tool calls.
/keymap leader key	Configure the prefix used for shortcut sequences.	The default is Ctrl+X; voice mute moves to F9.
/daemon restart	Restart a managed background server and reconnect.	Read the warning about work that could be interrupted.
Parallel read-only tools	Overlap independent skill, memory, and conversation-history lookups.	This does not mean all writes and shell commands run in parallel.
Daybreak by default	Enabled by default for eligible accounts.	Availability still depends on account eligibility and server access.

The official Codex CLI 0.163.0 feature list. Source: OpenAI ChatGPT & Codex changelog, checked October 17, 2026.

Upgrade and verify the installation

1. Record the current version

codex --version

Keep the current version and installation method in your notes. If you previously mixed npm, Homebrew, and the standalone installer, your shell may continue to resolve an older executable after the upgrade.

2. Upgrade through the same channel

The official changelog gives this version-pinned npm command:

npm install -g @openai/codex@0.163.0

For the macOS and Linux standalone installer, the official quickstart uses the same command for installation and updates:

curl -fsSL https://chatgpt.com/codex/install.sh | sh

Windows users should follow the PowerShell route in the official repository, while Homebrew users should update the existing cask. Keep one primary installation route rather than overwriting multiple copies and guessing which one the shell launches.

The official quickstart separates installation, sign-in, and the first task. Source: OpenAI Codex CLI documentation, checked October 17, 2026.

3. Confirm the version and permission boundary

codex --version
codex

Confirm that the reported version is 0.163.0 or later, then start Codex inside a project directory. Use /status to inspect the active directory and session state. Open /permissions before the first real task and verify the sandbox, approval policy, writable roots, and network boundary.

A useful default is to begin an unfamiliar repository in read-only mode. Move to workspace-write only after you know which files should change. A broad permission preset is not a substitute for a clean branch and a reviewable diff.

How to use the new controls

Search /config before editing TOML by hand

Open /config and search by the setting name or the behavior you want to change. The new panel spans categories, applies supported toggles immediately, and marks settings that need a restart. A local preference cannot override a stricter managed requirement, so verify the effective state after changing it.

This is especially useful when a setting moved or was renamed. The configuration reference is still the source of truth for exact keys and scope, but the panel reduces the risk of pasting an outdated field into config.toml.

Steer an active turn instead of waiting

In 0.163.0, a follow-up sent during a response can steer the active turn immediately. Suppose Codex starts touching deployment files during a refactor. You can add, “Keep deployment configuration unchanged and limit edits to the component and its tests,” while the turn is still running.

Use an interrupt when the current activity should stop, not merely change direction. The release notes say interrupting a turn also stops active Code Mode cells and their nested tool calls. Steering does not automatically revert files that were already modified, so inspect git diff afterward.

Use /keymap and /daemon deliberately

The leader key begins a shortcut sequence. Its default is Ctrl+X, and the shortcut hints remain visible until you choose an action or cancel. Voice mute moves to F9 in this release. Learn a small set of high-value shortcuts instead of customizing everything on the first day.

The /daemon restart action is for a managed background server. Codex warns about work that could be interrupted, restarts the service, and reconnects. Save important output first. If the menu is missing, your current execution mode may not use a managed background server.

Why the security fixes matter

Saved threads now restore their own permissions and network approvals when resumed, while still respecting explicit overrides and current managed policy. The practical lesson is not to assume that yesterday’s session and today’s environment are identical. After codex resume, inspect /permissions before allowing the next command.

The network proxy now checks permission before performing a DNS lookup, rejects duplicate Host headers, and blocks credential aliases from bypassing inspection hooks. These changes close specific gaps, but they do not make arbitrary outbound access safe. In the default local workspace-write sandbox, command network access is off. If you enable it, prefer narrow destination rules and review access to loopback, private addresses, sockets, and credential-bearing services separately.

Also remember that the command proxy does not cover every capability. Web search, browser activity, apps, MCP connections, cloud tasks, and model authentication use separate controls or service connections. A domain rule for shell commands is not a universal policy for every tool Codex can reach.

Three practical workflows

1. Narrow a long refactor while it is running

Goal: keep a multi-file refactor from expanding into unrelated configuration. Ask Codex to show a plan and the likely files first. During the turn, send a follow-up that preserves the public API and limits edits to the target component and tests. Review the resulting file list, API changes, test commands, and any unverified behavior. Use git diff to identify work that happened before the steering message.

2. Build a repeatable team setup checklist

Goal: document settings without relying on memory. Search /config for the permission, UI, and keymap controls your team changes most often. Separate live changes from restart-required changes. Record where each setting appears, how to verify it, and whether managed policy can override it. The result should be a short operational checklist, not a copied configuration file that may be wrong for another machine.

3. Resume yesterday’s task without silently widening access

Goal: continue a saved thread while preserving a clear trust boundary. Select the thread with codex resume, then inspect /status and /permissions. For every requested network approval, check the destination and purpose. Decline access outside the workspace unless the task truly needs it. Review the final diff, commands, tests, and remaining unknowns together.

Troubleshooting in the right order

• The version did not change: reopen the terminal, run codex --version, and check whether multiple installation routes placed different binaries on your PATH.
• /config is missing: confirm that you are running stable 0.163.0 or later rather than an older build.
• A setting does not apply immediately: check whether the panel marks it as restart-required, save active work, and restart through the appropriate flow.
• /daemon has no restart option: the feature applies to managed background servers and may not exist in your current mode.
• Daybreak is unavailable: the release limits it to eligible accounts and server-provided access. Do not treat the default change as universal availability.
• A resumed thread has different permissions than expected: inspect current managed policy and explicit overrides; they can take precedence over saved state.
• Windows paste behaves inconsistently: 0.163.0 includes fixes for text and image paste shortcuts, WSL clipboard reuse, and copy timeouts, so verify the running version before changing terminal settings.

Minimum post-upgrade checklist

1. Confirm codex --version reports 0.163.0 or later.
2. Open /config, search a setting, and note whether it is live or restart-required.
3. Test the difference between a steering follow-up and a full interrupt on a low-risk task.
4. Open /keymap and verify the leader key and F9 voice mute change.
5. Resume a test thread and recheck /permissions and network approvals.
6. Validate actual code changes with a diff and targeted tests.

The central improvement in Codex CLI 0.163.0 is not greater autonomy by itself. It is tighter control while work is in progress: steer sooner, find settings without guessing, restart managed services with a warning, and preserve a thread’s security context when you return. Learn the controls in a small repository and a narrow permission mode before applying them to a large or sensitive codebase.

한국어 버전: Codex CLI 0.163.0 사용법을 한국어로 읽기

Official sources

• OpenAI ChatGPT & Codex changelog
• Codex CLI 0.163.0 GitHub release
• OpenAI Codex CLI documentation
• Sandboxing, approvals, and network access

Sources checked: October 17, 2026.