experiment

[chrstnb]

Summary

Details

Screen.Recording.2026-01-07.at.4.51.14.PM.mov

Related Issues

How to Validate

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

[gemini-code-assist]

Summary of Changes

Hello @chrstnb, 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 significantly enhances the CLI's extension management system by introducing dynamic extension loading capabilities. It provides a new experimental setting and CLI argument to enable this feature, allowing extensions to be activated or deactivated on the fly. Furthermore, it integrates a new ActivateExtensionTool for agents, enabling them to dynamically utilize extensions as needed. The changes also improve extension metadata handling by allowing descriptions to be loaded from package.json and refine the extension enablement/disablement process with explicit scoping.

Highlights

• Dynamic Extension Loading: Introduced a new experimental setting dynamicExtensionLoading and a CLI argument --enable-extension-reloading to control the dynamic activation and deactivation of extensions during a session.
• ActivateExtensionTool: Added a new tool that allows agents to programmatically activate disabled extensions, enhancing the agent's capabilities.
• Extension Description Loading: Extensions can now automatically load their descriptions from their package.json file if not explicitly provided in their configuration.
• Enhanced Extension Management: The ExtensionLoader now includes enableExtension and disableExtension methods that support different ExtensionScope values, allowing for more granular control over extension lifecycle.
• System Prompt Integration: The core system prompt for agents now conditionally includes a list of available disabled extensions, providing context for the ActivateExtensionTool when dynamicExtensionLoading is enabled.

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

Code Review

This pull request introduces an experimental feature for dynamic extension loading, which allows the model to activate extensions on-the-fly during a session. The changes are comprehensive, touching both the CLI and core packages to support this new functionality. Key additions include new settings for enabling the feature, an activate_extension tool for the model, and updates to the system prompt to inform the model about available extensions. The implementation also thoughtfully adds the ability to read an extension's description from its package.json. Overall, the changes are well-implemented and include necessary tests. My review includes a couple of suggestions to improve type safety and address a potential design layering issue, which will enhance long-term maintainability.

[github-actions]

Size Change: +8.38 kB (+0.04%)

Total Size: 22.3 MB

Filename	Size	Change
./bundle/gemini.js	22.3 MB	+8.38 kB (+0.04%)

ℹ️ 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}