feat(models): register every /model/list scenario
Qoder's /model/list groups one account catalog by UI scenario (chat, assistant, quest, qwork, experts, ...). The CLI only read `chat`, so the picker hid models the IDE exposes elsewhere — GLM-5.3, GLM-5.2 and DeepSeek-V4-Pro live under experts/qwork. Register the union of the scenario groups, keeping the first occurrence per upstream key (chat wins) and excluding byok_* groups, which are bring-your-own-key providers rather than part of the shared catalog. Also keep an explicitly enabled `auto` model: live catalogs key `configs` by the whitespace-stripped display name, so it arrives as `Auto` instead of the legacy raw `auto` key. Refresh the lockfile to the 0.4.5 already in package.json.
This commit is contained in:
@@ -45,6 +45,8 @@ Model IDs are the catalog `display_name` with whitespace stripped. After login,
|
||||
|
||||
Examples: `Lite`, `Qwen3.8-Max`, `Qwen3.7-Plus`, `Qwen3.8-Flash`.
|
||||
|
||||
Qoder's `/model/list` groups one account catalog by UI scenario (`chat`, `assistant`, `quest`, `qwork`, `experts`, …). pi registers the **union** of those groups, so the picker matches the models your Qoder IDE shows instead of the old chat-only CLI subset (e.g. `GLM-5.3`, `GLM-5.2`, `DeepSeek-V4-Pro` appear only under `experts`/`qwork`). Duplicate upstream keys keep the `chat` entry.
|
||||
|
||||
Context uses the largest live catalog option (often 1M). Output is 128K.
|
||||
|
||||
## Endpoints
|
||||
|
||||
Reference in New Issue
Block a user