Bug: Codex macOS app ENOENT when viewing remote repo over SSH

Open 💬 5 comments Opened Apr 20, 2026 by nvemuri4649

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.417.40842 (1851)

What subscription do you have?

Pro

What platform is your computer?

macOS

What issue are you seeing?

Error: ENOENT: no such file or directory, stat '/home/nvemuri/projects/rl-experiments'

Context: Codex macOS app connected to a remote repo over SSH. Remote terminal/session is Linux

What happened: When viewing “All files” or the changed files view in Codex, it appears to resolve the remote Linux path locally in the macOS app, which fails with ENOENT.

Environment:

Codex app on macOS
Remote repo over SSH

What steps can reproduce the bug?

Steps:

Open the Codex macOS app
Connect to a remote machine over SSH
Open a repo at /home/[USER]/projects
Open the "All files" view and/or the changed files view
Observe the app fail with ENOENT for the remote path

What is the expected behavior?

Expected: All files and changed files views should work with SSH-connected repos by resolving paths on the remote machine, without trying to stat the remote workspace path locally on macOS.

Additional information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 4 months ago

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

#18186
#18547

Powered by Codex Action

Mahkhmood9 · 4 months ago

[quick fix]
why not use vscode, and then the remote ssh option from there?
https://code.visualstudio.com/docs/remote/ssh,

then insttall the vscode codex extention it will automatically load your extention

etraut-openai contributor · 4 months ago

@Mahkhmood9, please stop spamming our issue tracker. If you don't, I will report you to Github and ask them to ban your account.

kkosleeeep · 4 months ago

Having same problem. Using Codex App version 26.417.41555 (1858).

Some additional information:

My home directory is a link to the real mount point (like /home/xxx -> /mnt/disk/xxx)
I added the project in Codex via the symbolic link path (like /home/xxx/repo)
There is no upper case letter neither in the symbolic link path or the "real" path
While the remote machine is shared, there was no one else using Codex (the port 9234 is not occupied and can be listened by codex app-server) at that time.
Conversation was fine and Codex can respond to my questions/requests.

There were some other discoveries during debugging. My chat history just disappeared from the left side panel after a full turn completed. However, if I add the project via the real path (/mnt/disk/xxx/repo), I found that chat history can be held after a turn. Both two ways show the same ENOENT: no such file or directory, stat ....

I'm not sure whether these two problems are related. JFYI.

Mahkhmood9 · 4 months ago

Having same problem. Using Codex App version 26.417.41555 (1858). Some additional information: My home directory is a link to the real mount point (like /home/xxx -> /mnt/disk/xxx) I added the project in Codex via the symbolic link path (like /home/xxx/repo) There is no upper case letter neither in the symbolic link path or the "real" path While the remote machine is shared, there was no one else using Codex (the port 9234 is not occupied and can be listened by codex app-server) at that time. * Conversation was fine and Codex can respond to my questions/requests. There were some other discoveries during debugging. My chat history just disappeared from the left side panel after a full turn completed. However, if I add the project via the real path (/mnt/disk/xxx/repo), I found that chat history can be held after a turn. Both two ways show the same ENOENT: no such file or directory, stat .... I'm not sure whether these two problems are related. JFYI.

If you can replicate please use the /feedback option , the amazing openai team see those