Remote SSH connection falsely reports No `codex` found in PATH when `codex` is installed at a custom path
Resolved 💬 3 comments Opened Apr 23, 2026 by yiteng-guo Closed Aug 26, 2026
💡 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)?
26.422.20832
What subscription do you have?
api
What platform is your computer?
_No response_
What issue are you seeing?
Remote connection to SSH host fails with:
No `codex` found in PATH. Please install Codex on the remote machine.
But codex is installed at /home/$USER/bin and that path is added to $PATH in .zshrc. I believe this is a regression in the latest codex app since it worked in the previous version.
To work around it, you need to add /home/$USER/bin to ~/.profile such as
export PATH="$HOME/bin:$PATH"
What steps can reproduce the bug?
- Install
codexat/home/$USER/binand add/home/$USER/binto$PATHin.zshrc - Open up codex app and try connecting to the remote host. You will get an error.
What is the expected behavior?
_No response_
Additional information
_No response_
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Facing the same issue! It was working fine before the most recent update.
I think the latest desktop version uses login shell so
~/.zshrcor~/.bashrcwill be loaded correctly. Separately, there's a new env varCODEX_INSTALL_DIRthat you can use to override your codex installation directory.