#Gemini-cli not working

6 messages · Page 1 of 1 (latest)

wind bluff
#

I wanted to use gemini-cli because it has less rate limits than the normal gemini api

But when i set it up with gemini-cli oauth, when sending a message to the agent i don't get a response, i don't have the same issue with the api or any other provider

errant roseBOT
molten zenithBOT
#

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

errant roseBOT
cedar needleBOT
#

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 is openclaw plugins enable google
  • If gemini works in your shell but the gateway was started as a service, the gateway may not have the same PATH
  • If auth looks OK but requests still fail, set GOOGLE_CLOUD_PROJECT or GOOGLE_CLOUD_PROJECT_ID on the gateway host
  • If your gateway is remote, the OAuth tokens + gemini install 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.