Skip to content

Codex CLI is installed but failed to run. 'codex' is not recognized as an internal or external command, operable program or batch file. #269

Description

@Diopetes
Image

Im a total noob and i have no idea how to fix this

Activity

  1. aaditagrawal commented on Mar 7, 2026

    @aaditagrawal
    Contributor

    Try reinstalling it.

    Sometimes it just does not show up in your path, or might just require a restart of the app.

  2. bradymwilliams commented on Mar 7, 2026

    @bradymwilliams

    I had the same. i just had to paste the path in settings, (installed via homebrew incase that helps)

  3. Diopetes commented on Mar 7, 2026

    @Diopetes
    Author

    Thanks guys! I think i made it work thanks to you both!

  4. albertilagan commented on Mar 7, 2026

    @albertilagan

    Had the same issue.

    Image Image Image
  5. nathanscain commented on Mar 7, 2026

    @nathanscain

    Reasonable based on how early the project is, but homebrew definitely needs to be supported OOTB in a tool for devs

  6. hwanseoc commented on Mar 7, 2026

    @hwanseoc
    Contributor

    FYI - As mentioned in #234 the Codex binary path setting seems to have some bug, as I've built the rustc codex from source and setting this option doesn't change the path.

    not afilliated with authors, but I'd first check that codex is available in PATH of the shell session that t3code was launched from, not any other terminal.

  7. arrudacaio commented on Mar 8, 2026

    @arrudacaio

    i had the same issue in windows 11

  8. sharull9 commented on Mar 8, 2026

    @sharull9
    Image

    I'm Getting this error instead of codex getting node error.
    I think because of fnm in windows how to fix this

  9. muescha commented on Mar 9, 2026

    @muescha

    the codex error is also visible after clean install of codex.

    I need to run codex one time and do an auth to get it working.

    t3code It should recognize this error if codex is not authenticated and should suggest a solution. or at least add the info that codex need to run first to login (or some command line command to force just the login)

  10. nathanscain commented on Mar 10, 2026

    @nathanscain

    I remember theo mentioned that you needed to already be authed in codex since t3code is just passing through the requests. Should probably detect that, but feels like a different issue. The core issue appears fixed - t3 code immediately picked up codex from my path (installed with homebrew) both with I tested with npx t3 and when I installed (also with homebrew)

  11. benakdev commented on Mar 14, 2026

    @benakdev

    I am also getting this error when using the appimage:

    Codex provider status
    Codex CLI (`codex`) is not installed or not on PATH.
    
    

    I did try to run which codex and paste the path which did not work. When using the cli to start the app (web version) it works fine. not sure what is the exact issue yet but I do plan to look into it. worth noting that I use fnm

  12. THammond9 commented on Mar 18, 2026

    @THammond9

    I think my scenario is a bit different from the others. I am not a JS dev, Instead I use C# so installing things using NPM is not standard and I think t3code assumes that NPM installs are present. I have codex installed as part of a VS Code extension and, while I did download the Codex CLI, it did not install anything or add values to the cmd PATH on windows. Just providing some perspective when thinking about different environments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions