Codex CLI 0.139.0 segfaults in interactive mode on Ubuntu 24.04 x86_64

What version of Codex CLI is running?

0.139.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.5

What platform is your computer?

Linux 6.17.0-35-generic x86_64 x86_64

What terminal emulator and version are you using (if applicable)?

Konsole 23.08.5. Also reproduced in xterm. No terminal multiplexer was in use: no tmux, screen, or zellij.

Codex doctor report

Redacted. Relevant facts: overallStatus=ok, codexVersion=0.139.0, mcp servers=0, model=gpt-5.5, runtime=npm linux-x86_64 native x86_64-unknown-linux-musl binary, websocket/network ok, sandbox readable.

What issue are you seeing?

Codex CLI repeatedly crashes with Segmentation fault (core dumped) in interactive TUI mode on an Ubuntu 24.04-based x86_64 system.

The crash happens during interactive tool use, especially while reading/searching files or when switching from review mode to making edits. It can also happen during narrow prompts that only inspect one file.

I could not reproduce the same crash on another Linux system.

I reproduced this with both installation methods:

standalone installer binary:
~/.codex/packages/standalone/releases/0.139.0-x86_64-unknown-linux-musl/bin/codex
npm package binary:
@openai/codex-linux-x64/vendor/x86_64-unknown-linux-musl/bin/codex

I also tested npm installations through Node 24 and Node 22. Both still crashed because they launch the bundled native x86_64-unknown-linux-musl Codex binary.

What steps can reproduce the bug?

From a Python project directory:

ulimit -c unlimited
cd ~/project

codex \
--disable apps \
--disable plugins \
--disable terminal_resize_reflow \
--disable unified_exec \
--disable shell_snapshot \
--no-alt-screen

Then ask an interactive code-review or code-fix prompt, for example:

are there any issues in this codebase?

or:

please fix the issues you found

Codex begins running tools, reading files, searching, or preparing edits, then crashes with:

Segmentation fault (core dumped)

I also reproduced the crash with a fresh CODEX_HOME containing only auth.json and a minimal config, with many features disabled:

apps=false
plugins=false
tui_app_server=false
terminal_resize_reflow=false
unified_exec=false
shell_snapshot=false
browser/computer-use/multi-agent/plugin-sharing features disabled

With that clean state, a narrow prompt like this still crashed:

Read the local instructions first. Fix only one identified issue in a Python source file. Make the smallest possible edit. Do not run git. Do not scan runtime folders.

The crash happened shortly after Codex searched/read the target file.

The crash still occurs after trying:

standalone install and npm install
Node 24 and Node 22
disabling apps/plugins
removing an installed curated plugin
disabling terminal_resize_reflow
disabling unified_exec
disabling shell_snapshot
disabling tui_app_server
disabling browser/computer-use/multi-agent related feature flags
--no-alt-screen
NO_COLOR=1 CLICOLOR=0 TERM=xterm-256color
outside conda / virtual environments
a clean copy of the project without runtime output directories or Python cache folders
multiple terminal emulators
--sandbox danger-full-access
a fresh CODEX_HOME

Earlier, one crash path involved:

Booting MCP server: codex_apps
Segmentation fault

Removing the plugin and disabling apps/plugins stopped that specific startup path, but the interactive TUI still segfaults during normal file read/search/edit sessions.

Latest coredump excerpt, with local paths anonymized:

Signal: 11 (SEGV)

Command Line:
<home>/.nvm/versions/node/v24.x.x/lib/node_modules/@openai/codex/node_modules/@openai/codex-linux-x64/vendor/x86_64-unknown-linux-musl/bin/codex --disable apps --disable plugins --disable terminal_resize_reflow --disable unified_exec --disable shell_snapshot --no-alt-screen

Executable:
<home>/.nvm/versions/node/v24.x.x/lib/node_modules/@openai/codex/node_modules/@openai/codex-linux-x64/vendor/x86_64-unknown-linux-musl/bin/codex

Stack trace:
#0 ... x86_64-unknown-linux-musl/bin/codex + 0xacd7ccd

ELF object binary architecture: AMD x86-64

Thread id: not provided.

What is the expected behavior?

Codex should either complete the interactive task or fail gracefully with a normal error message.

It should not terminate the native CLI process with SIGSEGV.

Additional information

codex doctor --json reports overallStatus: ok.

Older Codex CLI 0.110.0 was stable on this machine, but newer GPT-5.5-era builds I tried segfault in interactive mode.

I may have limited availability for follow-up, but I included the most relevant reproduction details I have.

This issue text was drafted with AI assistance, but the commands, environment details, and crash observations are from my own local testing.