›_ Codex Issues
Codex Issues / #7410

Codex plugin 0.4.44–0.4.46 regression: commands hang/timeout (even /bin/ls) while prior versions work

Resolved 💬 7 comments Opened Nov 30, 2025 by oliverbarlucchi Closed Mar 29, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

regression introduced in 0.4.44

What subscription do you have?

plus

Which model were you using?

codex-max

What platform is your computer?

Darwin 24.6.0 x86_64 i386

What issue are you seeing?

Issue summary

Running any command via Codex CLI/harness in /Users/oliverbarlucchi/Desktop/DEV/GitHub/gunsym times out with exit code 124 and no output (even /bin/ls, echo test).
The same commands run instantly in the user’s terminal; non-interactive shells work fine (env -i ZDOTDIR=/tmp /bin/zsh -f -c 'echo OK && ls' shows the repo listing).
The repo path exists and is local (not a network mount); ls -la and df -h are normal.
Changing workdir in the CLI/harness doesn’t help; restarting the session doesn’t help.
No aliases/wrappers on core commands (type ls → /bin/ls, type zsh → /bin/zsh).

What steps can reproduce the bug?

Repro steps

Start a Codex session with workdir /Users/oliverbarlucchi/Desktop/DEV/GitHub/gunsym.
Run /bin/ls or echo test.
Observe: command hangs and returns exit code 124 after ~20s with no stdout/stderr.

What is the expected behavior?

Expected

Simple commands return immediately with output.

Actual

All commands via harness time out; no output.

Additional information

macOS repo on local disk.
CLI configured with danger-full-access, network enabled, approval policy “never”.
Local shells (zsh/bash/sh) work; clean zsh with no init works.
Notes

Appears to be a harness/runner issue rather than shell config or filesystem.

older Codex plugin versions worked; the timeout bug starts in 0.4.44 and is still present in 0.4.46 (regression introduced in 0.4.44).

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 7 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #7084
  • #7353

Powered by Codex Action

dylan-hurd-oai contributor · 7 months ago

@oliverbarlucchi can you use /feedback on sessions for:

  1. A broken session
  2. A working session

For (2), using codex resume or a new version of the extension is fine, as long as you run /feedback before running new commands. Please include this github issue number, #7410, in your feedback submission.

vlasky · 7 months ago

@oliverbarlucchi You almost certainly have pyenv installed. The latest version 2.6.16 has a compatibility fix to work with codex's sandbox mode. Update it to the latest version using pyenv update. See the following issue for more information:

smith558 · 7 months ago
@oliverbarlucchi You almost certainly have pyenv installed. The latest version 2.6.16 has a compatibility fix to work with codex's sandbox mode. Update it to the latest version using pyenv update. See the following issue for more information: * Codex commands timeout issue #7353 (comment)

This was it for me! Thanks! :)

oliverbarlucchi · 7 months ago
@oliverbarlucchi can you use /feedback on sessions for: 1. A broken session 2. A working session For (2), using codex resume or a new version of the extension is fine, as long as you run /feedback before running new commands. Please include this github issue number, #7410, in your feedback submission.

@dylan-hurd-oai just did as instructed. thanks. here are the session references just in case

019b0fab-9a53-7b91-80cc-7e222ac2d57b broken session (didnt mention it was broken but referred to github issue number)
019b0f98-7173-71f2-8cd2-fdb62511f9ef working session

@vlasky unfortunately i do not have pyenv installed. i installed and uninstalled just in case too but this has not resolved the issue. thanks for the tip tho

oliverbarlucchi · 7 months ago

@dylan-hurd-oai i had codex debug and it sorta fixed it i think. i did /feedback in the session with the debug info and fix. (019b0fd4-8bc0-7e10-b041-f374a3e8e3bc)

etraut-openai contributor · 3 months ago

This bug report hasn't received any upvotes or additional posts in four months. Closing.