Deprecating support for .vscode/mcp.json is a terrible idea
- Langage dominant
- Shell
- Étoiles
- 11.2k
- Forks
- 1.9k
- Merge moyen
- 14 h 16 min
- PR mergées (30 j)
- 6
Description
### Describe the bug
I just tried using the CLI and hit this:
[Deprecation of vscode mcp json](https://docs.github.com/en/copilot/reference/copilot-cli-reference/cli-command-reference#migrating-from-vscodemcpjson)
I use that mcp.json all the time in VS code. Now I need two mcp.json files?
### Affected version
_No response_
### Steps to reproduce the behavior
_No response_
### Expected behavior
_No response_
### Additional context
_No response_
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Start with the linked migration guidance and review how the CLI currently handles .vscode/mcp.json versus its replacement configuration. Confirm the intended compatibility behavior and identify the relevant configuration discovery and documentation entry points. Done means the issue has a decided, tested approach that avoids requiring duplicate mcp.json files.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- shell, vscode
- Domaine
- cli, developer-experience
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- Calme
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100