Gemini CLI now supports extension settings that prompt users for required configuration during installation. Extension authors can define settings in their manifest (API keys, database credentials, URLs) which are then collected interactively, stored securely in the system keychain, and automatically provided to extensions. Users can manage settings post-installation with the `gemini extensions config` command, including workspace-specific overrides. The feature eliminates manual environment variable setup and reduces configuration errors.
Table of contents
A first-class experience for extension configurationPractical example: The AlloyDB extensionHow to define settings as an authorManaging settings with the config commandDebugging the configurationBest practices for extension settingsGet started today3 Comments
Sort: