Expose opaque plugin identities and ownership references on discovered contributions

Abierto
  • ¿Algo no está bien?
#2,878 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java
Área
backend-api-design

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Java
Estrellas
10.7k
Forks
1.5k
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/copilot-sdk

Todos los issues de github/copilot-sdk

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.