OctoLink GEO

Codex 0.162.1 Fixes Multi-Line Questions and Startup Feature Checks

Author Editor

The 9 October 2026 patch stops a TUI crash on multi-line questions and checks features only for explicit command-line overrides.

Harness Engineering Codex TUI

Direct answer

Codex rust-v0.162.1, published 9 October 2026, fixes a TUI crash when an asynchronous question has several lines, and it stops startup failures caused by comparing a background server's feature settings with CLI defaults.

Codex rust-v0.162.1 was published on 9 October 2026 at 19:44:51Z by github-actions. The release is a bug-fix tag. The compare range printed on the page is rust-v0.162.0 through rust-v0.162.1. There are two fixes, and both sit on the boundary between the terminal interface and a process that is already running.

The first fix is a TUI crash when asynchronous questions contain multiple lines. The note says the fix preserves line breaks and complete hyperlink destinations, and it cites pull request 51866. A question that wraps is still one question. Dropping the line break, or cutting a link at the wrap, is a display failure, not a model failure. The page does not include a screenshot or a sample question. It names the crash and the two things the repaired renderer keeps.

Feature checks only for explicit overrides

The second fix is about startup. Differences between a running background server's feature settings and CLI defaults were failing startup. Compatibility checks now apply only to explicit command-line feature overrides. That item is pull request 52648. A default that the CLI would have chosen is no longer treated as a mismatch against a server that was started with a different default. An override the user actually passed is still checked. The release page does not list which feature flags were involved.

Source: Codex rust-v0.162.1.

FAQ

What happens to line breaks in those questions?
The notes say the fix preserves line breaks and complete hyperlink destinations.
Which feature checks still run at startup?
Compatibility checks now apply only to explicit command-line feature overrides.