linux system commands like List ls not working
Resolved 💬 4 comments Opened Oct 10, 2025 by znahas Closed Dec 2, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
codex-cli 0.46.0
Which model were you using?
gpt-5-codex
What platform is your computer?
Linux 6.11.0-29-generic x86_64 x86_64
What steps can reproduce the bug?
Fresh install either by npm or brew result in the same loading forever when doing /init on an empty folder (or non empty).
I am able to chat with it but when it comes to do any system commands like ls, it just gets stuck forever.
What is the expected behavior?
_No response_
What do you see instead?
_No response_
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I think this issue is out of date, so I'm going to close. If you're seeing this behavior with the latest version of the codex CLI, please use the
/feedbackslash command and submit a new bug report./feedback still seeing this with 0.63.0, running Ubuntu 24.04.3 LTS
This is what Codex is telling me:
• I'm noticing all shell commands, even simple ones like echo, are timing out after 10 seconds with exit code 124, which suggests they're hanging before
outputting anything. I suspect this might be due to the shell trying to run in a directory that's inaccessible or blocked, causing chdir to freeze. Even
setting the working directory explicitly to / hasn't fixed it, so maybe the environment or sandbox is restricting execution in a way that's not reported
clearly. Given these repeated timeouts, I think I should attempt running commands with escalated permissions to bypass potential sandbox restrictions and
help diagnose if it's a permissions or environment issue causing these hangs.
• Explored
└ List ls
• I confirmed sandboxed commands timed out, likely due to sandbox restrictions or bugs, while running with escalated permissions worked fast. I’ll report
the directory listing (including AGENTS.md) and note escalating was necessary to overcome sandbox hangs, then suggest next steps about continuing with
escalated commands.
─ Worked for 4m 42s ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
• Sandboxed cmds hung (timeout), likely sandbox/sandboxed FS issue.
Escalated ls in /home/pc/wip/apps/test2 succeeded: AGENTS.md, ...
If more work needed, may need escalated runs unless sandbox fixed.
@IceKickr, thanks. Please use the
/feedbackcommand in the CLI. It will upload your session, show you the thread ID, and give you a link to open a new bug report.