Tools installed by setup script in Codex Web not always accessible to the agent in Plan mode
Resolved 💬 3 comments Opened Oct 21, 2025 by leynos Closed Nov 26, 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-web
What subscription do you have?
Pro
Which model were you using?
gpt-5-codex
What platform is your computer?
Linux (Fedora 42)
What issue are you seeing?
Commandline tools installed in the environment setup script are not always accessible to the agent in Plan mode.
I'm not sure of the exact circumstances, but in some cases, the agent will be unable to execute the tool due to the executable file not being present in the agent's environment.
Running a normal "Code" session usually fixes this, but it means I have to go back to all of the failed sessions and re-run them.
What steps can reproduce the bug?
Place an executable in /usr/local/bin in the environment setup script. Ask the agent to use the tool in Plan mode. The agent's shell sometimes reports command not found.
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
Are you still seeing this problem?
@etraut-openai tbh, I've moved away from Codex cloud due to the cost, so I haven't been able to check this again. Feel free to close.