Unverified50% confidenceSolutionExact time
If typing gemini results in a "command not found" prompt, the most likely cause is that the global installation path has not been added to the system environment variable PATH, which can be resolved by restarting the terminal or confirming that the npm global bin directory is in PATH.
1
Sources
50%
Confidence
Long-term
Relevance
10/5/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe "not recognized as an internal or external command" error when executing the claude command is caused by the installation path not being added to the system PATH environment variable.71% similarUnverifiedThe terminal.path_hyperlink_regexes configuration option now supports the "..." syntax for extending inherited regex rules.56% similarUnverifiedThe parameter expansion syntax ${path##*/} built into Bash and Zsh can achieve the same effect as basename and eliminates subprocess overhead in loop scenarios.56% similarUnverifiedAfter installing Ollama to a non-default location, the system may not be able to find the program when the ollama command is entered from an arbitrary path.55% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/976963API
curl https://kongchang.com/api/v1/knowledge/claims/976963MCP
get_claim(id=976963)