github / github/copilot-cli

Subagents cannot access installed skills that are available to the main agent

Abierto
#4,708 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

area:agents area:plugins
Lenguaje dominante
Shell
Estrellas
11.2k
Forks
1.9k
Merge medio
14 h 16 min
PR fusionados (30 d)
6

Descripción

Describe the bug

Subagents cannot access installed skills that are available to the main agent

Describe the bug

In GitHub Copilot CLI 1.0.82, a main agent can discover and use skills installed through .copilot/installed-plugins. However, a subagent spawned by that main agent cannot access the same skills.

Instead of invoking the installed skill, the subagent attempts to search for the skill in the current workspace. This fails when the skill is provided by an installed plugin rather than stored in the repository.

This behavior appears to be a regression. The same workflow worked approximately two weeks ago: subagents had access to the same installed skills as the main agent.

Actual behavior

  • The main agent can retrieve and use an installed skill successfully.
  • A subagent spawned by that agent cannot retrieve the same skill.
  • The subagent searches the workspace for the skill instead of resolving it from the installed skills/plugins.

Environment

  • GitHub Copilot CLI version: 1.0.82
  • Skill source: installed plugins under .copilot/installed-plugins
  • Regression window: worked approximately two weeks ago

Why this matters

This breaks workflows where a coordinator agent delegates specialized work to subagents. The parent agent can access the relevant installed skills, but the workers cannot, which makes skill-based orchestration unreliable and forces users to duplicate skill instructions in the repository or pass them manually in prompts.

Requested fix

Please ensure that subagents inherit, or are otherwise given access to, the same installed skills as their parent/main agent. At a minimum, skills from the parent's installed plugin set should be discoverable and invocable by its subagents.

If full inheritance is intentionally not supported, please document the intended scope rules and provide a supported mechanism for declaring skills that a subagent requires.

Affected version

1.0.82

Steps to reproduce the behavior
  1. Install a Copilot plugin that provides one or more skills.
  2. Verify that the main Copilot CLI agent can discover and invoke one of those installed skills.
  3. Ask the main agent to spawn a subagent and explicitly instruct the subagent to use the same skill.
  4. Observe that the subagent tries to locate the skill in the repository workspace instead of resolving it from the installed plugin.
  5. The subagent therefore cannot invoke the skill that is available to the main agent.
Expected behavior

A subagent should receive access to the same installed skills that are available to its parent/main agent, including skills supplied through .copilot/installed-plugins.

When instructed to use a named skill, the subagent should discover and invoke that installed skill rather than searching the workspace for files or instructions with a matching name.

Additional context

No response

Guía de contribución

Abrir la guía de contribución

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.

Línea de trabajo

Reproduce el flujo de trabajo con un plugin instalado bajo .copilot/installed-plugins y compara después el descubrimiento de skills del agente principal y de un subagente generado. Traza cómo se pasa al subagente el conjunto de skills instalados del agente padre; se considera terminado cuando el subagente descubre e invoca el mismo skill instalado en lugar de buscar en el workspace.

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

Evaluación

Stack tecnológico
shell
Área
cli
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Activo
Claridad
Bastante claro
Aptitud para principiantes
48/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.