First run and PATH

If a brand new terminal reports tcode is "not recognized" or "command not found" right after installing, the cause is almost always the same: the folder pip installed the entry point into was not yet on that terminal session's PATH when the session started.

tCode checks for exactly this the first time it runs successfully and adds itself to your PATH automatically if it is missing, using the appropriate mechanism for your operating system. This means the fix is usually just opening a genuinely new terminal window rather than anything you need to configure by hand.

If the message persists across more than one fresh terminal, confirm the install actually completed with pip show tcode-cli, and see Troubleshooting for the fuller diagnostic path.

On Windows specifically, the self-fix works by writing the correct Scripts directory into your user-level PATH registry entry; on Linux, it appends the same information to the shell rc file it detects you are using, .bashrc, .zshrc, or similar. Either way, this only takes effect in terminal sessions started after the fix ran, which is the entire reason a fresh terminal is what actually resolves it.

This self-fix runs at most once; once tCode confirms it has already added itself to PATH, it does not repeat the check on every subsequent startup. If you later remove tCode from PATH manually for some reason, reinstalling with pip install --upgrade tcode-cli and running it again re-triggers the same one-time check.