Codex 0.132.0 TUI hangs on Android Termux chroot / ZeroTermux, works only through tmux

Summary

Codex CLI 0.132.0 TUI hangs on Android Termux chroot / ZeroTermux when launched directly from the foreground terminal.

The process does not render the TUI and Ctrl+C does not terminate it reliably. The same environment works with Codex 0.128.0. Codex 0.132.0 also works if launched through tmux.

Environment

• Device: Android ARM64
• Terminal: ZeroTermux / Termux-like terminal
• Runtime: Ubuntu chroot
• Shell: bash
• Node: v20.19.4
• npm: 9.2.0
• Codex version affected: 0.132.0
• Codex version working: 0.128.0
• Platform package: @openai/codex-linux-arm64 / aarch64-unknown-linux-musl

Reproduction

Inside the Ubuntu chroot:

cd /oc
codex

Result: terminal hangs; no TUI is shown; Ctrl+C does not reliably exit.

These workarounds did not fix direct launch:

TERM=xterm-256color codex
codex --no-alt-screen
codex --no-alt-screen --disable terminal_resize_reflow
TERM=xterm-256color codex --no-alt-screen --disable terminal_resize_reflow

Workaround

Running the same 0.132.0 CLI through tmux works:

tmux -f /dev/null new-session -A -s codex-new '/usr/local/bin/codex-new'

Expected behavior

Codex 0.132.0 TUI should either launch normally in the foreground terminal or fail gracefully without leaving the terminal in a stuck/raw state.

Actual behavior

The TUI hangs immediately after launch in the foreground terminal. The process remains running and the terminal often needs stty sane or killing the Codex process from another session.

Notes

codex exec works normally on 0.132.0, so API/auth/model configuration is not the problem. This appears to be specific to the interactive TUI terminal handling. The binary contains tui/src/terminal_probe.rs, so this may be related to terminal probing/control sequences not being handled correctly by ZeroTermux/Android chroot foreground TTY.