Codex binary not found for fnm installs #246

Activity

1. maria-rcks

   added

   bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.

   on Mar 7, 2026
2. mchisolm0 commented on Mar 8, 2026

   

   mchisolm0

   on Mar 8, 2026

   More actions

   Hey @maheshrijal I had the same problem. Similar to the workaround given in this comment, I ran which codex to find the directory for codex. Then I created a symlink to where t3code expects it using the following command.

   sudo ln -s <output-of-which-codex> /usr/local/bin/codex
3. davidda commented on Mar 9, 2026

   

   davidda

   on Mar 9, 2026

   More actions

   With #486 completed you can just set your path to codex in the settings.

   🎉React with 🎉2Reacted by Matthew Chisolm and Chindriș Mihai - Alexandru
4. idcom-jakub-soboczynski commented on Mar 11, 2026

   

   idcom-jakub-soboczynski

   on Mar 11, 2026

   More actions

   This setting doesn’t seem to work. I configured the path as follows:

   ➜  .codex which codex
   /home/jakub/.bun/bin/codex

   

   However, Codex is still not recognized.

   

   Also, there appears to be an issue with node when it is installed via fnm. The fnm paths look like this:

   ➜  .codex node -v
   v22.22.0
   ➜  .codex which node
   /run/user/1000/fnm_multishells/22992_1773212289328/bin/node
   ➜  .codex

   👍React with 👍1Reacted by Chindriș Mihai - Alexandru
5. maria-rcks

   closed this as completedon Apr 26, 2026