@OrenMe My point of view is that the plugin reference is a packaging standard. To APM that's just another packaging format for agent primitives. Current thinking is that "apm install" should work with plugins too, and add them as dependencies in the manifest.

Thanks for the explanation @danielmeppiel
Makes a lot of sense although I assume it will be challenging to support multiple packaging formats

I really love this project challenge - I see strange governance models hacks emerging due to lack of such a tool
Example:

1. Creating single repo with all tools and pulling it as git sub module - and then needing to re wire the path settings cause it is not standard for copilot in vscode and cli
2. Creating single repo with all tools and then creating a vscode workspace and pulling there the products/apps repos and the tools repo and then re wiring the copilot paths as well - and this is even worse IMO then option 1 cause the workspace config cannot be git managed

So this project really allows governance, distribution and versioning management