Expose opaque plugin identities and ownership references on discovered contributions

未關閉
  • 哪裡不對？
#2,878 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
35/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
java
領域
backend-api-design

研究方向

Start by locating the plugin inventory and discovery APIs for agents, skills, instructions, hooks, and MCP servers across the supported language SDKs, then read their existing provenance fields and tests. Define and document a consistent ownership reference that resolves in the matching global or session context, including ID lifetime and same-named plugins from different sources. Done means every contribution type and supported SDK follows the contract, with tests covering resolution and global/session behavior.

由索引模型根據 Issue 內容生成。

描述

Problem

VS Code needs to group SDK-discovered contributions under their owning plugins while leaving discovery and plugin lifecycle management to the SDK.

Please expose a common opaque plugin ID on plugin inventory entries and an owning-plugin reference on every plugin contribution: agents, skills, instructions, hooks, and MCP servers.

Without a shared ownership contract, consumers must infer relationships from names, parse contribution IDs, match filesystem paths, or scan plugin directories. Those approaches duplicate SDK responsibilities and can misattribute contributions when different plugins have the same name.

Proposed contract

  • Each plugin inventory entry exposes an opaque id.
  • Each plugin-owned contribution exposes an optional owning-plugin reference, for example pluginId, whose value matches an inventory entry's id.
  • Non-plugin contributions omit the reference.
  • Use the same identity contract across global discovery and session-scoped APIs wherever they refer to the same plugin instance.
  • Document the identity's scope and stability, including restarts, updates, and reinstallations. Distinguish same-named plugins from different marketplaces/direct sources and session-specific instances where necessary.
  • Document how contributions resolve to inventory entries in the corresponding context, including session-only, built-in, and managed plugins. Consumers should not need to reconstruct an identity from installation metadata.
  • Reuse or align existing provenance fields rather than introduce competing ownership identifiers.

Illustrative field names, not a required API shape:

const inventory = {
  plugins: [{ id: "opaque-plugin-id", name: "review-tools", enabled: true }]
};

const discovery = {
  agents: [{
    id: "opaque-agent-selection-id",
    name: "reviewer",
    pluginId: "opaque-plugin-id"
  }]
};

The agent's selection ID and the owning plugin's ID serve different purposes; callers must not parse either.

Expected consumer behavior

VS Code can join contribution results to inventory entries by the opaque plugin ID, present SDK-owned plugin groups, and use SDK-reported enablement. It does not scan plugin directories, parse manifests, match file paths, or implement another discovery mechanism.

Acceptance criteria

  • Ownership attribution is available consistently for agents, skills, instructions, hooks, and MCP servers.
  • Every returned plugin reference can be resolved using the documented inventory API/context.
  • Same-named plugins from different sources remain distinguishable.
  • Global/session behavior and ID lifetime are documented and covered by tests.
  • All supported language SDKs expose the contract.

Scope

This requests ownership attribution, not filesystem roots, enablement migration, or a change to policy precedence.

Whether APIs should also enumerate contributions of disabled plugins is a separate capability question. This issue does not require scanning those contributions on the client or assume active discovery returns them.

Related VS Code work: https://github.com/microsoft/vscode/issues/343342

主要語言
Java
星號
10.7k
分支
1.5k
30 天內沒有已合併 PR

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

github/copilot-sdk 的其他 Issue

查看 github/copilot-sdk 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。