Codex attempts to modify route metrics and activate two saved NetworkManager connections before running normal commands.

Open 💬 1 comment Opened Mar 27, 2026 by arothmel

What version of Codex CLI is running?

codex-cli 0.42.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

GPT-5.4 Thinking

What platform is your computer?

Linux 6.18.7-100.fc42.x86_64 x86_64 unknown

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

GNOME Terminal 3.56.3 using VTE 0.80.4 +BIDI +GNUTLS +ICU +SYSTEMD

What issue are you seeing?

Before ordinary shell commands such as pwd and ls, Codex CLI invokes /usr/bin/nmcli. This causes NetworkManager-related errors to be printed, but the requested command still succeeds afterward.

What steps can reproduce the bug?

Even for simple commands like pwd, Codex prints NetworkManager errors first, then runs the requested command successfully.

What is the expected behavior?

Tracing the native Codex binary showed these exact invocations before the command ran:

  • nmcli connection modify <redacted-connection-1> ipv4.route-metric 100
  • nmcli connection modify <redacted-connection-2> ipv4.route-metric 400
  • nmcli connection reload
  • nmcli connection up <redacted-connection-1>
  • nmcli connection up <redacted-connection-2>

Additional information

Additional notes:

  • Reproduces with ordinary commands like pwd and ls
  • Reproduces even when the child shell is started with env -i ... bash --noprofile --norc
  • PROMPT_COMMAND was empty
  • This does not appear to be caused by shell init files
  • Reinstalling Codex did not resolve the issue
  • The npm launcher appears clean; the behaviour was observed from the native Codex binary it launches

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗