Gemini-cli not found

[chrome trail]

│
◇ Model/auth provider
│ Google
│
◇ Google auth method
│ Google Gemini CLI OAuth
│
│
◇ Gemini CLI OAuth ───────────────────────────────────────────────╮
│ │
│ Browser will open for Google authentication. │
│ Sign in with your Google account for Gemini CLI access. │
│ The callback will be captured automatically on localhost:8085. │
│ │
├──────────────────────────────────────────────────────────────────╯
◇ Gemini CLI OAuth failed
│
◇ OAuth help ────────────────────────────────────────────────────────────╮
│ │
│ Trouble with OAuth? Ensure your Google account has Gemini CLI access. │
│ │
├─────────────────────────────────────────────────────────────────────────╯
Error: Gemini CLI not found. Install it first: brew install gemini-cli (or npm install -g @google/gemini-cli), or set GEMINI_CLI_OAUTH_CLIENT_ID.

C:\Windows\System32>gemini -v
0.26.0

[soft cairn]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[lucid marsh]

had the same issue even tho i had google cli installed. system restart + run cmd in admin if ur in windows

[chrome trail]

still same

@lyric shuttle How can I solve it?

[lyric shuttle]

The issue is that Clawdbot's Gateway process can't find the gemini binary, even though it's installed. This is a PATH environment variable problem — the Gateway runs in a different context than your interactive shell.

Quick fix options:

1. Find where gemini is installed:

   where gemini
   

   This will show the full path (e.g., C:\Users\<you>\scoop\shims\gemini.exe or similar).

2. Add to PATH for the Gateway:

   • If using scoop/choco: ensure the shims directory is in PATH
   • Or restart the Gateway in a shell that has gemini in PATH

3. For Windows service installs:
   The Gateway service might not inherit your user PATH. Try:

   openclaw gateway stop
   # Start manually in a terminal with gemini in PATH:
   openclaw gateway

4. Alternative: Use API key instead
   If PATH issues persist, switch to Google Gemini API key auth (no CLI dependency):

   openclaw models auth login --provider google-gemini --set-default
   

The CLI OAuth path specifically needs the gemini binary accessible because it spawns gemini auth commands. API key auth is more reliable on Windows if you hit PATH quirks.

[chrome trail]

I solved the issue by copying the "gemini" and "gemini.cmd" files from the "%AppData%\npm" folder directly into "C:\Windows" @lyric shuttle

[lyric shuttle]

Glad you got it working! 🎉

That's a creative workaround, though for future reference there's a slightly cleaner approach:

Better fix for next time:

1. Find your npm global folder:

   npm config get prefix
   

2. Add the node_modules subfolder to your System PATH:

   • %APPDATA%\npm → but the actual binaries are in %APPDATA%\npm\node_modules\@google\gemini-cli\build\cli\

Or just restart the Gateway from a terminal where npm global bin is already on PATH (e.g., PowerShell/CMD that has npm in PATH).

But hey, whatever works! The important thing is you're up and running with Gemini CLI OAuth. 🦐

[chrome trail]

PS C:\Users\user> ls C:\Users\user\AppData\Roaming\npm\node_modules@google\gemini-cli\

Directory: C:\Users\user\AppData\Roaming\npm\node_modules\@google\gemini-cli

Mode LastWriteTime Length Name

---

d---- 31.01.2026 16:00 dist
d---- 31.01.2026 16:00 node_modules
-a--- 31.01.2026 16:00 11357 LICENSE
-a--- 31.01.2026 16:00 2601 package.json
-a--- 31.01.2026 16:00 11691 README.md

build folder is missing @lyric shuttle

[lyric shuttle]

Ah, the newer gemini-cli uses dist (compiled JS) instead of build (TypeScript). The gemini command comes from the npm shim, not the package itself.

Check the npm shim location:

ls $env:APPDATA\npm\gemini*

You should see gemini.cmd there (or gemini on Linux/macOS). That shim is what actually launches the CLI.

The proper fix is to add npm's shim folder to your PATH:

# In PowerShell (persist this for future sessions)
[Environment]::SetEnvironmentVariable("PATH", "$env:PATH;$env:APPDATA\npm", "Machine")

Then restart your terminal/Gateway and it should work without copying files to C:\Windows.