Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Agent plugin migration: gaps in package conversion, canvas discovery, and hook stdout guidance

オープン
  • 何か問題がありますか？
#10,551 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
54/100
issue の種類
ドキュメント
明瞭さ
おおむね明確
活発さ
活発
技術スタック
markdown
領域
documentation

調査の方向性

Start with docs/agent-customization/migrate-customizations.md, docs/agents/reference/agent-plugin-reference.md, and the hook input/output section in docs/agent-customization/hooks.md. Compare their current guidance with the three gaps described here; investigate the canvas discovery contract and its support status before documenting a migration path. Done means the docs give a package conversion checklist, clarify canvas extension discovery and support, and explain that subprocess stdout can corrupt hook responses.

索引モデルが issue の本文から書いたものです。

説明

Context

Migrating the 13 local plugins in microsoft/vscode-team-kit#47 exposed three documentation gaps for later editorial follow-up. The customization migration guide and plugin reference cover the core contracts, but these details required additional investigation.

1. Converting an existing plugin package

The reference describes the Agent Plugins 1.0 destination, but there is no end-to-end checklist for converting a legacy package. The missing connections include:

  • Moving the manifest to root plugin.json and declaring the canonical schema.
  • Moving client-specific components under com.github.copilot/, while retaining portable skills and MCP configuration at their standard locations.
  • Removing unsupported manifest metadata such as categories, status, maintainers, and evals, while retaining applicable catalog metadata in marketplace.json.
  • Updating relative references, tests, and version metadata, and avoiding duplicate active legacy components.
  • Validating the closed manifest schema separately from checking runtime discovery and execution.
2. SDK canvas extension discovery

The plugin reference's package layout does not cover SDK canvas extensions. During the session-timeline migration, we needed runtime-source investigation to establish that Agent Plugins packages discover them from com.github.copilot/extensions/ and that a manifest path does not redirect that discovery.

The documentation does not currently establish whether this packaging contract is supported, experimental, or intentionally outside the public authoring guidance. That leaves authors without a documented migration path for an existing canvas plugin.

3. Subprocess output can invalidate hook responses

The hook input/output guidance already says to keep diagnostics separate from the JSON response. A less obvious case is a dependency installer or other subprocess inheriting stdout: progress text can corrupt an otherwise correct hook response.

We encountered this risk in the shared dependency bootstrap and redirected installer output to stderr. The existing warning does not make clear that the one-response contract applies to the whole process tree, not just the hook's final JSON write. This can leave enforcement or context injection absent even when the script appears to complete successfully.

These are documentation follow-ups, not a request to change runtime behavior. CLI version differences and agent invocation naming are outside this issue's scope.

🤖 Posted by GitHub Copilot on Harald's behalf.

主要言語
Markdown
スター
6.7k
フォーク
5.8k
平均マージ
18時間 49分
マージ済み PR（30日）
116

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

microsoft/vscode-docs のほかの issue

microsoft/vscode-docs の issue をすべて見る

似ている issue

Documentation の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。