codex remote-control hangs silently and does not open a listening port

What happened

Running codex remote-control appears to hang during startup. The process stays alive, but it prints nothing to stdout/stderr and does not appear to open any listening TCP port.

Reproduction

codex remote-control

Also checked:

timeout 10s codex remote-control
echo $?
# 124

codex remote-control --help works normally.

Observed behavior

After 30 seconds:

• the process is still alive: node .../codex remote-control
• stdout is empty
• stderr is empty
• ss -ltnp shows no listening TCP port for the process

Expected behavior

Either:

• the remote-control app-server starts and prints/listens on a usable URL/port, or
• startup fails with an actionable error message.

Environment

• Codex CLI: codex-cli 0.130.0
• Package: @openai/codex@0.130.0
• Node: v24.15.0
• npm: 11.12.1
• OS: Ubuntu 26.04 LTS
• Kernel: Linux 7.0.0-15-generic x86_64

Related issues checked

I found related Remote Control reports such as #22851, #22715, #22733, and #22696, but this appears different:

• this reproduces on Linux with the CLI command itself: codex remote-control
• it does not print the usual JSON status/bootstrapped output
• after 30 seconds there is no stdout/stderr and no listening TCP port
• codex remote-control --help works normally

Redaction check

This report intentionally omits usernames, hostnames, absolute home paths, raw logs, and private identifiers.