feat: add extensionsExplore setting to enable extensions explore UI.

[sripasg]

Summary

add extensionsRegistry setting to enable extensions explore UI.
Run npm run schema:settings to update the json.

Related Issues

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

How to Validate

Built the plugin: npm run build:all
Checked types: tsc --noEmit locally via npm run typecheck
Verified tests: npm run test:ci -w @google/gemini-cli
Ran full validation: npm run preflight

Pre-Merge Checklist

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

[gemini-code-assist]

Summary of Changes

Hello @sripasg, 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 introduces a new configuration setting to control the visibility and functionality of an experimental extension registry explore UI. By adding this setting, users will have the option to enable or disable this feature, providing more granular control over the CLI's extension management capabilities.

Highlights

• New Setting Introduced: A new experimental setting, extensionRegistry, has been added to enable the extension registry explore UI.
• Schema Updates: The settingsSchema.ts and settings.schema.json files have been updated to include the definition for the new extensionRegistry setting.

Changelog

• packages/cli/src/config/settingsSchema.ts
  • Added a new extensionRegistry boolean setting with a label 'Extension Registry Explore UI' and marked as 'Experimental'.
  • Configured the setting to require a restart and default to false.
• schemas/settings.schema.json
  • Included the extensionRegistry property in the JSON schema, defining its title, description, and default value.
  • Added markdown description detailing its category, restart requirement, and default state.

Activity

• The author built the plugin using npm run build:all.
• Type checks were performed locally via tsc --noEmit.
• Tests were verified using npm run test:ci -w @google/gemini-cli.
• Full validation was run with npm run preflight.

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. ↩

[gemini-cli]

Hi @sripasg, 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]

Code Review

This pull request introduces a new experimental setting, extensionRegistry, to enable an extensions explore UI. The implementation is straightforward. The suggestion to rename the setting to extensionsExplore has been kept as it aligns with the pull request title and provides greater clarity on the setting's purpose, improving long-term maintainability and preventing potential confusion.

[github-actions]

Size Change: +286 B (0%)

Total Size: 23.9 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	23.9 MB	+286 B (0%)
./bundle/sandbox-macos-permissive-closed.sb	1.03 kB	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-closed.sb	3.29 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

_{compressed-size-action}