Issue Station
Sign In
Tools hereToolbox

gemini-cli - ✅(Solved) Fix Gemini Extension can't be installed from ssh repository [1 pull requests, 1 comments, 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#26273•Fetched 2026-05-01 05:52:54
View on GitHub
Comments
1
Participants
1
Timeline
3
Reactions
0
Author
danielmundidanielmundi
Participants
danielmundidanielmundi
Timeline (top)
commented ×1cross-referenced ×1labeled ×1

Error Message

Error:

Fix Action

Fixed

PR fix notes

PR #26274: fix(cli): allow installing extensions from ssh repo

Description (problem / solution / changelog)

Current code doesn't allow installing extensios from an URL with ssh:// prefix. Update the filter to include this prefix option.

Summary

Allow installing extensions from Git repositories that have the URL using the ssh:// prefix.

Details

Some repositories don't accept the github and gitlab URL patterns and instead use the URL as ssh://url.domain.com. It should be possible to install from those Git repositories as well.

Related Issues

Fixes #26273

How to Validate

Execute command to install extension using an URL with ssh:// prefix, such as:

gemini extensions install ssh://url.domain.com

Pre-Merge Checklist

  • Updated relevant documentation and README (if needed)
  • Added/updated tests (if needed)
  • Noted breaking changes (if any)
  • Validated on required platforms/methods:
    • MacOS
      • npm run
      • npx
      • Docker
      • Podman
      • Seatbelt
    • Windows
      • npm run
      • npx
      • Docker
    • Linux
      • npm run
      • npx
      • Docker

Changed files

  • packages/cli/src/config/extension-manager.ts (modified, +2/-1)

Code Example

Error:

---

### What did you expect to happen?

The extension should be downloaded and installed, since the ssh key is already available.

### Client information

<details>
<summary>Client Information</summary>
RAW_BUFFERClick to expand / collapse

What happened?

Trying to install an extension from a repository that uses an SSH URL, the extension is not installed.

Command: gemini extensions install ssh://url.domain.com

Error: Install source not found.

What did you expect to happen?

The extension should be downloaded and installed, since the ssh key is already available.

Client information

<details> <summary>Client Information</summary> 
> /about
About Gemini CLI

CLI Version: 0.40.0
Git Commit: 3d5bdc052
Model: Auto (Gemini 3)
Sandbox: no sandbox
OS: linux
Auth Method: Signed in with Google
Tier: Gemini Code Assist Enterprise
</details>

Login information

Google Account

Anything else we need to know?

Currently, the installation process filters the allowed URL, which doesn't include URLs with ssh:// prefix (on packages/cli/src/config/extension-manager.ts). Is there any reason why ssh:// prefix is not allowed? Can we enable it as well?

extent analysis

TL;DR

The issue is likely due to the ssh:// prefix not being allowed in the installation process, and a potential fix is to modify the extension-manager.ts file to include ssh:// in the allowed URLs.

Guidance

  • The error message "Install source not found" suggests that the installation process is unable to recognize the SSH URL, which is likely due to the filtering of allowed URLs in extension-manager.ts.
  • To verify this, check the extension-manager.ts file to confirm that ssh:// is not included in the list of allowed URL prefixes.
  • Modify the extension-manager.ts file to include ssh:// in the allowed URLs, or consider using a different URL prefix that is already allowed.
  • Test the installation process again after making the modification to see if it resolves the issue.

Example

No code snippet is provided as it would require modifying the extension-manager.ts file, which is not explicitly shown in the issue.

Notes

The solution assumes that modifying the extension-manager.ts file is feasible and allowed. If this is not the case, alternative solutions may need to be explored.

Recommendation

Apply workaround: Modify the extension-manager.ts file to include ssh:// in the allowed URLs, as this is the most direct way to address the issue based on the provided information.

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…
#installation#latency issue#model loading#dependency error#configuration error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING