What would you like to be added?
Currently, we ask for consent when you install an extension:
chrstn-mac:gemini-cli chrstn$ gemini extensions install https://github.com/gemini-cli-extensions/alloydb
Extensions may introduce unexpected behavior.
Ensure you have investigated the extension source and trust the author.
This extension will run the following MCP servers:
* AlloyDB Admin (local): /var/folders/hp/ncqqhq914xx5hfv1__pthktw00fmch/T/gemini-extensionsNDhQc/toolbox --prebuilt alloydb-postgres-admin --stdio
* AlloyDB (local): /var/folders/hp/ncqqhq914xx5hfv1__pthktw00fmch/T/gemini-extensionsNDhQc/toolbox --prebuilt alloydb-postgres --stdio
This extension will append info to your gemini.md context using ALLOYDB.md
Do you want to continue? [Y/n]:
Extension "alloydb" installed successfully and enabled.
When you update an extension (manually or auto-update), we should do something similar, perhaps by comparing the old and new extension to detect what changed.
Why is this needed?
The consent flow is a security measure and we introduce a vulnerability by allowing extensions to be updated without requesting consent for new behavior.
Additional context
No response
What would you like to be added?
Currently, we ask for consent when you install an extension:
When you update an extension (manually or auto-update), we should do something similar, perhaps by comparing the old and new extension to detect what changed.
Why is this needed?
The consent flow is a security measure and we introduce a vulnerability by allowing extensions to be updated without requesting consent for new behavior.
Additional context
No response