Gemini CLI stuck in "Loading..."

[gsim-inbolt]

Summary

Trying to create a new Gemini CLI thread is not working

Description

I have never been able to use the Gemini CLI integration since it got officially released. Claude works fine though.

Steps to reproduce:

1. Create a new Gemini CLI thread
2. "Loading..." appears and never goes away

I don't have gemini installed locally using npm and no setting related to agents.

I tried to quit Zed, update it, delete Library/Application Support/Zed/external_agents/gemini without success in any of this

Zed Version and System Specs

Zed: v0.204.4 (Zed)
OS: macOS 26.0
Memory: 16 GiB
Architecture: aarch64

[wiyota]

Same here (including specs.)

[Omar-Ahmed85]

The same problem here.
I have Gemini CLI installed at version: "0.6.1".

Zed: Nightly 0.207.0
OS: Windows 10 64-bit
Memory: 8 GiB

[abdull1986]

@zed-intelligence am not sure how was this tested it never worked since day one across all platforms

[CLoaKY233]

I Tried it on windows

win 11 16gb, 

---

with

"agent_servers": {
    "gemini": {
      "ignore_system_version": true
    }
  },

and setting it true aswell,

• Initially some issues came up with the proxy, but resolving them the cli is still stuck on loading
• I have gemini installed in the system aswell, with auth method direct login

ACP logs only show this upon opening a new thread with gemini cli, but there is no further action

{
  "protocolVersion": 1,
  "clientCapabilities": {
    "fs": {
      "readTextFile": true,
      "writeTextFile": true
    },
    "terminal": true
  }
}

---

Also tried to add gemini as an external agent to run it directly that way,

"agent_servers": {
    "Gemini CLI": {
      "command": "C:\\Users\\laysh\\AppData\\Roaming\\npm\\gemini.cmd",
      "args": ["--acp"],
      "env": {}
    }
  },

• This shows exact same behaviour [ stuck on loading with the same acp log aswell ]

{
  "protocolVersion": 1,
  "clientCapabilities": {
    "fs": {
      "readTextFile": true,
      "writeTextFile": true
    },
    "terminal": true
  }
}

• on the assistant panel it shows the error

Internal error: "server shut down unexpectedly"

[ConradIrwin]

This should definitely be working, so I wonder if there's something different about your setup.

What versions of node.js are you using? If you manually run the command with npx ~/Library/Application\ Support/Zed/external_agents/gemini/0.5.4/node_modules/@google/gemini-cli does it work?

If not, does one of you have the time to screen share with me later this week and we can try and debug? Email conrad@zed.dev

[CLoaKY233]

This should definitely be working, so I wonder if there's something different about your setup.

What versions of node.js are you using? If you manually run the command with npx ~/Library/Application\ Support/Zed/external_agents/gemini/0.5.4/node_modules/@google/gemini-cli does it work?

If not, does one of you have the time to screen share with me later this week and we can try and debug? Email conrad@zed.dev

yes it works,
the command exactly was

 npx C:\Users\laysh\AppData\Local\Zed\external_agents\gemini\0.6.1\node_modules\@google\gemini-cli

I can surely help with debugging this, sometime this week. Meanwhile I'll also try to run it directly once and provide the runtime logs of the error aswell!

[p-arndt]

I can confirm that running the comand directly works as @CLoaKY233 mentioned already!

However setting up the client via PATH doesn't work also (https://zed.dev/docs/ai/external-agents#installation) with setting ignore_system_version to false.

In normal normal Powershell Terminal i can execute Gemini, so my path is verified working.

[Omar-Ahmed85]

@ConradIrwin

The command is working just perfectly + I run Gemini in Powershell using the command: gemini and everything is fine.

[Mik3Rizzo]

Same here: Gemini CLI stuck on "Loading...".

Gemini CLI: installed, 0.6.1
npm: 11.5.1
Zed: Nightly 0.207.0
OS: Windows 11

The problem still persists with the setting:

  "agent_servers": {
    "gemini": {
      "ignore_system_version": false
    }
  },

[cole-miller]

For those seeing this on Windows, it's an upstream issue with Gemini CLI, which we've opened a PR to fix: google-gemini/gemini-cli#10339. (On macOS and Linux we're not yet sure what's going on.)