Long-running (idle?) codex sessions have bwrap failures

Resolved 💬 4 comments Opened Mar 16, 2026 by RadixSeven Closed Mar 17, 2026

What version of Codex CLI is running?

codex-cli 0.114.0

What subscription do you have?

Enterprise

Which model were you using?

gpt-5.4

What platform is your computer?

Linux 4.18.0-553.100.1.el8_10.x86_64 x86_64 x86_64

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

SecureCRT 9.3.2 (x64 build 2978)

What issue are you seeing?

I left the session and returned after more than 12 hours (I'm not sure how long it was), and bwrap started to give errors. The thread I uploaded is for a different set of errors because the error messages were no longer displayed after resuming, but the first time I experienced this, I recorded the errors elsewhere:

• Ran pwd
  └ bwrap: Can't bind mount /oldroot/ on /newroot/: Unable to apply mount flags: remount "/newroot/home/ ostapchu": Invalid argument
• Ran git status --short
  └ bwrap: Can't bind mount /oldroot/ on /newroot/: Unable to apply mount flags: remount "/newroot/home/ ostapchu": Invalid argument

I solve this by exiting and resuming, which makes it more of an annoyance. But I expect that if I had a task that ran for 24 hours, it would trigger this and the task would start to encounter spurious errors and confuse the LLM.

What steps can reproduce the bug?

  • Start a codex session using bwrap sandboxing
  • Run a simple prompt that runs a tool that accesses the filesystem (it should succeed)
  • Leave for 24 hours
  • Run another prompt that runs a tool that accesses the filesystem - it should fail

Uploaded thread: 019ce3b7-623a-7180-a4fd-de9a4f82f097

What is the expected behavior?

The second access to the filesystem should be OK.

Additional information

The working directory for this conversation (and everything I do) is outside my home directory and on a local drive. However, the home directory is NFS-mounted. Oddly, the error messages talk about attempting to mount another user's home directory. This problem has happened twice now, and it was a different user's directory each time. The server I work on is shared by several hundred developers.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗