Open
Description
Summary
When a newer version of Dev Proxy is installed and started with a configuration file from an older version, Dev Proxy Toolkit should warn the user that the config is for a different version than what's installed. The Toolkit should:
- Detect the current Dev Proxy version.
- Find all Dev Proxy config files in the workspace.
- Compare their versions to the installed Dev Proxy version.
- Suggest a one-click upgrade to the current Dev Proxy version if necessary.
Suggested Implementation
One way to solve this could be to use GitHub Copilot Chat with the Dev Proxy MCP server (which has access to the latest schemas, etc.) and let the LLM generate the necessary config upgrades. The approach would:
- Send a preconfigured prompt to Copilot Chat.
- Pre-select the MCP tools.
- Select Claude 4 as the model.
Action Items:
- Investigate if Copilot Chat can be programmatically invoked from the Toolkit with pre-selected tools and model, via the VSCode APIs.
- Implement detection and comparison logic for Dev Proxy/config versions.
- Add UI for warning and one-click upgrade.
Questions:
- Is it possible to programmatically configure Copilot Chat in this way through VSCode APIs?
- Are there edge cases (e.g. breaking config changes) that should be handled?
This feature would help keep config files up to date and avoid runtime issues due to version mismatches.