[feat]: Add `/extensions restart` command #12739

jakemac53 · 2025-11-07T21:57:36Z

Summary

Now that we have all extension reloading features working, this adds an /extensions restart command to explicitly restart extensions.

This command exists currently without opting into the extension reloading experiment - so that experiment just makes it automatic, but there is a way to restart extensions generally without opting in to anything.

Details

Also adds an event for the extensions update state reducer to update the "(updated, needs restart)" message for extensions after they have been updated.

Related Issues

Related to #11108

How to Validate

Update an extension and then restart it - you should see all the new features and also if you do /extensions list you should see its updated state is now green.

Pre-Merge Checklist

gemini-code-assist · 2025-11-07T21:57:52Z

Summary of Changes

Hello @jakemac53, 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 /extensions restart command, empowering users to manually refresh the state of their extensions. This functionality is available regardless of whether the automatic extension reloading experiment is active, offering a consistent method for applying updates or resolving issues. The change also includes updates to the extension state management, ensuring the user interface accurately reflects when an extension has been successfully restarted.

Highlights

New /extensions restart Command: Introduced a new command to explicitly restart extensions, allowing users to refresh extension states manually.
Independent of Auto-Reloading: This command functions even when automatic extension reloading is not enabled, providing a universal way to restart extensions.
UI State Update: Implemented a new RESTARTED event to update the UI, changing an extension's status from "updated, needs restart" to "updated" after a successful restart.

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.

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-code-assist

Code Review

This pull request introduces a new /extensions restart command, which is a valuable addition for managing extensions. The implementation is solid and includes comprehensive tests. I've identified one high-severity issue related to user feedback when no extensions match the restart criteria, which could lead to confusion. Addressing this will improve the user experience of the new command.

packages/cli/src/ui/commands/extensionsCommand.ts

github-actions · 2025-11-07T22:00:51Z

Size Change: +3.89 kB (+0.02%)

Total Size: 20.5 MB

Filename	Size	Change
`./bundle/gemini.js`	20.4 MB	+3.89 kB (+0.02%)

ℹ️ View Unchanged

Filename	Size
`./bundle/sandbox-macos-permissive-closed.sb`	1.03 kB
`./bundle/sandbox-macos-permissive-open.sb`	890 B
`./bundle/sandbox-macos-permissive-proxied.sb`	1.31 kB
`./bundle/sandbox-macos-restrictive-closed.sb`	3.29 kB
`./bundle/sandbox-macos-restrictive-open.sb`	3.36 kB
`./bundle/sandbox-macos-restrictive-proxied.sb`	3.56 kB

_{compressed-size-action}

jacob314 · 2025-11-07T22:15:39Z

LGTM! The implementation of /extensions restart is solid.

One minor suggestion for UX improvement:

In packages/cli/src/ui/commands/extensionsCommand.ts, if a user provides an invalid extension name, it seems it will just be silently ignored. It might be helpful to warn the user if any of the specified extensions were not found or not active.

jacob314 · 2025-11-07T22:21:46Z

packages/cli/src/ui/commands/extensionsCommand.ts

+
+  context.ui.addItem(
+    {
+      type: MessageType.INFO,


group the messages together. seeing two info icons here is ugly.

or tweak so the info icon isn't used.

This is what it looks like now PTAL

jacob314

Approved once the multiple info messages are cleaned up and there is a clearer error for invalid extension names.

…s the primary color and remove icon from second one

jakemac53 · 2025-11-07T23:01:20Z

Note that this should also be very useful when working locally on a linked extension - you can edit the main repo and then restart the extension to see your changes.

jacob314 · 2025-11-07T23:15:20Z

packages/cli/src/ui/commands/extensionsCommand.ts

+    const infoItem: HistoryItemInfo = {
+      type: MessageType.INFO,
+      text: `${extensionsToRestart.length} extension${s} restarted successfully.`,
+      icon: '  ',


'. ' is not an icon. make the api clearer or at least defined a constant like OMIT_ICON

jacob314

UI looks much more polished with these updates. Thanks for the fixes.

jakemac53 added 2 commits November 7, 2025 21:41

add /extensions restart command

31168d5

add tests

15bddee

jakemac53 requested a review from a team as a code owner November 7, 2025 21:57

gemini-code-assist bot reviewed Nov 7, 2025

View reviewed changes

packages/cli/src/ui/commands/extensionsCommand.ts Outdated Show resolved Hide resolved

gemini review comments

5f75fb0

jakemac53 requested a review from jacob314 November 7, 2025 22:07

jacob314 reviewed Nov 7, 2025

View reviewed changes

jakemac53 added 2 commits November 7, 2025 22:32

Add warning if some extensions are not found or active

fb37ae5

allow info messages to have custom colors and icons, make the message…

bdfcea5

…s the primary color and remove icon from second one

jakemac53 enabled auto-merge November 7, 2025 23:01

jacob314 reviewed Nov 7, 2025

View reviewed changes

jacob314 approved these changes Nov 7, 2025

View reviewed changes

jakemac53 added this pull request to the merge queue Nov 7, 2025

Merged via the queue into main with commit bafbcbb Nov 7, 2025
22 checks passed

jakemac53 deleted the extensions-restart-command branch November 7, 2025 23:28

jakemac53 mentioned this pull request Nov 7, 2025

[cleanup] rename info message property 'icon' to 'prefix' #12743

Merged

18 tasks

thacio added a commit to thacio/auditaria that referenced this pull request Nov 8, 2025

Merge Commit 'bafbcbb': [feat]: Add \ command (google-gemini#12739)

471d1ee

jackwotherspoon pushed a commit that referenced this pull request Nov 19, 2025

[feat]: Add /extensions restart command (#12739)

5b54c7b

danpalmer pushed a commit to danpalmer/gemini-cli that referenced this pull request Nov 29, 2025

[feat]: Add /extensions restart command (google-gemini#12739)

3369a25

[feat]: Add /extensions restart command #12739

[feat]: Add /extensions restart command #12739

Uh oh!

Conversation

jakemac53 commented Nov 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Details

Related Issues

How to Validate

Pre-Merge Checklist

Uh oh!

gemini-code-assist bot commented Nov 7, 2025

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

github-actions bot commented Nov 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jacob314 commented Nov 7, 2025

Uh oh!

jacob314 Nov 7, 2025

Choose a reason for hiding this comment

Uh oh!

jacob314 Nov 7, 2025

Choose a reason for hiding this comment

Uh oh!

jakemac53 Nov 7, 2025

Choose a reason for hiding this comment

Uh oh!

jacob314 left a comment

Choose a reason for hiding this comment

Uh oh!

jakemac53 commented Nov 7, 2025

Uh oh!

jacob314 Nov 7, 2025

Choose a reason for hiding this comment

Uh oh!

jacob314 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

[feat]: Add `/extensions restart` command #12739

[feat]: Add `/extensions restart` command #12739

jakemac53 commented Nov 7, 2025 •

edited

Loading

github-actions bot commented Nov 7, 2025 •

edited

Loading