Summary
Plugin and marketplace management is currently fully manual: the user must memorize and type the full owner/repo (and for marketplaces, the marketplace name + plugin name) with no autocomplete, no interactive picker, and no list-based selection — even when the CLI clearly already has the relevant list available.
Affected surfaces
Expected
When invoked without arguments, these commands should drop into an interactive picker (similar to existing model/session pickers) backed by:
- For
install: the marketplace catalog the CLI already has cached
- For
enable/disable: the list of currently installed plugins
- For
browse <marketplace> → install: the plugin list already on screen — let the user arrow + Enter
Related
Why this matters
The current flow assumes the user has the full plugin coordinate memorized, which is fine for power users but defeats the discoverability point of having a marketplace at all.
Summary
Plugin and marketplace management is currently fully manual: the user must memorize and type the full
owner/repo(and for marketplaces, the marketplace name + plugin name) with no autocomplete, no interactive picker, and no list-based selection — even when the CLI clearly already has the relevant list available.Affected surfaces
copilot plugin install <owner/repo>— no tab-complete, no fuzzy pickercopilot plugin marketplace install <name>— samecopilot plugin marketplace browse <marketplace>— lists plugins but doesn't let you select one to install from the listcopilot plugin enable/disable(see Feature Request: Allow toggling plugins enabled/disabled #2714, Feature Request: --disable-plugin flag for per-session plugin control #3452) would have the same UX problemExpected
When invoked without arguments, these commands should drop into an interactive picker (similar to existing model/session pickers) backed by:
install: the marketplace catalog the CLI already has cachedenable/disable: the list of currently installed pluginsbrowse <marketplace>→install: the plugin list already on screen — let the user arrow + EnterRelated
Why this matters
The current flow assumes the user has the full plugin coordinate memorized, which is fine for power users but defeats the discoverability point of having a marketplace at all.