Repository navigation
Enterprise-managed custom model is listed in /model but cannot be selected #4960
Description
Activity
Thanks for raising this, @jorgegarciarey!
I've been able to confirm this and working on a fix as well as reviewing how this regressed. 🙇
Reacted by Jorge García Rey and Thiago CharãoWe're seeing the same behavior on our Enterprise configuration — an Enterprise-managed custom model (OpenAI-compatible provider) shows up in the
/modelpicker but selecting it via Enter silently leaves the previous model active,--model <catalog-model-id>does not work.May or may not be the same root cause, but worth mentioning: when the request does go through against the custom model via VS Code, we get a 400 back from the provider that looks like a content-negotiation / Accept-header issue:
Sorry, your request failed. Please try again. Client Request Id: a1174e63-9bfe-453d-8429-4bd3b4070ad4 GH Request Id: F3B0:2E667B:553842:5B1151:6AB53812 Reason: Request Failed: 400 {"error":{"message":"{\n \"code\" : \"391902\",\n \"message\" : \"Unsupported Accept header null is specified. Result set format must be JSON.\"\n}","code":"invalid_request_body"}}The
Unsupported Accept header null ... Result set format must be JSONpart suggests the request reaching the provider is missing anAccept: application/jsonheader. Flagging in case it's related to the picker path not fully wiring up the custom-model request the way--modeldoes.Also on CLI 1.0.88, macOS.
Describe the bug
An Enterprise-managed custom model configured through an OpenAI-compatible provider is shown in the interactive
/modelpicker, but cannot be selected.The picker displays the entry as:
Selecting the entry and pressing Enter leaves the previously active model unchanged. No error message is displayed.
The model itself is available and can be selected successfully when its full catalog model ID is supplied directly using the
--modelcommand-line option. This indicates that the model configuration, Enterprise policy, entitlement, and provider connectivity are valid.The failure appears to be limited to the interactive
/modelpicker.Affected version
GitHub Copilot CLI 1.0.88
Steps to reproduce the behavior
/model.Expected behavior
The custom model should become the active model for the current session, just as it does when its catalog ID is passed with
copilot --model <catalog-model-id>.Additional context
Other modelsin the/modelpicker.-for Context and Reasoning for this model.--modelselects and uses it successfully.Environment: