Inconsistent process name: npm installs show node instead of codex

What version of Codex is running?

0.39.0

Which model were you using?

Any

What platform is your computer?

Windows with WSL Ubuntu

What steps can reproduce the bug?

Run Codex CLI via the npm install.

What is the expected behavior?

In the Homebrew install of Codex, we see the correct process name as "codex".

What do you see instead?

When using the npm version, the process title is "node".

Additional information

When Codex is installed via npm, the running process appears as node in VS Code terminal tabs and process monitors (ps, htop, etc.). By contrast:

• Homebrew/release installs: already display as codex because the binary name is codex.
• Expected behavior: all install methods should consistently show codex.

This inconsistency makes it harder to identify Codex when running multiple processes side by side (for example, Claude, a local Node server, and Codex`), which slows down development velocity.

Proposed change

In the Node entrypoint (codex-cli/bin/codex.js), set the process title explicitly:

try { process.title = "codex"; } catch {}

Impact & rationale

Consistency: Aligns npm installs with native/brew installs, which already behave correctly.

Developer velocity: Easier to identify the Codex process in terminals and monitors when multiple Node processes are running.

Scope: Purely cosmetic; no functional behavior changes.

Precedent: Other Node CLIs (Claude) also set process.title for the same reason.

Request

This seems more like a consistency fix than a new feature, but I wanted to raise it here first to confirm whether maintainers consider this in-scope. If approved, I can prepare a minimal PR with the one-line change.