Issue Station
Sign In
Tools hereToolbox

gemini-cli - ✅(Solved) Fix gemini extensions install shows confusing errors/warnings that may deter new users [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#24966•Fetched 2026-04-09 08:16:42
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
husenzhanghusenzhang
Participants
husenzhanghusenzhang
Timeline (top)
labeled ×3unlabeled ×1

When installing an extension from a GitHub URL, gemini extensions install displays multiple error/warning messages that are not user-actionable and can confuse non-technical users. These should be suppressed or downgraded to debug-level logs.

Error Message

Error downloading github release for https://github.com/<org>/<repo>.git with the following error: Failed to fetch release data for <org>/<repo> at tag undefined: Request failed with status code 404.

Root Cause

When installing an extension from a GitHub URL, gemini extensions install displays multiple error/warning messages that are not user-actionable and can confuse non-technical users. These should be suppressed or downgraded to debug-level logs.

PR fix notes

PR #25410: fix(extensions): suppress non-actionable errors during extension install

Description (problem / solution / changelog)

Summary

  • Silently fall through to git clone when GitHub release download fails for plain git URL installs, instead of showing an error prompt
  • Downgrade keychain fallback messages from debugLogger.log() to debugLogger.debug() so they are hidden unless --debug is enabled Fixes #24966

Changed files

  • packages/cli/src/config/extension-manager.ts (modified, +4/-4)
  • packages/core/src/services/keychainService.ts (modified, +7/-4)

Code Example

gemini extensions install https://github.com/<org>/<repo>.git

---

Error downloading github release for https://github.com/<org>/<repo>.git
with the following error: Failed to fetch release data for <org>/<repo>
at tag undefined: Request failed with status code 404.

---

Keychain initialization encountered an error: Cannot find package 'keytar'...
Using FileKeychain fallback for secure storage.
RAW_BUFFERClick to expand / collapse

Description

When installing an extension from a GitHub URL, gemini extensions install displays multiple error/warning messages that are not user-actionable and can confuse non-technical users. These should be suppressed or downgraded to debug-level logs.

Steps to Reproduce

  1. Create a valid Gemini CLI extension with gemini-extension.json at the repo root
  2. Push to a public GitHub repo
  3. Run: 
    gemini extensions install https://github.com/<org>/<repo>.git

Observed Behavior

Two non-actionable messages appear:

1. GitHub release error (even with a valid release tag):

Error downloading github release for https://github.com/<org>/<repo>.git
with the following error: Failed to fetch release data for <org>/<repo>
at tag undefined: Request failed with status code 404.

2. Keychain warning (macOS):

Keychain initialization encountered an error: Cannot find package 'keytar'...
Using FileKeychain fallback for secure storage.

Expected Behavior

  • The release data lookup should fail silently (or at debug level) if no matching tag is found -- extensions should not require GitHub releases to install
  • The keychain fallback should be transparent to the user -- it is an internal implementation detail

Impact

These messages create a poor first impression for new users installing extensions. Non-technical users may think the install failed when it actually succeeded.

Environment

  • macOS
  • Gemini CLI v0.34.x

extent analysis

TL;DR

Suppressing or downgrading non-actionable error messages during extension installation can improve the user experience.

Guidance

  • Review the Gemini CLI's logging configuration to determine if the error messages can be suppressed or downgraded to debug-level logs.
  • Consider modifying the gemini extensions install command to handle cases where no matching GitHub release tag is found, allowing it to fail silently or log at a debug level.
  • Investigate the Keychain initialization error to determine if the 'keytar' package is required, and if the fallback to FileKeychain can be made transparent to the user.
  • Update the Gemini CLI documentation to reflect the expected behavior and any potential workarounds for common issues.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The solution may require changes to the Gemini CLI's logging and error handling mechanisms, as well as potential updates to the Keychain initialization process.

Recommendation

Apply a workaround to suppress or downgrade non-actionable error messages, as upgrading to a fixed version is not mentioned in the issue. This will improve the user experience for non-technical users installing extensions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#serialization error#model compatibility#GPU setup#container setup#orchestration issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING