Codex CLI 0.160.0: Reconnect and Permission Fixes

Codex CLI 0.160.0 arrived October 1, 2026 with improvements to interrupted sessions, permission restoration and provider-supplied model lists. If you frequently reopen tasks, the useful upgrade question is whether your next action stays attached to the intended conversation and configuration. OpenAI’s changelog records the release.

Codex CLI 0.160.0: recovery before new work

After reconnecting, Codex resolves uncertain submissions before sending pending prompts. It retains server-supplied provider and output settings, and repairs resume/fork history.

For an interrupted coding task, our suggested first step is to inspect the recovered conversation before submitting the same request again. Look for the original instruction, its response, and any pending follow-up. If a file-writing instruction already ran, compare the resulting diff with the requested change. Sending it again simply because the connection banner disappeared is a poor recovery check.

Consider a task that updates a navigation label and then runs tests. After reconnecting, the useful questions are whether the label changed, whether the test command finished, and whether the follow-up remains unsent. These are separate observations. Ask for the missing step only after identifying it; do not assume that an absent final answer means every earlier action failed.

The 0.159.0 instant-interrupt release focused on steering active work. This release gives users a reason to check what happens when they return after a disruption. Keep the original task’s acceptance criteria when checking recovery.

Resume a specific session and inspect its boundaries

The official command reference documents several resume choices. Use codex resume to choose a saved session, or supply its session ID to target known work. The most-recent option is scoped to the current working directory unless you also request all directories:

codex resume --last
codex resume --last --all
codex resume SESSION_ID

When the current directory differs from the saved one, Codex asks which directory to use. The documented resume-directory setting can preserve a choice between the current and saved directory; an explicit directory override takes precedence. For work spread across several repositories, a session ID is a more deliberate choice than guessing which conversation a recent-session shortcut will select.

OpenAI’s CLI overview shows /status for current configuration and /permissions for permissions. Review both before continuing a task with meaningful filesystem effects. Write down the checkout, selected model, and permitted roots in an upgrade check; these observations make a later failure easier to localize.

Projectless tasks can use workspace defaults where policy permits. Resumed tasks recover their stored access settings. Check the intended directory independently. Our recommended check is a harmless read of the intended project, followed by a small reversible edit only after the displayed permissions and task scope agree.

Provider catalogs: check configuration, not model-name guesses

An explicit provider catalog now overrides incompatible bundled entries; failed refreshes no longer recycle obsolete listings. For a custom gateway, investigate the configured provider and its catalog before changing the model name. A familiar name in another client’s menu is not a substitute for checking your own route.

The advanced configuration guide explains named profile files layered over the base user configuration. A profile can set a model and a model-catalog path. Profiles can override the catalog file selected in the base configuration, so include the active profile in any catalog investigation.

Keep a short comparison: which profile was launched, which provider it selects, which catalog path it uses, and which model was requested. Compare a failing run against a previously working configuration without copying credentials into a bug report. If those inputs differ, resolve that difference before attributing the failure to the release.

The 0.159.2 Windows and Sol catalog report covers the preceding model additions and console-flash patch. Here, the useful comparison is between the catalog your provider supplies and the one the upgraded client actually presents.

Platform-specific checks and installation

Windows fixes cover PowerShell fallback, long-path access repairs and stray helper windows. Compatible local X11 terminals gain fullscreen selection and middle-button paste. Choose checks that match the operating system and terminal actually used by the team.

For Linux, try selecting a short transcript paragraph and pasting it with the middle mouse button into a harmless draft. Compare the copied text with the original before using it as review evidence. For Windows, repeat a known background-helper launch and a harmless sandboxed command, recording the terminal and whether an extra console appeared. These are suggested checks, not results from our own platform tests.

The changelog supplies this pinned npm installation command:

npm install -g @openai/codex@0.160.0
codex --version

The CLI documentation also covers standalone installation and other setup paths. Use the path appropriate to the existing installation; do not mix installation methods merely to get past a permission error.

A focused upgrade check for ongoing projects

Before upgrading, record the current task, checkout, and unfinished steps, and preserve any uncommitted work. After installation, confirm the executable version, reopen the intended session, inspect its configuration, and request a harmless status check. Then complete one bounded piece of the original task and run its relevant tests.

Use this checklist to distinguish installation, session recovery, provider selection, and command execution. A successful install establishes only the first. A recovered transcript helps establish the second. The selected provider and permissions still need inspection before the next action.

Codex CLI 0.160.0 is most relevant to people who resume long tasks, use custom providers, or depend on the affected terminal and Windows launch paths. Upgrade around a concrete workflow and keep its original scope: the release makes that workflow more reliable without requiring a new project structure or a different model.