Enterprise managed `model` setting is received but not applied in the Copilot app and non-interactive CLI
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 65/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
研究方向
The issue is in the runtime's model resolution path for non-interactive sessions. Start by examining the log output and the managed settings loading code, likely in a Rust module like model_bindings::api_resolver. Compare the interactive vs. non-interactive session initialization. Look for where the model key from managed-settings.json is read and applied. Check the session type detection and ensure the enterprise setting overrides the default. Run the CLI with -p and inspect the logs to see the flow.
由索引模型根據 Issue 內容生成。
描述
Describe the bug
Enterprise managed settings (copilot/managed-settings.json in the .github-private configuration source) contain { "model": "auto" }. The runtime log shows the server policy is fetched with keys=[model,permissions], but immediately afterwards the model resolver picks the built-in default (gpt-5.6-sol) instead of Auto.
Interactive CLI sessions in a terminal do honor the setting (new sessions show Auto). Sessions started by the GitHub Copilot desktop app, and CLI runs with -p or piped stdin, do not.
Affected version
Copilot CLI 1.0.89-1; GitHub Copilot app 1.1.23; macOS (Darwin 25.6). No MDM or file-based managed settings on the device.
Steps to reproduce the behavior
- Set the enterprise configuration source to a
.github-privaterepo whosecopilot/managed-settings.jsonis{ "model": "auto" }. Confirm the AI controls "Configuration summary" shows it. - Wait for propagation (runtime log shows
server policy served ... keys=[model,permissions]). - Run
copilot -p "Reply with the model name you are running as"or start a new session in the Copilot app. - Observe the session runs on
gpt-5.6-sol. Same on a cleanCOPILOT_HOMEwith no user settings or remembered model.copilot --model autoworks, so Auto is available to the account.
Runtime log (~/.copilot/logs/process-*.log):
[managedSettings] device MDM: no policy present on this device
[managedSettings] server policy served from fresh cache (age 47512ms) for https://github.com: bypassDisabled=false, keys=[model,permissions]
[managedSettings] effective policy resolved: source=server, bypassDisabled=false, serverFetchFailed=false, policyHelperFailed=false, policyHelperFailClosed=false
[rust:model_bindings::api_resolver] Using default model: gpt-5.6-sol
Expected behavior
Per the enterprise managed settings reference, model "sets your preferred model as the default for new conversations" and is listed as supported for Copilot CLI and the Copilot app. New sessions should start on Auto in both, including non-interactive runs.
Additional context
Interactive terminal sessions apply it correctly, so the gap appears to be in the non-interactive / app session path of the runtime. Happy to share a full redacted runtime log.
- 主要語言
- Shell
- 星號
- 11.2k
- 分支
- 1.9k
- 平均合併
- 17 小時 6 分鐘
- 30 天內合併 PR
- 5
環境準備
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/copilot-cli 的其他 Issue
-
triage
難度 1/5 1 小時以內 新手友好度 88/100
github/copilot-cli#4963 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 75/100
github/copilot-cli#4932 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 78/100
github/copilot-cli#4909 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 76/100
github/copilot-cli#4906 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 72/100
github/copilot-cli#4848 ·
維護者通常 1 天內回覆
查看 github/copilot-cli 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 78/100
YosysHQ/oss-cad-suite-build#216 ·
-
難度 2/5 1-3 小時 新手友好度 84/100
ekalinin/github-markdown-toc#167 ·
-
out-of-date
難度 1/5 1 小時以內 新手友好度 82/100
CachyOS/CachyOS-PKGBUILDS#1917 ·
維護者通常 1 天內回覆
-
package-update
難度 2/5 1-3 小時 新手友好度 78/100
-
bug needs triage
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆