Report the resolved definition path (and content hash) for each custom agent
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/copilot-cli
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/copilot-cli#4932 ·
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github/copilot-cli#4909 ·
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
github/copilot-cli#4906 ·
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/copilot-cli#4848 ·
-
area:agents area:mcp
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/copilot-cli#4729 ·
All issues in github/copilot-cli
Similar issues
-
Bob Shell support Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
tooling
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
openSUSE/python-rpm-macros#219 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YunoHost-Apps/adguardhome_ynh#258 ·
-
steam-short-session-tracker: incorrect registry backup path resets settings during automatic repair Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ValveSoftware/SteamOS#2829 ·