plugin marketplace add reports success but registration is not persisted (browse immediately fails with 'not found')
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Shell
- Sterne
- 11.2k
- Forks
- 1.9k
- Ø Merge
- 14 Std. 16 Min.
- Gemergte PRs (30 T.)
- 6
Beschreibung
Describe the bug
copilot plugin marketplace add reports success, but the marketplace registration is never persisted anywhere on disk. A subsequent copilot plugin marketplace list (even in the same command chain / immediately after) does not show the newly added marketplace, and copilot plugin marketplace browse <name> fails with Marketplace "<name>" not found.
This reproduces both for a local directory marketplace and a GitHub-hosted marketplace, so it does not appear to be specific to local-path or git-auth handling (unlike #4103).
Environment
- GitHub Copilot CLI: 1.0.74 (latest at time of filing)
- OS: Windows 11 (PowerShell 7 / native)
- Marketplace manifest: valid
.claude-plugin/marketplace.jsonat repo root (per docs, this location is supported)
Steps to reproduce
# Local directory marketplace with a valid .claude-plugin/marketplace.json
copilot plugin marketplace add C:\Git\Agentic
copilot plugin marketplace list
copilot plugin marketplace browse company-skills
# Also reproduces with a GitHub-hosted marketplace
copilot plugin marketplace add anthropics/claude-code
copilot plugin marketplace list
Actual result
Marketplace "company-skills" added successfully.
...but copilot plugin marketplace list afterward only shows the two built-in marketplaces:
Included with GitHub Copilot:
- copilot-plugins (GitHub: github/copilot-plugins)
- awesome-copilot (GitHub: github/awesome-copilot)
And:
Fetching plugins from marketplace "company-skills"...
Failed to browse marketplace: Error: Marketplace "company-skills" not found
Confirmed via Compare-Object of a full recursive file listing under ~/.copilot, %LOCALAPPDATA%, and %APPDATA% before/after running add — no files are created or modified anywhere as a result of the command, despite the CLI reporting success.
Expected result
copilot plugin marketplace add should persist the marketplace registration so that a subsequent list/browse in a new process reflects it, matching the documented behavior in https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/plugins-finding-installing.
Additional context
Possibly related to #3403 (~/.copilot/config.json being overwritten/reset on session start, dropping previously-written keys like hooks) — if marketplace registrations are also expected to live in config.json, the same overwrite-on-start bug could explain why the registration never survives past the single add invocation.
--- This report was investigated and drafted by GitHub Copilot CLI (Claude Sonnet 5).
Additional notes: name of marketplace changed for to company-skills. Additional details
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne bei den CLI-Einstiegspunkten für plugin marketplace add, list und browse und untersuche anschließend den Persistenzort, einschließlich des möglichen Pfads ~/.copilot/config.json und des Manifests .claude-plugin/marketplace.json. Reproduziere das Verhalten sowohl mit Beispielen aus dem lokalen Verzeichnis als auch mit auf GitHub gehosteten Beispielen; abgeschlossen ist die Aufgabe, wenn die Registrierung einen neuen Prozess überlebt und in list und browse erscheint.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- github, powershell, shell
- Bereich
- cli
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 52/100