fix(coding-agent): use mimo-v2.6-pro as Xiaomi default model

The generated Xiaomi catalogs no longer include mimo-v2.5-pro.
This commit is contained in:
David Brailovsky 2026-10-16 12:51:37 +02:00
parent 99fe148970
commit 90d863f7c1

View file

@ -55,10 +55,10 @@ export const defaultModelPerProvider: Partial<Record<KnownProvider, string>> = {
"qwen-token-plan": "qwen3.7-max",
"qwen-token-plan-cn": "qwen3.7-max",
"qwen-token-plan-individual": "qwen3.8-max",
xiaomi: "mimo-v2.5-pro",
"xiaomi-token-plan-cn": "mimo-v2.5-pro",
"xiaomi-token-plan-ams": "mimo-v2.5-pro",
"xiaomi-token-plan-sgp": "mimo-v2.5-pro",
xiaomi: "mimo-v2.6-pro",
"xiaomi-token-plan-cn": "mimo-v2.6-pro",
"xiaomi-token-plan-ams": "mimo-v2.6-pro",
"xiaomi-token-plan-sgp": "mimo-v2.6-pro",
};
export interface ScopedModel {
@ -222,7 +222,7 @@ function resolveText(
/**
* `provider/rest` is only a hint: the whole text may also be a model id on another provider, such as
* gateway id `zai/glm-5` or commandcode id `xiaomi/mimo-v2.5-pro`. The named provider wins when usable,
* gateway id `zai/glm-5` or commandcode id `xiaomi/mimo-v2.6-pro`. The named provider wins when usable,
* since that is what the syntax usually means; otherwise a sole usable raw match wins, since the named
* provider could not serve the request. An unusable named match is still preferred over unusable raw
* matches, so `--api-key` can set up the named provider.