You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think t3code by default expect latest codex that is built with Rust and is installed as binary not npm package one correction to my comment. I think its due to the way .nvm scopes installed packages.
However, in the settings from the bottom left corner you can customize the codex's path to your custom one.
I think t3code by default expect latest codex that is built with Rust and is installed as binary not npm package one correction to my comment. I think its due to the way .nvm scopes installed packages.
However, in the settings from the bottom left corner you can customize the codex's path to your custom one.
As I mentioned above I did that already. So it seems there are 2 bugs:
codex is not found although it IS in the path (proved by "which codex" returning the correct path)
Activity
sifatulrabbi commentedon Mar 9, 2026
I think t3code by default expect latest codex
that is built with Rust and is installed as binary not npm packageone correction to my comment. I think its due to the way.nvmscopes installed packages.However, in the settings from the bottom left corner you can customize the codex's path to your custom one.
Astisme commentedon Mar 9, 2026
I'm using the AppImage as well but I get the error AND it actually works
nicodh commentedon Mar 11, 2026
As I mentioned above I did that already. So it seems there are 2 bugs:
Problem still exists with version 0.0.9
payne0420 commentedon Mar 25, 2026
Bump, this is still occurring