Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Custom-agent reference documents reasoningEffort, but the working frontmatter key is reasoning-effort

未關閉 適合新手
#4,963 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
1/5
預估耗時
1 小時以內
新手友好度
88/100
Issue 類型
文件
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
github
領域
cli, documentation

研究方向

開啟連結的 Custom Agents Reference,搜尋 reasoningEffort,包括其描述和優先順序範例。更新參考文件,將 reasoning-effort 記錄為可運作的 frontmatter 鍵;只有在 camelCase 形式確實受到支援時才保留兩種拼法;完成的條件是文件中的語法與回報的可運作行為一致。

由索引模型根據 Issue 內容生成。

描述

triage

Describe the bug

The Copilot CLI custom-agent reference documents reasoningEffort as a frontmatter field. In Copilot CLI 1.0.88, that spelling did not apply the configured effort when I selected the agent with /agent. Changing only the field name to reasoning-effort made it work.

This matches the syntax reported in a comment on #2904. The reference currently leads users to configure a field that does not work in this case.

Affected version

GitHub Copilot CLI 1.0.88; macOS arm64.

Steps to reproduce the behavior

  1. Define a custom agent with reasoningEffort: "low" in its YAML frontmatter.
  2. Select it with /agent and observe that the configured effort does not take effect.
  3. Change only that key to reasoning-effort: "low", reload the agent, and select it again.
  4. Observe that the configured effort now takes effect.

Expected behavior

Update the custom-agent frontmatter reference to document reasoning-effort as the working key, including its description and precedence examples. If reasoningEffort is also intended to be supported, document both spellings and fix the camelCase spelling separately; it should not be presented as working while it is not.

Additional context

The issue is the documented frontmatter spelling, not a request to add per-agent reasoning effort: that capability was addressed in #2904.

主要語言
Shell
星號
11.2k
分支
1.9k
平均合併
14 小時 16 分鐘
30 天內合併 PR
6

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

github/copilot-cli 的其他 Issue

查看 github/copilot-cli 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。