Report the resolved definition path (and content hash) for each custom agent
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 65/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Shell
- Stelle
- 11.2k
- Fork
- 1.9k
- Merge medio
- 14h 16m
- PR unite (30g)
- 6
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di github/copilot-cli
-
triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
github/copilot-cli#4932 ·
-
triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
github/copilot-cli#4909 ·
-
triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
github/copilot-cli#4906 ·
-
triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
github/copilot-cli#4848 ·
-
area:agents area:mcp
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
github/copilot-cli#4729 ·
Tutte le issue di github/copilot-cli
Issue simili
-
Bob Shell support Apertaenhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
-
tooling
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
openSUSE/python-rpm-macros#219 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
YunoHost-Apps/adguardhome_ynh#258 ·
-
steam-short-session-tracker: incorrect registry backup path resets settings during automatic repair Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
ValveSoftware/SteamOS#2829 ·