What version of Codex CLI is running?

codex-cli 0.115.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

Unknown (default model selected by Codex CLI)

What platform is your computer?

Linux 4.4.0-22621-Microsoft x86_64 x86_64

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

Windows Terminal 1.23.20211.0

What issue are you seeing?

There appears to be a regression between codex-cli 0.114.0 and 0.115.0 in WSL.

• 0.114.0 works
• 0.115.0 fails

After upgrading to 0.115.0, Codex can no longer run shell commands in my WSL environment. The failure happens before the target command runs and appears to come from the sandbox backend using bubblewrap.

What steps can reproduce the bug?

Environment:

• Windows host
• WSL1
• working directory under /mnt/c/...
• bubblewrap 0.6.1

From Codex, run:

git status --short

With codex-cli 0.114.0, this works.

With codex-cli 0.115.0, it fails with:

bwrap: Creating new namespace failed, likely because the kernel does not support user namespaces. bwrap must be installed setuid on such systems.

In a nearby version during rollback testing, I also saw:

bwrap: Unknown option --argv0

What is the expected behavior?

Codex should either:

• continue to run shell commands in this WSL environment, as 0.114.0 does, or
• detect that the current bubblewrap/namespace setup is unsupported and fall back gracefully

Additional information

These checks were run directly in the terminal, outside Codex:

$ ls -l "$(command -v bwrap)"
-rwxr-xr-x 1 root root 72160 Feb 26  2022 /bin/bwrap

bwrap is installed, but not setuid.

$ sysctl kernel.unprivileged_userns_clone
sysctl: cannot stat /proc/sys/kernel/unprivileged_userns_clone: No such file or directory
$ unshare -Ur true
unshare: unshare failed: Invalid argument
$ echo $?
1

So this environment does not support the namespace setup that the newer Codex version appears to require.

Notes

• git itself works normally in the terminal
• the issue is specific to shell execution through Codex
• repro date: 2026-03-28
• regression boundary:
  • 0.114.0: OK
  • 0.115.0: broken

I can test a workaround or provide more environment details if needed.