#Gemini-cli not working
6 messages · Page 1 of 1 (latest)
The annoying bit with google-gemini-cli is that it does not use the normal Gemini API path, it shells out to the local gemini binary on the gateway host. So the usual failure points are a bit different.
Most likely checks, from the machine running the gateway:
openclaw --version
openclaw models status --probe-provider google-gemini-cli
openclaw models list --provider google-gemini-cli
which gemini && gemini --version
A few important gotchas:
- If you enabled
google-gemini-cli-auth, that’s old. Current setup isopenclaw plugins enable google - If
geminiworks in your shell but the gateway was started as a service, the gateway may not have the samePATH - If auth looks OK but requests still fail, set
GOOGLE_CLOUD_PROJECTorGOOGLE_CLOUD_PROJECT_IDon the gateway host - If your gateway is remote, the OAuth tokens +
geminiinstall both need to exist on that remote host
If which gemini is the problem, pin the absolute path in config:
{
agents: {
defaults: {
cliBackends: {
"google-gemini-cli": {
command: "/full/path/to/gemini"
}
}
}
}
}
Then restart the gateway.