Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#4,708 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
shell
Bereich
cli

Rechercherichtung

Reproduziere den Workflow mit einem unter .copilot/installed-plugins installierten Plugin und vergleiche anschließend die Skill-Erkennung für den Hauptagenten und einen erzeugten Subagenten. Verfolge, wie der installierte Skill-Satz des übergeordneten Agenten an den Subagenten übergeben wird; abgeschlossen ist die Aufgabe, wenn der Subagent denselben installierten Skill erkennt und aufruft, anstatt den Workspace zu durchsuchen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area:agents area:plugins
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

Vorherrschende Sprache
Shell
Sterne
11.2k
Forks
1.9k
Ø Merge
17 Std. 6 Min.
Gemergte PRs (30 T.)
5

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus github/copilot-cli

Alle Issues in github/copilot-cli

Ähnliche Issues

Weitere Issues zu Shell/Bash

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.