cannot read files on my install

Resolved 💬 2 comments Opened Jun 8, 2025 by gbrault Closed Aug 7, 2025

What version of Codex is running?

0.1.2505172129

Which model were you using?

codex-mini-latest

What platform is your computer?

win32 | x64 | 10.0.26100

What steps can reproduce the bug?

codex was working well at start, but I got (node:11384) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. MaxListeners is 10. Use events.setMaxListeners() to increase limit

And when I asked to read back a file, it just told it was not able to access them

I have windows 11, I use codex undex vs-code powershell, I have docker desktop installed

I did the install with npm install -g @openai/codex

What is the expected behavior?

readeback files

What do you see instead?

can you read the scenario in documentation\persistence-08-06-2025.md

command

$ cat documentation/persistence-08-06-2025.md

command.stdout (code: 0, duration: 0.4s)

command

$ ls -la documentation

command.stdout (code: 0, duration: 0.4s)

command

$ pwd

command.stdout (code: 0, duration: 0.5s)

command

$ pwd; ls -la

command.stdout (code: 0, duration: 0.5s)

command

$ ls /

command.stdout (code: 0, duration: 0.4s)

command

$ ls -la /mnt/d/SeaDev/vapidpg

command.stdout (code: 0, duration: 0.5s)

command

$ find / -type f -name 'persistence-08-06-2025.md' 2>/dev/null

command.stdout (code: 143, duration: 120s)

command

$ ls /workspaces && ls /workspace && ls /mnt

command.stdout (code: 2, duration: 0.4s)

command

$ find / -maxdepth 4 -type d -name venv 2>/dev/null

command.stdout (code: 1, duration: 1.1s)

command

$ ls /d /c /host_mnt /mnt 2>/dev/null

command.stdout (code: 2, duration: 0.4s)

(node:11384) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. MaxListeners is 10. Use events.setMaxListeners() to increase limit

command

$ echo hello

command.stdout (code: 0, duration: 0.4s)

command

$ bash

command.stdout (code: 143, duration: 10s)

command

$ echo hello

command.stdout (code: 0, duration: 0.5s)

command

$ codex open documentation/persistence-08-06-2025.md

command.stdout (code: 127, duration: 1.1s)

codex
I tried to open documentation/persistence-08-06-2025.md, but I can’t seem to locate any contents under that path in the project. Could you please double‑check the filename and location (or paste the contents here) so I can read through the scenario?

user
this is a bug of your own, how can I report it?

command

$ rg -i contributing -n .

command.stdout (code: 127, duration: 0.6s)

command

$ codex --help

command.stdout (code: 127, duration: 0.7s)

codex
If you’ve run into what looks like a bug in the Codex CLI itself, the best way to get it fixed is to file an issue on the project’s GitHub repo. Here’s how:

Additional information

_No response_

View original on GitHub ↗

2 Comments

vahidreza · 1 year ago

same
codex -version
0.1.2504172351

Os
Mac Os 14.4.1 (23E224)

codex --full-auto -m gpt-4o

command

$ 'cat package.json'

command.stdout (code: 71, duration: 0s)

sandbox-exec: execvp() of 'cat package.json' failed: No such file or directory

codex
It seems I'm unable to access any files directly. Let's attempt a different approach by accessing the
src directory to observe existing component structures.

command

$ 'ls src'

command.stdout (code: 71, duration: 0s)

sandbox-exec: execvp() of 'ls src' failed: No such file or directory

codex
It appears I'm having consistent issues with accessing the file system. Let's reset and consider a
different approach.

codex-maintainers · 1 year ago

Thank you for the feedback. Please try using the latest version of Codex CLI, as we have made significant updates and improvements. If the issue persists, feel free to reach out again.