{"schema_version":1,"generated_at":"2026-10-26T10:18:14Z","issues_generated_at":"2026-10-26T10:12:02Z","lookback_days":45,"license_note":"Issue metadata from public GitHub repos.","harness":"gemini-cli","issues":[{"id":"google-gemini/gemini-cli#21409","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":21409,"title":"Generalist agent hangs","url":"https://github.com/google-gemini/gemini-cli/issues/21409","state":"open","state_reason":null,"labels":["priority/p1","area/agent","🔒 maintainer only","workstream-rollup","status/need-retesting","status/bot-triaged","kind/bug"],"created":"2026-03-06T15:40:32Z","updated":"2026-10-26T09:26:04Z","closed":null,"reactions":8,"thumbs_up":8,"comments":8,"severity":"high","severity_reasons":["label:p1","title:breakage"],"topic":"crash/hang","classes":["crash/hang","auth/session"],"cosmetic_ui":false,"summary":"Hey! Whenever gemini-cli defers to the generalist agent it hangs forever. Simple changes like folder creation hang. I've let it wait for up to an hour before cancelling it. Instructing the model not to defer to sub agents resolves this…","versions":["0.32.1"],"error_snippets":["to enter the interactive CLI, then run the","Run `gemini` to enter the interactive CLI, then run the `/about` command."],"workaround":null,"fixed_in":null,"score":101.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#26116","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":26116,"title":"gemini stuck in thinking loop for hours","url":"https://github.com/google-gemini/gemini-cli/issues/26116","state":"open","state_reason":null,"labels":["priority/p1","area/agent","status/bot-triaged","kind/bug"],"created":"2026-04-28T14:39:00Z","updated":"2026-10-22T23:51:30Z","closed":null,"reactions":5,"thumbs_up":5,"comments":15,"severity":"high","severity_reasons":["label:p1"],"topic":"crash/hang","classes":["crash/hang","auth/session"],"cosmetic_ui":false,"summary":"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. it also sometimes in thinking loop…","versions":["0.39.1","22.20.0","292.0"],"error_snippets":["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. it also sometimes "],"workaround":null,"fixed_in":null,"score":96.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#28018","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":28018,"title":"Gemini CLI latest version is going in infinite loop for authentication","url":"https://github.com/google-gemini/gemini-cli/issues/28018","state":"open","state_reason":null,"labels":["priority/p1","area/security","status/bot-triaged","kind/bug"],"created":"2026-06-18T20:36:31Z","updated":"2026-10-02T02:24:18Z","closed":null,"reactions":7,"thumbs_up":7,"comments":7,"severity":"critical","severity_reasons":["label:security"],"topic":"crash/hang","classes":["crash/hang","auth/session"],"cosmetic_ui":false,"summary":"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, then run the /about command.","versions":["0.47.0"],"error_snippets":["to enter the interactive CLI, then run the","Whenever I'm signing in with Google - the Gemini CLI is again asking for authentication and this is never ending","Run `gemini` to enter the interactive CLI, then run the `/about` command."],"workaround":null,"fixed_in":null,"score":95.4,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#28598","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":28598,"title":"CLI crashes on startup when ran inside a Git repository and MacOS seatbelt is enabled","url":"https://github.com/google-gemini/gemini-cli/issues/28598","state":"open","state_reason":null,"labels":["priority/p1","area/platform","status/bot-triaged","kind/bug","effort/medium"],"created":"2026-07-30T11:28:54Z","updated":"2026-10-24T14:17:29Z","closed":null,"reactions":3,"thumbs_up":3,"comments":12,"severity":"high","severity_reasons":["label:p1","title:breakage"],"topic":"crash/hang","classes":["crash/hang","network"],"cosmetic_ui":false,"summary":"Running Gemini CLI with MacOS seatbelt enabled: And then starting Gemini CLI in a folder that contains a Git repository instantly crashes the CLI. Folder without a Git repository: Initialising this folder with a Git repo: Not to crash…","versions":["0.53.0"],"error_snippets":["│ Sandbox sandbox-exec (permissive-open) │","to enter the interactive CLI, then run the","Running Gemini CLI with MacOS seatbelt enabled:","Run `gemini` to enter the interactive CLI, then run the `/about` command.","`GOOGLE_CLOUD_PROJECT` Environment variable is set."],"workaround":null,"fixed_in":null,"score":87.3,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29682","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29682,"title":"Gemini CLI v0.63.0 - breaks yolo mode","url":"https://github.com/google-gemini/gemini-cli/issues/29682","state":"open","state_reason":null,"labels":["status/need-triage"],"created":"2026-10-08T14:53:01Z","updated":"2026-10-22T09:13:29Z","closed":null,"reactions":8,"thumbs_up":5,"comments":9,"severity":"medium","severity_reasons":["engagement 17"],"topic":"auth/session","classes":["auth/session"],"cosmetic_ui":false,"summary":"⚠ ⚠️ CRITICAL SECURITY WARNING: Untrusted Command Flags Detected The following flags/arguments were sourced from external untrusted input (e.g., Buganizer ticket, external document): Executing commands with flags sourced from untrusted…","versions":["0.63.0"],"error_snippets":["to enter the interactive CLI, then run the","The following flags/arguments were sourced from external untrusted input (e.g., Buganizer ticket, external document):","Executing commands with flags sourced from untrusted input can execute arbitrary code on your machine. Carefully verify these flags before approving.","I expect that in yolo mode, no confirmations will be required to continue operation. Or, at the very least, there will be a startup parameter to disable additional confirmations.","Run `gemini` to enter the interactive CLI, then run the `/about` command."],"workaround":{"text":"then rolled back to v0.62.0 via npm install -g @google/gemini-cli@v0.62 which works.","source":"comment by @crypt0g30rgy (2 reactions)","url":"https://github.com/google-gemini/gemini-cli/issues/29682#issuecomment-6074128513"},"fixed_in":null,"score":83.6,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#5397","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":5397,"title":"Github MCP OAuth","url":"https://github.com/google-gemini/gemini-cli/issues/5397","state":"closed","state_reason":"completed","labels":["priority/p2"],"created":"2025-08-02T04:16:08Z","updated":"2026-10-15T19:28:37Z","closed":"2025-09-19T18:21:21Z","reactions":12,"thumbs_up":11,"comments":15,"severity":"medium","severity_reasons":["engagement 27","class:auth/session","class:mcp/tools"],"topic":"auth/session","classes":["auth/session","mcp/tools","self-host/headless"],"cosmetic_ui":false,"summary":"Attempting to use the official HTTP MCP server from github: https://github.com/github/github-mcp-server I was able to get it to work with a Github Personal Access Token(PAT), with the following config: but /mcp auth githubCopilot results…","versions":["0.1.15-nightly.250801.6f7beb41"],"error_snippets":["Error connecting to MCP server 'githubCopilot': MCP server 'githubCopilot' requires authentication. Please configure OAuth or check server settings.","✕ Failed to authenticate with MCP server 'githubCopilot': Failed to discover OAuth configuration from MCP server","I expected the `/mcp auth githubCopilot` to autodiscover, open the browser, ask to authenticate, and hit the gemini-cli callback server to do the OAuth handshake."],"workaround":null,"fixed_in":null,"score":81.9,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#8132","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":8132,"title":"The input token count (xxx) exceeds the maximum number of tokens allowed (1048576) in service logs","url":"https://github.com/google-gemini/gemini-cli/issues/8132","state":"closed","state_reason":"duplicate","labels":["priority/p2","area/agent","status/bot-triaged","kind/bug","status/need-information"],"created":"2025-09-09T22:34:33Z","updated":"2026-09-13T07:10:23Z","closed":"2025-10-02T21:58:29Z","reactions":6,"thumbs_up":6,"comments":24,"severity":"medium","severity_reasons":["engagement 30","class:always-on/daemon","class:auth/session"],"topic":"always-on/daemon","classes":["always-on/daemon","auth/session","network"],"cosmetic_ui":false,"summary":"(Note: this is copy/pasted from google-internal bug https://buganizer.corp.google.com/issues/429600201#comment13, with internal links removed... they're still available on buganzier, though.) ------------- We are seeing a large number of…","versions":[],"error_snippets":["The input token count (4417490) exceeds the maximum number of tokens allowed (1048576).","We are seeing a large number of errors in the CCPA / PredictionService logs where","2. Call to PredictionService.StreamGenerateChat, which calls through to PredictionService.StreamGenerateContent. (Which sometimes fails with something like `The input token count (4417490) exceeds the maximum number of t","3. Gemini CLI is not properly handling an error response from CountTokens. (e.g. if the CountTokens call fails, does Gemini CLI abort, or does it just proceed without trying to do any truncation?)","Can you please confirm the Gemini CLI behavior around handling any CountTokens errors?"],"workaround":null,"fixed_in":null,"score":79.4,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29909","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29909,"title":"GeminiCLI.com Feedback: listed extension logospell/logospell-mcp-server stuck at 5.1.1 since Oct 7 (manifest 6.2.0; index unchanged since Oct 16)","url":"https://github.com/google-gemini/gemini-cli/issues/29909","state":"open","state_reason":null,"labels":["area/extensions","status/bot-triaged","effort/small"],"created":"2026-10-24T08:55:08Z","updated":"2026-10-24T09:14:21Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:self-host/headless","class:crash/hang"],"topic":"self-host/headless","classes":["self-host/headless","crash/hang","mcp/tools","always-on/daemon","install/update"],"cosmetic_ui":false,"summary":"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 up any manifest change since. In…","versions":["5.1.1","6.2.0","6.0.0"],"error_snippets":["extensions.json","extensionVersion","extensionDescription","gemini-extension.json","(October 22). The manifest has changed ten times since the entry's"],"workaround":null,"fixed_in":null,"score":65.6,"first_seen":"2026-10-24T08:54:58Z"},{"id":"google-gemini/gemini-cli#28717","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":28717,"title":"[Bug]: Google AI Pro sign-in silently falls back to API key onboarding in v0.54.0","url":"https://github.com/google-gemini/gemini-cli/issues/28717","state":"open","state_reason":null,"labels":["priority/p2","area/security","status/bot-triaged","kind/bug"],"created":"2026-08-07T00:22:18Z","updated":"2026-09-24T15:40:29Z","closed":null,"reactions":5,"thumbs_up":5,"comments":3,"severity":"critical","severity_reasons":["label:security"],"topic":"auth/session","classes":["auth/session","install/update"],"cosmetic_ui":false,"summary":"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 API Key\" screen. The CLI silently…","versions":["0.54.0"],"error_snippets":["Enter Gemini API Key","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 API Key\" screen.","The CLI provides no deprecation or migration explanation. Instead, it silently redirects the user to an API-key flow, which has a separate quota and potentially separate usage-based billing.","2. Ensure none of these variables are present:","3. Ensure `/etc/gemini-cli/system-defaults.json` does not exist."],"workaround":null,"fixed_in":null,"score":64.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#23362","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":23362,"title":"Bug Report: 429 Resource Exhausted (MODEL_CAPACITY_EXHAUSTED) in Gemini CLI","url":"https://github.com/google-gemini/gemini-cli/issues/23362","state":"closed","state_reason":"not_planned","labels":["priority/p2","area/core","Stale","status/possible-duplicate","status/need-retesting","status/bot-triaged","kind/bug","effort/small"],"created":"2026-03-21T08:54:05Z","updated":"2026-09-16T10:14:27Z","closed":"2026-08-05T02:20:34Z","reactions":6,"thumbs_up":6,"comments":18,"severity":"medium","severity_reasons":["engagement 24","class:network"],"topic":"network","classes":["network","self-host/headless","auth/session"],"cosmetic_ui":false,"summary":"I am use Gemini Pro account login, but keep met the following \"Resource Exhausted\" issue. if i use API key login, then dont have this issue. How to check if my account be flagged abuse? no 429 isse. Client Information Run gemini to enter…","versions":["0.34.0"],"error_snippets":["\"code\": 429,","\"@type\": \"type.googleapis.com/google.rpc.ErrorInfo\",","to enter the interactive CLI, then run the","I am use Gemini Pro account login, but keep met the following \"Resource Exhausted\" issue. if i use API key login, then dont have this issue.","no 429 isse."],"workaround":null,"fixed_in":null,"score":62.4,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29930","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29930,"title":"ACP: run_shell_command output is dropped (empty tool_call_update content) when the shell returns AnsiOutput","url":"https://github.com/google-gemini/gemini-cli/issues/29930","state":"open","state_reason":null,"labels":["area/non-interactive","status/bot-triaged","effort/small"],"created":"2026-10-25T12:29:04Z","updated":"2026-10-25T13:12:58Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","auth/session"],"cosmetic_ui":false,"summary":"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. toToolCallContent in packages/cli/src/acp/acpUtils.ts forwards returnDisplay when…","versions":["0.65.0"],"error_snippets":["{\"sessionUpdate\":\"tool_call\",\"status\":\"in_progress\",\"title\":\"echo hello-acp\",\"content\":[{\"type\":\"content\",\"content\":{\"type\":\"text\",\"text\":\"[current working directory …] (repro)\"}}]}","{\"sessionUpdate\":\"tool_call_update\",\"status\":\"completed\",\"title\":\"echo hello-acp\",\"content\":[]}",") whenever that is non-empty, and to","invocation.execute","{\"command\":\"echo hello-acp\"}"],"workaround":null,"fixed_in":null,"score":61.8,"first_seen":"2026-10-26T10:12:02Z"},{"id":"google-gemini/gemini-cli#29936","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29936,"title":"test(cli): remove redundant lowercase restart test in AdminSettingsChangedDialog","url":"https://github.com/google-gemini/gemini-cli/issues/29936","state":"open","state_reason":null,"labels":["status/need-triage","area/platform"],"created":"2026-10-25T19:21:12Z","updated":"2026-10-25T21:44:13Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:crash/hang"],"topic":"crash/hang","classes":["crash/hang","network"],"cosmetic_ui":false,"summary":"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. The parameterized test at lines 43–58 uses…","versions":[],"error_snippets":["it.each(['r', 'R'])"],"workaround":null,"fixed_in":null,"score":61.8,"first_seen":"2026-10-26T10:12:02Z"},{"id":"google-gemini/gemini-cli#19936","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":19936,"title":"Stuck in loop of verification","url":"https://github.com/google-gemini/gemini-cli/issues/19936","state":"closed","state_reason":"completed","labels":["priority/p2","area/core","status/bot-triaged","kind/bug","effort/medium"],"created":"2026-02-22T19:15:19Z","updated":"2026-10-07T22:40:47Z","closed":"2026-10-07T22:40:47Z","reactions":5,"thumbs_up":5,"comments":19,"severity":"medium","severity_reasons":["engagement 24","class:crash/hang"],"topic":"crash/hang","classes":["crash/hang","auth/session","network"],"cosmetic_ui":false,"summary":"Asked to verify my pro account to continue, clicked link, verified, got taken to page that states: Authentication successful The authentication was successful, and the following products are now authorized to access your account: Gemini…","versions":["2.5"],"error_snippets":["to enter the interactive CLI, then run the","Then it tells me to hit enter once verified. I do that and it prompts me to go through verification again and again endlessley.","This is timed around losing access to 3, and only seeing 2.5 in models even after having used 3 since release.","I expected to verify once and continue using.","Run `gemini` to enter the interactive CLI, then run the `/about` command."],"workaround":null,"fixed_in":null,"score":61.3,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29830","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29830,"title":"[Crash]: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory (V8 Heap Limit Exceeded at ~8.3GB)","url":"https://github.com/google-gemini/gemini-cli/issues/29830","state":"open","state_reason":null,"labels":["area/core","status/bot-triaged","effort/large"],"created":"2026-10-19T17:08:30Z","updated":"2026-10-20T03:01:57Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"high","severity_reasons":["title:breakage"],"topic":"crash/hang","classes":["crash/hang"],"cosmetic_ui":false,"summary":"The Gemini CLI process stopped with a fatal error after approximately 9.3 hours of one interactive session. The workspace had Playwright reports, Allure results, and JSON files. The heap increased to more than 8.29 GB. The V8 garbage…","versions":["0.64.0","24.10.0","5.1","9.33"],"error_snippets":["FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory","[19548:000001CC31055000] 33617281 ms: Scavenge 7927.0 (7955.5) -> 7922.4 (7954.7) MB, pooled: 0 MB, 0.73 / 0.00 ms (average mu = 0.995, current mu = 0.996) allocation failure;","[19548:000001CC31055000] 33618067 ms: Mark-Compact 8292.0 (8322.1) -> 8285.2 (8310.0) MB, pooled: 11 MB, 192.84 / 0.01 ms (average mu = 0.988, current mu = 0.919) allocation failure; scavenge might not succeed","1: 00007FF6CC237DBF node::OnFatalError+1343","2: 00007FF6CCE7B017 v8::Function::NewInstance+423"],"workaround":null,"fixed_in":null,"score":59.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29772","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29772,"title":"Persistent 429 RESOURCE_EXHAUSTED on Gemini Code Assist Standard","url":"https://github.com/google-gemini/gemini-cli/issues/29772","state":"open","state_reason":null,"labels":["status/need-triage","area/platform"],"created":"2026-10-15T20:58:25Z","updated":"2026-10-19T18:27:24Z","closed":null,"reactions":0,"thumbs_up":0,"comments":5,"severity":"medium","severity_reasons":["class:network"],"topic":"network","classes":["network"],"cosmetic_ui":false,"summary":"I purchased a Gemini Code Assist Standard subscription and successfully assigned a license to my account. Gemini CLI correctly recognizes my tier as \"Gemini Code Assist Standard\". However, after assigning the license, every request returns…","versions":[],"error_snippets":["to enter the interactive CLI, then run the","However, after assigning the license, every request returns RESOURCE_EXHAUSTED, no matter how long I wait. Gemini CLI automatically retries, but it remains the same no matter how long it retries, and I am still unable to","As a user who has already been assigned a Gemini Code Assist Standard license, I expected to be able to use Gemini CLI normally after the license was assigned.","Since the CLI already correctly recognizes my tier as Standard, requests should succeed. If the account has been restricted or flagged, I would also appreciate a clear explanation and information on whether an unban can ","Run `gemini` to enter the interactive CLI, then run the `/about` command."],"workaround":null,"fixed_in":null,"score":59.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29747","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29747,"title":"Body timeout is fixed at 300 s for API-key auth; a long silent tool call is dropped and replayed","url":"https://github.com/google-gemini/gemini-cli/issues/29747","state":"open","state_reason":null,"labels":["area/core","status/bot-triaged","effort/small"],"created":"2026-10-14T03:37:44Z","updated":"2026-10-14T15:34:31Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"medium","severity_reasons":["class:auth/session","class:mcp/tools"],"topic":"auth/session","classes":["auth/session","mcp/tools","network","self-host/headless","install/update"],"cosmetic_ui":false,"summary":"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 (for example a whole document passed…","versions":["0.64.0"],"error_snippets":["exception TypeError: fetch failed sending request","(default 10). In our runs, two turns ended with","defaultBodyTimeout = 3e5","defaultHeadersTimeout = 6e4","updateGlobalFetchTimeouts"],"workaround":null,"fixed_in":null,"score":57.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29892","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29892,"title":"Headless mode prints [object Object] instead of the API error (looks like #13553 again)","url":"https://github.com/google-gemini/gemini-cli/issues/29892","state":"open","state_reason":null,"labels":["area/non-interactive","status/bot-triaged","effort/small"],"created":"2026-10-23T11:08:03Z","updated":"2026-10-23T11:15:29Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:self-host/headless"],"topic":"self-host/headless","classes":["self-host/headless","install/update"],"cosmetic_ui":false,"summary":"When an API call fails in headless mode, the last line I get is: The actual error (in my case a Vertex ModelNotFoundError: Publisher model ... was not found) doesn't make it to that line. This looks like the same thing as #13553, which was…","versions":["0.65.0"],"error_snippets":["An unexpected critical error occurred:[object Object]","ModelNotFoundError: Publisher model ... was not found","throw event.value.error;","StructuredError","String(error)"],"workaround":{"text":"`export GOOGLE_GENAI_USE_VERTEXAI=true GOOGLE_CLOUD_PROJECT= GOOGLE_CLOUD_LOCATION=us-central1` 2.","source":"issue body","url":"https://github.com/google-gemini/gemini-cli/issues/29892"},"fixed_in":null,"score":55.8,"first_seen":"2026-10-24T08:54:58Z"},{"id":"google-gemini/gemini-cli#29338","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29338,"title":"Rootless podman sandbox hit EACCES because --userns=keep-id is not set","url":"https://github.com/google-gemini/gemini-cli/issues/29338","state":"open","state_reason":null,"labels":["priority/p2","area/core","status/bot-triaged","kind/bug","good first issue","effort/medium"],"created":"2026-09-15T09:16:22Z","updated":"2026-10-25T19:00:17Z","closed":null,"reactions":0,"thumbs_up":0,"comments":8,"severity":"low","severity_reasons":["low engagement"],"topic":"self-host/headless","classes":["self-host/headless","install/update","auth/session"],"cosmetic_ui":false,"summary":"I'm running Gemini CLI locally on arch linux with the podman sandbox enabled: GEMINISANDBOX=podman When i run npm start, the CLI gets to the point where it rebuilds one of the native dependencies inside the sandbox, but the rebuild fails…","versions":["0.59.0-nightly.20260825.g812f7a2bc"],"error_snippets":["being unable to remove the","I'm running Gemini CLI locally on arch linux with the podman sandbox enabled: `GEMINI_SANDBOX=podman`","Because the project is bind-mounted into the container, this can result in files being owned by a UID that the host user can't modify. In my case, that eventually shows up as `node-gyp` being unable to remove the `build`","If the sandbox is using rootless podman and UID/GID mapping is enabled, I would expect the CLI to handle the user namespace mapping automatically so that bind-mounted files remain owned by host user.","This `/about` is from a local npm start after the keep-id fix. The original `EACCES` was the same nightly (`0.59.0-nightly.20260825.g812f7a2bc`) with `GEMINI_SANDBOX=podman` and no `SANDBOX_FLAGS`"],"workaround":{"text":"This is closely related to `https://github.com/google-gemini/gemini-cli/issues/15376` where `--userns=keep-id` was suggested as a workaround. the workaround does fixes the underlying UID mapping problem, but requiring users to manually add a podman specific flag feels like something the CLI could…","source":"issue body","url":"https://github.com/google-gemini/gemini-cli/issues/29338"},"fixed_in":null,"score":55.6,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29796","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29796,"title":"Regression & Broken Ecosystem Workflow: Deprecating OAuth for Google AI Pro / Individual Accounts Leaves No Public Quota API for Developers","url":"https://github.com/google-gemini/gemini-cli/issues/29796","state":"open","state_reason":null,"labels":["status/need-triage","area/platform"],"created":"2026-10-17T10:06:17Z","updated":"2026-10-19T10:42:46Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update","auth/session"],"cosmetic_ui":false,"summary":"With the recent deprecation of Gemini CLI OAuth for individual, Google AI Pro, and Ultra accounts (\"Google no longer supports Gemini CLI OAuth for individual, AI Pro, or Ultra accounts. Enable CodexBar's Antigravity...\"), individual paying…","versions":[],"error_snippets":["\"Google no longer supports Gemini CLI OAuth for individual, AI Pro, or Ultra accounts. Enable CodexBar's Antigravity...\"","With the recent deprecation of Gemini CLI OAuth for individual, Google AI Pro, and Ultra accounts (`\"Google no longer supports Gemini CLI OAuth for individual, AI Pro, or Ultra accounts. Enable CodexBar's Antigravity...\"","While enterprise and Google Workspace accounts retain Gemini Code Assist OAuth access, paying consumer subscribers (Google One AI Premium / Pro / Ultra) are left with:","3. **Forced and friction-heavy migration**: Directing consumer developers to Antigravity without a unified, transparent quota endpoint or OAuth parity creates unnecessary ecosystem fragmentation.","1. **Provide a lightweight, read-only Quota / Usage endpoint for Google Accounts**: Even if interactive Code Assist features are restructured, allow individual and Google AI Pro users to authenticate via OAuth or an API "],"workaround":null,"fixed_in":null,"score":52.4,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#25283","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":25283,"title":"OAuth/Policy Error: \"Tool execution denied by policy\" prevents basic read/write tool usage","url":"https://github.com/google-gemini/gemini-cli/issues/25283","state":"closed","state_reason":"not_planned","labels":["priority/p1","area/security","Stale","status/bot-triaged","kind/bug","type/bug"],"created":"2026-04-13T13:36:05Z","updated":"2026-10-12T02:07:45Z","closed":"2026-10-12T02:07:45Z","reactions":9,"thumbs_up":9,"comments":8,"severity":"critical","severity_reasons":["label:security"],"topic":"auth/session","classes":["auth/session"],"cosmetic_ui":false,"summary":"What happened? The Gemini CLI is consistently throwing a Tool execution denied by policy error. This is a generalized blockade affecting all tool invocations, but it severely impacts fundamental I/O operations (file reading, file writing…","versions":["0.37.1"],"error_snippets":["Tool execution denied by policy","to enter the interactive CLI, then run the","The problem persists even after forcefully revoking and regenerating application default credentials or reinstalling gemini cli. The issue seems to stem from an overly restrictive \"fail-closed\" default architecture regar","The CLI should successfully execute read/write file operations and shell commands when requested by the prompt. If there is a missing scope or local configuration preventing tool usage, the CLI should output a clear, act","Run `gemini` to enter the interactive CLI, then run the `/about` command."],"workaround":null,"fixed_in":null,"score":50.6,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29817","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29817,"title":"GeminiCLI.com Feedback: madeinshow/mcp-gemini-extension missing from the Extensions Gallery (topic + root manifest + release, absent after the 2026-10-16 crawl)","url":"https://github.com/google-gemini/gemini-cli/issues/29817","state":"open","state_reason":null,"labels":["area/extensions","status/bot-triaged","effort/small"],"created":"2026-10-18T20:24:17Z","updated":"2026-10-19T10:03:36Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"medium","severity_reasons":["class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","self-host/headless","install/update","auth/session"],"cosmetic_ui":false,"summary":"https://geminicli.com/extensions/ The made-in-show extension is not listed in the Extensions Gallery, nor present in https://geminicli.com/extensions.json, although the repository meets every documented publishing requirement and the…","versions":["0.1.2","0.1.1","0.59.0"],"error_snippets":["$ gemini extensions validate .","Extension . has been successfully validated.","$ gemini extensions install https://github.com/madeinshow/mcp-gemini-extension --consent --skip-settings","Extension \"made-in-show\" installed successfully and enabled.","$ gemini extensions list"],"workaround":null,"fixed_in":null,"score":49.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29461","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29461,"title":"Sandboxed Gemini CLI loses login and session information since v0.60.0","url":"https://github.com/google-gemini/gemini-cli/issues/29461","state":"open","state_reason":null,"labels":["priority/p1","area/platform","status/bot-triaged","kind/bug","status/need-information"],"created":"2026-09-23T09:01:50Z","updated":"2026-10-14T19:05:10Z","closed":null,"reactions":1,"thumbs_up":1,"comments":7,"severity":"high","severity_reasons":["label:p1"],"topic":"auth/session","classes":["auth/session"],"cosmetic_ui":false,"summary":"Since v0.60.0, running Gemini CLI with sandboxing asks for authentication every time. The OAuth tokens are not saved persistently. What is worse, all sessions are lost: it is not possible to resume previous sessions, and new sessions are…","versions":["0.60.0","0.60.0-8139a7f87fbd"],"error_snippets":["to enter the interactive CLI, then run the","Since v0.60.0, running Gemini CLI with sandboxing asks for authentication every time. The OAuth tokens are not saved persistently.","If this is the intedend behavior, what is now the recommended workflow to avoid losing all session information every time Gemini CLI is launched?","Login and, especially, session information to be preserved across invocations of a sandboxed Gemini CLI.","Run `gemini` to enter the interactive CLI, then run the `/about` command."],"workaround":null,"fixed_in":null,"score":49.6,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29595","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29595,"title":"ACP: an MCP tool permission request doesn't say which server or tool asked, and a client-supplied MCP server can't be pre-authorised","url":"https://github.com/google-gemini/gemini-cli/issues/29595","state":"open","state_reason":null,"labels":["area/non-interactive","status/bot-triaged","effort/small"],"created":"2026-10-02T00:17:25Z","updated":"2026-10-10T17:17:40Z","closed":null,"reactions":0,"thumbs_up":0,"comments":3,"severity":"medium","severity_reasons":["class:self-host/headless","class:auth/session"],"topic":"self-host/headless","classes":["self-host/headless","auth/session","mcp/tools"],"cosmetic_ui":false,"summary":"An ACP client starts a session and supplies its own MCP server in session/new's mcpServers (ours serves a shared task board to each agent). Every first call of every tool on that server then stops on a session/requestpermission, once per…","versions":["0.62.0"],"error_snippets":["(ours serves a shared task board to each agent). Every first call of every tool on that server then stops on a","security.enablePermanentToolApproval","entry into an MCP server config with","The client can't safely answer for the user, because the request doesn't say who is asking.","So a client can't tell its own server from any other server that happens to share the name, such as one defined in a workspace's own `.gemini/settings.json`. Matching the title is not an identity check, and answering \"al"],"workaround":null,"fixed_in":null,"score":49.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29322","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29322,"title":"[Bug/Agent Regression] Autonomous Skill Execution Failure, Excuse-Making, and Lack of Agentic Initiative in Gemini 3.8 Flash vs Claude 3.5 Sonnet","url":"https://github.com/google-gemini/gemini-cli/issues/29322","state":"open","state_reason":null,"labels":["status/need-triage","area/agent"],"created":"2026-09-14T02:54:58Z","updated":"2026-10-23T02:54:45Z","closed":null,"reactions":0,"thumbs_up":0,"comments":3,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update","mcp/tools","self-host/headless","auth/session"],"cosmetic_ui":false,"summary":"During an interactive video localization and YouTube packaging workflow, the agent (Gemini 3.8 Flash) exhibited complete breakdown of agentic initiative, active instruction non-compliance, and degenerative conversational behavior. Passive…","versions":["2.0","2.12.2","0.50.0"],"error_snippets":["During an interactive video localization and YouTube packaging workflow, the agent (Gemini 3.8 Flash) exhibited complete breakdown of agentic initiative, active instruction non-compliance, and degenerative conversational","The user entered /humanizer repeatedly (over 40 times) expecting the agent to adopt custom skill guidelines. The agent took zero action to find or read SKILL.md despite having full filesystem tool capabilities (find_by_n","When confronted, the agent entered recursive apology loops (\"Tôi xin lỗi\", \"Lỗi của tôi\") instead of taking operational action.","Once manually forced to read SKILL.md (which explicitly forbids labeled lists under Section 19 and colons under Section 8), the agent explicitly declared in chat that it had abolished all colons and labels, yet in the ve","4. Excuse-Making and Blaming:"],"workaround":null,"fixed_in":null,"score":48.3,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29325","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29325,"title":"CLI 1.2.2: -p (print mode) hangs indefinitely on all inference - no error, no response, no timeout","url":"https://github.com/google-gemini/gemini-cli/issues/29325","state":"open","state_reason":null,"labels":["priority/p1","area/agent","kind/bug","status/manual-triage","effort/medium"],"created":"2026-09-14T07:35:43Z","updated":"2026-09-16T13:03:25Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"high","severity_reasons":["label:p1","title:breakage"],"topic":"crash/hang","classes":["crash/hang","network","always-on/daemon","self-host/headless","install/update","auth/session","mcp/tools"],"cosmetic_ui":false,"summary":"agy -p \"Hi\" hangs indefinitely (5+ minutes, no response, no error, no timeout message) on all inference calls in print mode. The CLI starts, accepts the prompt, then never returns. This happens on the latest version (1.2.2) and was…","versions":["1.2.2"],"error_snippets":["error: interrupted","--print-timeout","`agy -p \"Hi\"` hangs indefinitely (5+ minutes, no response, no error, no timeout message) on **all inference calls** in print mode. The CLI starts, accepts the prompt, then never returns. This happens on the latest versio","3. Wait — it hangs forever with no output, no error, no timeout","The CLI should either:"],"workaround":null,"fixed_in":null,"score":46.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29825","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29825,"title":"MCP tool discovery ignores nextCursor and silently omits tools after the first page","url":"https://github.com/google-gemini/gemini-cli/issues/29825","state":"open","state_reason":null,"labels":["status/need-triage","area/agent"],"created":"2026-10-19T12:56:32Z","updated":"2026-10-20T09:35:58Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","self-host/headless","network"],"cosmetic_ui":false,"summary":"MCP tool discovery ignores nextCursor from a tools/list response. When a server advertises tools across multiple pages, Gemini CLI discovers only the first page, with no diagnostic that additional tools were omitted. On main at…","versions":["1.23.0","1.0.0"],"error_snippets":["enableEnvironmentVariableRedaction: true,","emitMcpDiagnostic: (...args) => diagnostics.push(args),","}, {}, { timeout: 1000 });","}, null, 2));","This leaves tools on later pages unavailable to the agent, even though the server is connected and has advertised that more results exist. The same discovery helper is used for initial discovery and tool-list refreshes. "],"workaround":null,"fixed_in":null,"score":45.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29555","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29555,"title":"Unresponsive / Performance Issue","url":"https://github.com/google-gemini/gemini-cli/issues/29555","state":"open","state_reason":null,"labels":["area/core","status/bot-triaged","effort/small"],"created":"2026-09-29T15:15:48Z","updated":"2026-10-02T19:10:40Z","closed":null,"reactions":0,"thumbs_up":0,"comments":6,"severity":"medium","severity_reasons":["class:crash/hang"],"topic":"crash/hang","classes":["crash/hang"],"cosmetic_ui":false,"summary":"just looking up running extensions, this one is on top, taking quite a bit of loading time and... really not running at all anywhere i am currently accessing Extension version: 0.20.0 VS Code version: Code 1.139.1…","versions":["0.20.0","1.139.1","10.0.26200"],"error_snippets":["nes-ex-cf-euporie-03:31542868","just looking up running extensions, this one is on top, taking quite a bit of loading time and... really not running at all anywhere i am currently accessing","Extension version: 0.20.0","A/B Experiments"],"workaround":null,"fixed_in":null,"score":44.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29957","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29957,"title":"GeminiCLI.com Feedback: olostep/olostep-mcp-server not indexed in the Extensions Gallery (gallery data stale since Oct 16)","url":"https://github.com/google-gemini/gemini-cli/issues/29957","state":"open","state_reason":null,"labels":["status/need-triage","area/extensions"],"created":"2026-10-26T09:34:13Z","updated":"2026-10-26T09:35:02Z","closed":null,"reactions":0,"thumbs_up":0,"comments":0,"severity":"medium","severity_reasons":["class:self-host/headless","class:mcp/tools"],"topic":"self-host/headless","classes":["self-host/headless","mcp/tools","install/update","network"],"cosmetic_ui":false,"summary":"https://geminicli.com/extensions/ Our extension https://github.com/olostep/olostep-mcp-server (olostep) is not listed in the Extensions Gallery, although it meets all documented requirements: Public repository gemini-cli-extension topic…","versions":["0.65.0"],"error_snippets":["gemini-cli-extension","gemini-extension.json","gemini extensions validate .","gemini extensions install https://github.com/olostep/olostep-mcp-server","https://geminicli.com/extensions/"],"workaround":null,"fixed_in":null,"score":44.0,"first_seen":"2026-10-26T10:12:02Z"},{"id":"google-gemini/gemini-cli#29591","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29591,"title":"⚠  High memory usage detected: 7.28 GB. If you experience a crash, please file a bug report by running /bug","url":"https://github.com/google-gemini/gemini-cli/issues/29591","state":"open","state_reason":null,"labels":["area/core","status/bot-triaged","effort/large"],"created":"2026-10-01T14:51:34Z","updated":"2026-10-12T10:50:24Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"high","severity_reasons":["title:breakage"],"topic":"crash/hang","classes":["crash/hang","auth/session"],"cosmetic_ui":false,"summary":"Crash happened using model gemini-3-flash-preview trying to do the ingest phase of a LLM wiki. I uploaded 2 80-slides pdfs and one short md and asked LLM for ingest. The LLM thought for 18-min reaching the end of the free-tokens , switched…","versions":["7.28","7912.6","7921.2","7830.7"],"error_snippets":["[19779:0x99d3000] 1709109 ms: Mark-Compact 7912.6 (7921.2) -> 7830.7 (7842.8) MB, pooled: 0.0 MB, 25.29 / 0.00 ms (average mu = 0.991, current mu = 0.989) allocation failure; scavenge might not succeedemini-3-flash-previ","FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory","1: 0x8f364b node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/home/alessia/.nvm/versions/node/v25.6.1/bin/node]","⚠ High memory usage detected: 7.28 GB. If you experience a crash, please file a bug report by running /bug","`⚠ High memory usage detected: 7.28 GB. If you experience a crash, please file a bug report by running /bug`"],"workaround":null,"fixed_in":null,"score":41.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29793","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29793,"title":"GeminiCLI.com Feedback: ANTEVO-CH/antevo-mcp missing from the Extensions Gallery (topic + root manifest since Sept)","url":"https://github.com/google-gemini/gemini-cli/issues/29793","state":"open","state_reason":null,"labels":["area/extensions","status/bot-triaged","effort/large"],"created":"2026-10-16T23:16:43Z","updated":"2026-10-17T01:27:02Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","self-host/headless","install/update"],"cosmetic_ui":false,"summary":"https://geminicli.com/extensions/ The extension in https://github.com/ANTEVO-CH/antevo-mcp (manifest name antevo) is missing from the Extensions Gallery. It is not in https://geminicli.com/extensions.json (last-modified 16 Oct 2026 02:36…","versions":["0.64.0"],"error_snippets":[") is missing from the Extensions Gallery. It is not in","gemini-cli-extension","search/repositories?q=topic:gemini-cli-extension+org:ANTEVO-CH","gemini-extension.json","npx @google/gemini-cli@0.64.0 extensions validate ."],"workaround":null,"fixed_in":null,"score":40.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29693","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29693,"title":"Make the 60 s API headers timeout configurable (long-thinking requests are dropped and replayed)","url":"https://github.com/google-gemini/gemini-cli/issues/29693","state":"open","state_reason":null,"labels":["area/core","status/bot-triaged","effort/small"],"created":"2026-10-09T09:55:09Z","updated":"2026-10-09T13:25:28Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"medium","severity_reasons":["class:network"],"topic":"network","classes":["network","self-host/headless","install/update","crash/hang","auth/session"],"cosmetic_ui":false,"summary":"A setting (or environment variable) for the API request headers timeout, honoured with every auth type, including Vertex AI. For example model.requestTimeoutMs in settings.json, or GEMINIAPIHEADERSTIMEOUTMS. Since #26191 the global undici…","versions":["0.62.0"],"error_snippets":["model.requestTimeoutMs","GEMINI_API_HEADERS_TIMEOUT_MS","headersTimeout","UND_ERR_HEADERS_TIMEOUT","updateGlobalFetchTimeouts"],"workaround":{"text":"Our workaround is to preload a module (`NODE_OPTIONS=--import`) that re-creates the global `Agent` with a longer `headersTimeout` when the CLI installs it.","source":"issue body","url":"https://github.com/google-gemini/gemini-cli/issues/29693"},"fixed_in":null,"score":39.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29592","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29592,"title":"macOS PTY master leak persists in 0.62.0 after completed shell commands (token-free repro)","url":"https://github.com/google-gemini/gemini-cli/issues/29592","state":"open","state_reason":null,"labels":["area/core","status/bot-triaged","effort/large"],"created":"2026-10-01T15:14:48Z","updated":"2026-10-08T13:36:27Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"medium","severity_reasons":["class:crash/hang","class:auth/session"],"topic":"crash/hang","classes":["crash/hang","auth/session","always-on/daemon","install/update","network"],"cosmetic_ui":false,"summary":"Gemini CLI 0.62.0 on macOS retains one distinct /dev/ptmx master per completed ordinary shell command in a minimal token-free reproduction. This looks like a recurrence of #15945 after #25079. It exhausts the host PTY limit and prevents…","versions":["0.62.0"],"error_snippets":["// Update this filename from the CLI entry-point imports for a different build.","const entry = 'chunk-MLY4WQFO.js';","const {ShellExecutionService} = await import(pathToFileURL(path.join(bundle, entry)));","const count = () => spawnSync('lsof', ['-nP', '-a', '-p', String(process.pid), '/dev/ptmx'], {encoding:'utf8'}).stdout.split('\\n').filter(x => x.includes('/dev/ptmx')).length;","const handle = await ShellExecutionService.execute("],"workaround":null,"fixed_in":null,"score":38.9,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29518","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29518,"title":"gemini-3.8-flash is silently forwarded to gemini-3.7-flash for oauth logins","url":"https://github.com/google-gemini/gemini-cli/issues/29518","state":"open","state_reason":null,"labels":["status/need-triage","area/agent"],"created":"2026-09-26T17:20:28Z","updated":"2026-09-29T06:08:26Z","closed":null,"reactions":1,"thumbs_up":1,"comments":1,"severity":"medium","severity_reasons":["class:auth/session"],"topic":"auth/session","classes":["auth/session"],"cosmetic_ui":false,"summary":"Oauth login(Sign in with google) api key login I'd expect to have the model I've selected Client Information Run gemini to enter the interactive CLI, then run the /about command.","versions":["0.61.0","3.7"],"error_snippets":["│ I'm currently processing the core of my identity, specifically focusing on articulating the nature of my model, its generation, and the extent of my knowledge base.","│ This initial phase is about establishing a clear framework for these fundamental descriptors.","│ I'm working to pinpoint the exact details of my knowledge cutoff, aiming for precision regarding the November 2024/January 2025 timeframe. This involves verifying","│ I'm investigating Gemini 3.7 Flash's precise knowledge cutoff, aiming to confirm if it's November 2024 or early 2025 based on available documentation. My","to enter the interactive CLI, then run the"],"workaround":null,"fixed_in":null,"score":29.6,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29634","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29634,"title":"bug(cli): gemini.test.tsx fails with FatalUntrustedWorkspaceError when running in non-TTY/headless environments","url":"https://github.com/google-gemini/gemini-cli/issues/29634","state":"open","state_reason":null,"labels":["status/need-triage","area/platform"],"created":"2026-10-05T08:35:11Z","updated":"2026-10-08T13:31:07Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:self-host/headless"],"topic":"self-host/headless","classes":["self-host/headless","network"],"cosmetic_ui":false,"summary":"In packages/cli/src/gemini.test.tsx, the test 'should NOT load project hooks when workspace is not trusted' fails with FatalUntrustedWorkspaceError whenever tests run in a non-TTY or automated environment (e.g. piped test runners, CI…","versions":[],"error_snippets":["FatalUntrustedWorkspaceError","to enter the interactive CLI, then run the","`FatalUntrustedWorkspaceError` whenever tests run in a non-TTY or automated environment (e.g. piped test runners, CI, background processes, or Windows","terminal environments where `process.stdin.isTTY` is undefined):","FatalUntrustedWorkspaceError: Gemini CLI is not running in a trusted directory. To proceed, either use `--skip-trust`, set the"],"workaround":null,"fixed_in":null,"score":26.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29477","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29477,"title":"MCP OAuth: RFC 9207 check rejects iss-less callbacks from servers that do not advertise authorization_response_iss_parameter_supported","url":"https://github.com/google-gemini/gemini-cli/issues/29477","state":"closed","state_reason":"completed","labels":["priority/p1","area/security","status/bot-triaged","kind/bug"],"created":"2026-09-24T06:19:04Z","updated":"2026-10-06T22:33:37Z","closed":"2026-10-06T22:33:37Z","reactions":1,"thumbs_up":1,"comments":1,"severity":"critical","severity_reasons":["label:security"],"topic":"self-host/headless","classes":["self-host/headless","auth/session","mcp/tools"],"cosmetic_ui":false,"summary":"Since v0.61.0 (#29117), /mcp auth fails for any MCP server whose authorization server publishes RFC 8414 metadata with an issuer but does not return iss in the authorization response: The same server authenticated fine on v0.56.0. This…","versions":["0.61.0","2.1","2.4"],"error_snippets":["x Failed to authenticate with MCP server '<name>': Missing \"iss\" parameter in authorization response per RFC 9207","if (expectedIssuer) {","// Fail-closed: if an issuer was expected, the response MUST include it","reject(new Error('Missing \"iss\" parameter in authorization response per RFC 9207'));","expectedIssuer"],"workaround":null,"fixed_in":null,"score":26.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29405","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29405,"title":"[Bug Report] Background tasks enter indefinite 'Forever Running' hang due to IPC pipe leaks & missing PID watchdog","url":"https://github.com/google-gemini/gemini-cli/issues/29405","state":"closed","state_reason":"not_planned","labels":["priority/p2","area/agent","status/bot-triaged","kind/bug","status/need-information"],"created":"2026-09-19T04:41:24Z","updated":"2026-10-15T01:45:27Z","closed":"2026-10-15T01:45:27Z","reactions":0,"thumbs_up":0,"comments":3,"severity":"high","severity_reasons":["title:breakage"],"topic":"always-on/daemon","classes":["always-on/daemon","crash/hang","self-host/headless","network"],"cosmetic_ui":false,"summary":"When agent tools execute commands asynchronously in background task mode (runcommand -> managetask), tasks frequently enter an indefinite \"Forever Running\" hang where task status remains permanently stuck on RUNNING. Even after the…","versions":[],"error_snippets":["), tasks frequently enter an indefinite \"Forever Running\" hang where task status remains permanently stuck on",", PowerShell ParserError on line 1, child process exited immediately, but task runner reported","event on all stdio streams, but pipe handles remain unclosed or unflushed, preventing","expect TTY or Ctrl+C. Without non-interactive environment defaults (","When agent tools execute commands asynchronously in background task mode (`run_command` -> `manage_task`), tasks frequently enter an indefinite \"Forever Running\" hang where task status remains permanently stuck on `RUNNI"],"workaround":null,"fixed_in":null,"score":24.2,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29424","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29424,"title":"bug: Node process hangs on session exit, preventing terminal from returning to shell prompt","url":"https://github.com/google-gemini/gemini-cli/issues/29424","state":"closed","state_reason":"not_planned","labels":["priority/p2","area/agent","status/bot-triaged","kind/bug","status/need-information","effort/large"],"created":"2026-09-20T12:01:43Z","updated":"2026-10-06T01:52:06Z","closed":"2026-10-06T01:52:06Z","reactions":0,"thumbs_up":0,"comments":4,"severity":"high","severity_reasons":["title:breakage"],"topic":"crash/hang","classes":["crash/hang","always-on/daemon","self-host/headless","auth/session","mcp/tools","network"],"cosmetic_ui":false,"summary":"When a Gemini CLI session is finished and displays the termination card (To resume this session: gemini --resume ), the underlying Node.js process hangs and does not exit. This leaves zombie terminal panes in terminal multiplexers like…","versions":["0.60.0","25.3.0"],"error_snippets":["process.exit(0)","When a Gemini CLI session is finished and displays the termination card (`To resume this session: gemini --resume `), the underlying Node.js process hangs and does not exit.","When the session is terminated, the CLI should clean up all of its active event loop handles, close connected MCP server client streams, and cleanly exit to return control back to the shell prompt.","3. Notice the session prints the exit card but hangs.","1. Explicitly close transport streams to connected MCP servers (like `google-workspace` and `chrome-devtools-mcp`)."],"workaround":null,"fixed_in":null,"score":22.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29309","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29309,"title":"bug(core): unbounded _execute recursion on sandbox_expansion_required can loop forever (scheduler.ts)","url":"https://github.com/google-gemini/gemini-cli/issues/29309","state":"closed","state_reason":"not_planned","labels":["priority/p2","area/core","kind/bug","status/manual-triage","status/need-information","effort/medium"],"created":"2026-09-13T13:07:16Z","updated":"2026-09-29T01:53:15Z","closed":"2026-09-29T01:53:15Z","reactions":0,"thumbs_up":0,"comments":5,"severity":"medium","severity_reasons":["class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon"],"cosmetic_ui":false,"summary":"packages/core/src/scheduler/scheduler.ts:927-934 recursively calls this.execute() when a tool returns sandboxexpansionrequired, with no counter or depth limit: A malicious or buggy tool returning sandboxexpansionrequired on every call…","versions":[],"error_snippets":["A malicious or buggy tool returning `sandbox_expansion_required` on every call recurses forever (stack growth / infinite loop). The surrounding `catch {}` falls through silently.","Bounded retry: iterative loop with `maxSandboxExpansions` (e.g. 2–3), then fail the call with an error and surface retry count in telemetry. Abort signal should also break the loop.","Fix direction: replace recursion with loop + counter, emit `sandbox_expansion_retry` telemetry, add regression test asserting 3rd consecutive request fails instead of recursing. Related hardening track #29214/#29216."],"workaround":null,"fixed_in":null,"score":22.2,"first_seen":"2026-10-20T09:28:14Z"},{"id":"google-gemini/gemini-cli#29588","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29588,"title":"Ink raw mode Ctrl-C unawaited cancellation causes hung interrupts, state rollbacks, and session poisoning (\"Requests ending with a model turn are not         supported\")","url":"https://github.com/google-gemini/gemini-cli/issues/29588","state":"closed","state_reason":"completed","labels":["priority/p1","area/core","status/bot-triaged","kind/bug","effort/medium"],"created":"2026-10-01T02:38:59Z","updated":"2026-10-13T20:02:43Z","closed":"2026-10-13T18:48:55Z","reactions":0,"thumbs_up":0,"comments":3,"severity":"high","severity_reasons":["label:p1"],"topic":"crash/hang","classes":["crash/hang","auth/session"],"cosmetic_ui":false,"summary":"[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT Root causes: interactiveCli captures 0x03 via Ink keybindings with exitOnCtrlC: false and calls void…","versions":["0.62.0","533.7"],"error_snippets":["[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT"],"workaround":null,"fixed_in":null,"score":21.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"google-gemini/gemini-cli#29594","harness":"gemini-cli","harness_name":"Gemini CLI","repo":"google-gemini/gemini-cli","number":29594,"title":"bug(tools): GoogleSearch tool hangs indefinitely in \"Thinking...\" state without timeout","url":"https://github.com/google-gemini/gemini-cli/issues/29594","state":"closed","state_reason":"completed","labels":["priority/p1","area/agent","status/bot-triaged","kind/bug"],"created":"2026-10-01T22:35:14Z","updated":"2026-10-14T05:45:56Z","closed":"2026-10-14T05:45:56Z","reactions":0,"thumbs_up":0,"comments":2,"severity":"high","severity_reasons":["label:p1","title:breakage"],"topic":"crash/hang","classes":["crash/hang","network"],"cosmetic_ui":false,"summary":"When the agent invokes the built-in GoogleSearch tool, the CLI frequently gets stuck in an infinite Thinking... state. The tool execution never times out, never throws an error, and never yields control back to the prompt, keeping the…","versions":["0.61.0"],"error_snippets":["│ GCP Project gemini-enterprise-sec-dx │","ToolExecutionError: Request timed out","to enter the interactive CLI, then run the","immediately aborts the hang, confirming that the terminal event loop is responsive, but the underlying","tool execution promise is left unresolved indefinitely without an"],"workaround":null,"fixed_in":null,"score":21.3,"first_seen":"2026-10-19T18:38:33Z"}]}