Add install as an option when extension is selected.

[DavidAPierce]

Summary

Within the extension explore feature, open up extension dialog on enter and support install

Related Issues

closes
https://github.com/google-gemini/maintainers-gemini-cli/issues/1402https://github.com/google-gemini/maintainers-gemini-cli/issues/1402

How to Validate

Set ```"experimental": {
"plan": true,
"extensionReloading": true,
"extensionRegistry": true
},

Then run /extensions explore and press enter on any of the uninstalled extensions to open the install dialogue.

## Pre-Merge Checklist

<!-- Check all that apply before requesting review or merging. -->

- [ ] 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
    - [x] npm run
    - [ ] npx
    - [ ] Docker

[gemini-cli]

Hi @DavidAPierce, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this.

We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines.

Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed.

Thank you for your understanding and for being a part of our community!

[gemini-code-assist]

Summary of Changes

Hello @DavidAPierce, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the /extensions explore command by integrating the ability to install extensions directly from the interactive registry view. Users can now select an uninstalled extension, and upon confirmation, the system will initiate its installation, streamlining the extension management workflow within the CLI.

Highlights

• Extension Installation: Enabled direct installation of extensions from the /extensions explore command by pressing Enter on a selected extension.
• UI Interaction: Implemented logic to automatically trigger the installation process and close the extension registry view upon selection.
• Test Coverage: Added new unit tests to ensure the correct behavior of the ExtensionRegistryView's onSelect and onClose handlers, verifying that installation is initiated and the component is removed.

Changelog

• packages/cli/src/ui/commands/extensionsCommand.test.ts
  • Added imports for ExtensionRegistryView and RegistryExtension types.
  • Included removeComponent in the mocked UI context for testing.
  • Introduced new test cases to verify that ExtensionRegistryView is rendered correctly when experimental.extensionRegistry is true.
  • Added tests to confirm that selecting an extension triggers the installAction and removeComponent is called.
• packages/cli/src/ui/commands/extensionsCommand.ts
  • Modified the onSelect handler for ExtensionRegistryView to call installAction with the selected extension's URL.
  • Ensured context.ui.removeComponent() is called after an extension is selected to close the view.
  • Changed debugLogger.debug to debugLogger.log for selected extension messages.
• packages/cli/src/ui/components/views/ExtensionRegistryView.tsx
  • Exported the ExtensionRegistryViewProps interface to allow its use in other modules, particularly for type-checking in tests.

Activity

• Validated on Linux using npm run.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

Size Change: +96 B (0%)

Total Size: 25.8 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	25.3 MB	+96 B (0%)
./bundle/node_modules/@google/gemini-cli-devtools/dist/client/main.js	221 kB	0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/_client-assets.js	227 kB	0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/index.js	11.5 kB	0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/types.js	132 B	0 B
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B
./bundle/sandbox-macos-strict-open.sb	4.82 kB	0 B
./bundle/sandbox-macos-strict-proxied.sb	5.02 kB	0 B

_{compressed-size-action}

[gemini-code-assist]

Code Review

This pull request adds the ability to install an extension directly from the extension explorer UI. The implementation correctly triggers the installation process when an uninstalled extension is selected. I've added one suggestion to improve the user experience by preventing an installation attempt on an already installed extension, which currently results in an error.