Report the resolved definition path (and content hash) for each custom agent

Offen

#4,956 erstellt am 23.9.2026 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit: 3/5
Geschätzter Aufwand: 1-2 Tage
Anfängerfreundlichkeit: 65/100

Issue-Typ: Feature
Klarheit: Klar beschrieben
Aktivitätsstatus: Aktiv
Tech-Stack: shell
Bereich: cli, security

Rechercherichtung

Look for where custom agents are loaded and the session.custom_agents_updated event is emitted. The code likely resides in the agent resolution logic, possibly in a file like src/agent/loader.js or similar. Start by searching for 'custom_agents_updated' and 'tools_available' in the codebase. Understand how agent definitions are resolved from multiple sources (repo, user, plugin, --add-dir). Add the absolute file path and a SHA-256 hash of the file content to the agent entry. Verify the change by running the CLI with a custom agent and checking the debug log or event output.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

triage

Describe the feature or problem you'd like to solve

session.custom_agents_updated reports source: "project" for an agent, but not which file it came from. When several definitions could supply an agent ID (repo, user, plugin, --add-dir), the caller can't confirm which one actually loaded. Nor can it confirm that the loaded file is the one it reviewed. This matters for teams that review agent definitions before trusting an automated run.

Proposed solution

Add the resolved definition's absolute path and a content hash (for example, SHA-256) to each agent entry in session.custom_agents_updated. The same data could go in the debug log next to tools_available.

Example prompts or workflows

A pipeline runs copilot --agent implementer -p .... Before trusting the run, it checks that implementer resolved to .github/agents/implementer.agent.md with the reviewed hash. If a same-ID definition elsewhere took precedence, the pipeline refuses the run.

Additional context

Copilot CLI 1.0.87-0, Windows. The only read-back we have today is tools_available. It shows what an agent was offered, but not why.

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

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

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

Mehr aus github/copilot-cli

Built-in skill `github-pr-media` cannot run: `gh auth token` is empty in a cloud agent session, and the endpoint rejects `Bearer` Offen

triage

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100

github/copilot-cli#4932 · Erstellt am 22.9.2026
/ide finds no workspaces under the CLI sandbox: kill(pid,0) EPERM misread as a dead process Offen

triage

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100

github/copilot-cli#4909 · Erstellt am 19.9.2026
MCP OAuth: DCR sends client_name "copilot-cli", rejected with 403 by Figma's allowlist (expects "GitHub Copilot CLI") Offen

triage

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100

github/copilot-cli#4906 · Erstellt am 18.9.2026
/feedback: “Save feedback bundle” is easily mistaken for submitting feedback Offen

triage

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100

github/copilot-cli#4848 · Erstellt am 15.9.2026
Built-in research agent tells subagents to call unavailable github/get_me tool Offen

area:agents area:mcp

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100

github/copilot-cli#4729 · Erstellt am 04.9.2026

Alle Issues in github/copilot-cli