Expose opaque plugin identities and ownership references on discovered contributions

Đang mở
  • Có gì không ổn?
#2,878 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
35/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
java
Lĩnh vực
backend-api-design

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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

Ngôn ngữ chính
Java
Star
10.7k
Fork
1.5k
Không có pull request nào được merge trong 30 ngày

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của github/copilot-sdk

Tất cả issue của github/copilot-sdk

Issue tương tự

Thêm issue về Java

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.