Add user-level custom agent configuration
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github
- Domain
- cli, documentation
Research direction
Open the affected GitHub Docs article, especially the “Where you can configure custom agents” section. Add the user level and document the $HOME/.copilot/agents/CUSTOM-AGENT-NAME.md location, then verify the rendered list and wording explain that it applies across repositories.
Written by the indexing model from the issue text.
Description
Code of Conduct
- I have read and agree to the GitHub Docs project's Code of Conduct
What article on docs.github.com is affected?
What part(s) of the article would you like to see updated?
The Where you can configure custom agents section currently documents three configuration levels:
-
Repository level
-
Organization level
-
Enterprise level
Add the user level to this list.
For GitHub Copilot CLI, custom agents can also be configured in the user's home directory using:
$HOME/.copilot/agents/CUSTOM-AGENT-NAME.md
This provides user-level instructions that apply across repositories.
Additional information
A user-level agent is useful when a developer wants the same custom agent and instructions to be available across repositories without modifying each repository
- Dominant language
- TypeScript
- Stars
- 21k
- Forks
- 69k
- Avg merge
- 8h 53m
- Merged PRs (30d)
- 114
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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/docs
-
GPT 6.1 SolPossibly taken A pull request linked to this issue is open or already merged. Opencontent triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
content driver persona triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Clarify vars context availability in composite actionsPossibly taken A pull request linked to this issue is open or already merged. Opencontent triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
github/docs#46232 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Dependabot docs disagree on when the ecosystem label is added, and on its name (github-actions vs github_actions)Possibly taken A pull request linked to this issue is open or already merged. Openbuilder persona triage
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
content driver persona triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
supadata-ai/mcp#27 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
capricorn86/happy-dom#2485 ·
Maintainers usually reply within 2 days
-
优化导入 OCR 模型选择文件的按钮样式Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
siyuan-note/siyuan#20430 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Albert-Weasker/niubigeo#194 ·
Maintainers usually reply within 1 day