# Gemini CLI: known issues context pack (KnownFix)
Generated 2026-10-26T10:18:14Z from github.com/google-gemini/gemini-cli. Auto-extracted; verify via links. Source: https://knownfix.ai/issues/gemini-cli/
Fields: severity (auto-estimate) | symptom | versions mentioned | workaround (quoted from issue/comments, if any) | fixed-in (if referenced).

## Active
- [HIGH] Generalist agent hangs (https://github.com/google-gemini/gemini-cli/issues/21409)
  - symptom: Hey! Whenever gemini-cli defers to the generalist agent it hangs forever
  - versions: 0.32.1
  - error: `to enter the interactive CLI, then run the`
  - workaround: none stated
- [HIGH] gemini stuck in thinking loop for hours (https://github.com/google-gemini/gemini-cli/issues/26116)
  - symptom: its cli is thinking and thinking and loop donot breaks event it took 2 hours for completing a task which was just be done in 2 minutes in previous version, its started happening in this latest version
  - versions: 0.39.1, 22.20.0, 292.0
  - error: `its cli is thinking and thinking and loop donot breaks event it took 2 hours for completing a task which was just be done in 2 minutes in previous version, its `
  - workaround: none stated
- [CRITICAL] Gemini CLI latest version is going in infinite loop for authentication (https://github.com/google-gemini/gemini-cli/issues/28018)
  - symptom: Whenever I'm signing in with Google - the Gemini CLI is again asking for authentication and this is never ending One time authentication only Client Information Run gemini to enter the interactive CLI
  - versions: 0.47.0
  - error: `to enter the interactive CLI, then run the`
  - workaround: none stated
- [HIGH] CLI crashes on startup when ran inside a Git repository and MacOS seatbelt is enabled (https://github.com/google-gemini/gemini-cli/issues/28598)
  - symptom: Running Gemini CLI with MacOS seatbelt enabled: And then starting Gemini CLI in a folder that contains a Git repository instantly crashes the CLI
  - versions: 0.53.0
  - error: `│ Sandbox sandbox-exec (permissive-open) │`
  - workaround: none stated
- [MEDIUM] Gemini CLI v0.63.0 - breaks yolo mode (https://github.com/google-gemini/gemini-cli/issues/29682)
  - symptom: ⚠ ⚠️ CRITICAL SECURITY WARNING: Untrusted Command Flags Detected The following flags/arguments were sourced from external untrusted input (e.g., Buganizer ticket, external document): Executing command
  - versions: 0.63.0
  - error: `to enter the interactive CLI, then run the`
  - workaround: then rolled back to v0.62.0 via npm install -g @google/gemini-cli@v0.62 which works. [comment by @crypt0g30rgy (2 reactions)]
- [MEDIUM] GeminiCLI.com Feedback: listed extension logospell/logospell-mcp-server stuck at 5.1.1 since Oct 7 (manifest 6.2.0; inde (https://github.com/google-gemini/gemini-cli/issues/29909)
  - symptom: https://geminicli.com/extensions/ https://geminicli.com/extensions.json The gallery entry for logospell/logospell-mcp-server still shows the extension as it was on October 7, 2026, and hasn't picked u
  - versions: 5.1.1, 6.2.0, 6.0.0
  - error: `extensions.json`
  - workaround: none stated
- [CRITICAL] [Bug]: Google AI Pro sign-in silently falls back to API key onboarding in v0.54.0 (https://github.com/google-gemini/gemini-cli/issues/28717)
  - symptom: On Gemini CLI v0.54.0, selecting "Sign in with Google" and completing the browser flow with a personal Google account that has an active Google AI Pro subscription returns the CLI to the "Enter Gemini
  - versions: 0.54.0
  - error: `Enter Gemini API Key`
  - workaround: none stated
- [MEDIUM] ACP: run_shell_command output is dropped (empty tool_call_update content) when the shell returns AnsiOutput (https://github.com/google-gemini/gemini-cli/issues/29930)
  - symptom: In ACP mode, a runshellcommand call that prints output ends with a toolcallupdate whose content is empty, so an ACP client never sees the command's output
  - versions: 0.65.0
  - error: `{"sessionUpdate":"tool_call","status":"in_progress","title":"echo hello-acp","content":[{"type":"content","content":{"type":"text","text":"[current working dire`
  - workaround: none stated
- [MEDIUM] test(cli): remove redundant lowercase restart test in AdminSettingsChangedDialog (https://github.com/google-gemini/gemini-cli/issues/29936)
  - symptom: AdminSettingsChangedDialog.test.tsx tests the lowercase restart key twice: The standalone test at lines 26–41 renders the dialog, writes 'r' to stdin, and checks that handleRestartMock was called
  - error: `it.each(['r', 'R'])`
  - workaround: none stated
- [HIGH] [Crash]: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory (V8 Heap Limit Exceeded at ~8 (https://github.com/google-gemini/gemini-cli/issues/29830)
  - symptom: The Gemini CLI process stopped with a fatal error after approximately 9.3 hours of one interactive session
  - versions: 0.64.0, 24.10.0, 5.1
  - error: `FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory`
  - workaround: none stated
- [MEDIUM] Persistent 429 RESOURCE_EXHAUSTED on Gemini Code Assist Standard (https://github.com/google-gemini/gemini-cli/issues/29772)
  - symptom: I purchased a Gemini Code Assist Standard subscription and successfully assigned a license to my account
  - error: `to enter the interactive CLI, then run the`
  - workaround: none stated
- [MEDIUM] Body timeout is fixed at 300 s for API-key auth; a long silent tool call is dropped and replayed (https://github.com/google-gemini/gemini-cli/issues/29747)
  - symptom: With @google/gemini-cli 0.64.0 in headless mode (-p, --output-format stream-json), API-key auth and gemini-4-argon at thinkingLevel: HIGH, a turn in which the model writes one large tool-call argument
  - versions: 0.64.0
  - error: `exception TypeError: fetch failed sending request`
  - workaround: none stated