Custom Agents are sorted by filename instead of display name
還沒有人認領這個 Issue。
評估
研究方向
定位自訂 agent 檔案 .agent.md 在選擇器中是在哪裡被發現並排序的：在程式碼庫中搜尋 *.agent.md 萬用字元以及對該清單的任何 .sort(。排序鍵應改為 frontmatter 的 name，當 name 缺少時回退到由檔名衍生的名稱，正如 issue 所指定。完成的標準是由 01-reviewer.agent.md/name: Zeta Reviewer 這類名稱建立的 agent 清單將 'Alpha Writer' 排在 'Zeta Reviewer' 之前；執行任何涵蓋 agent 載入的現有測試，或為比較器新增一個。
由索引模型根據 Issue 內容生成。
描述
Short summary
Custom Agents are sorted by filename instead of display name
Affected version or release
Latest
Installation context
GitHub Copilot App on Windows 11
What happened?
Description
Custom Agents in the Copilot desktop app are sorted by their filename instead of the name defined in the Markdown front matter.
GitHub documents name as the agent's display name, with the filename only used as a fallback when name is omitted.
Expected
Agents should be sorted alphabetically by their displayed name.
Actual
Agents are sorted alphabetically by their filename.
Steps to reproduce
No response
Expected behavior
Description
Custom Agents in the GitHub Copilot desktop app appear to be sorted alphabetically by their file name, rather than by the display name defined in the Markdown frontmatter.
This makes the ordering in the agent picker unexpected when file names are intentionally different from their user-facing names.
Steps to reproduce
Create multiple custom agents whose file names and display names sort differently, for example:
01-reviewer.agent.md
---
name: Zeta Reviewer
description: Reviews code changes
---
02-writer.agent.md
---
name: Alpha Writer
description: Helps write code and documentation
---
Open the Custom Agent picker in the GitHub Copilot desktop app.
Actual behavior
The agents are ordered according to their file names:
- Zeta Reviewer
- Alpha Writer
Expected behavior
The agents should be sorted by their displayed names:
- Alpha Writer
- Zeta Reviewer
Since the name frontmatter property represents the user-facing display name, sorting by that value would make the list consistent with what users actually see.
If name is omitted, the filename-derived name could naturally be used as the fallback sorting value.
Additional context
GitHub's Custom Agents documentation describes name as the display name for the custom agent and states that the filename is used as the default display name only when name is not specified.
This issue concerns the ordering of agents in the UI, not agent resolution/deduplication, where the filename may still be an appropriate identifier.
Additional context
No response
- 主要語言
- 沒有語言資料
- 星號
- 2.2k
- 分支
- 176
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/app 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 85/100
-
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 2/5 1-3 小時 新手友好度 70/100
-
難度 2/5 1-3 小時 新手友好度 70/100
-
難度 2/5 1-3 小時 新手友好度 62/100
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
-
bug
難度 2/5 1-3 小時 新手友好度 62/100
penso/herdr-gpui#399 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
feature
難度 2/5 1-3 小時 新手友好度 72/100
-
難度 2/5 1-3 小時 新手友好度 74/100
slopus/happy-desktop#45 ·
維護者通常 8 天內回覆