The model selector appears to list only a prefix of the available models in alphabetical order, so models later in the alphabet cannot be selected at all.
Concretely, openai/gpt-4o-mini was not selectable from the dropdown on an OpenRouter-configured agent, despite being a valid model for that provider. The workaround was to set the model outside the UI (env/agent record).
Impact
On OpenRouter especially, the model list is long, and a large share of commonly used models sort past the visible cut-off. Since the dropdown is the only place to choose a comparison model in the UI, anything past the cut-off is unreachable.
Expected
All models for the configured provider are reachable — via a type-ahead/filter on the selector, or pagination, rather than a fixed prefix of an alphabetical list.
Note
Reported from observed behaviour in the dashboard on the claude/mcp-tool-execution branch; I did not confirm where the truncation happens (frontend render cap vs. API page size), so the exact limit and its location are worth verifying before fixing.
The model selector appears to list only a prefix of the available models in alphabetical order, so models later in the alphabet cannot be selected at all.
Concretely,
openai/gpt-4o-miniwas not selectable from the dropdown on an OpenRouter-configured agent, despite being a valid model for that provider. The workaround was to set the model outside the UI (env/agent record).Impact
On OpenRouter especially, the model list is long, and a large share of commonly used models sort past the visible cut-off. Since the dropdown is the only place to choose a comparison model in the UI, anything past the cut-off is unreachable.
Expected
All models for the configured provider are reachable — via a type-ahead/filter on the selector, or pagination, rather than a fixed prefix of an alphabetical list.
Note
Reported from observed behaviour in the dashboard on the
claude/mcp-tool-executionbranch; I did not confirm where the truncation happens (frontend render cap vs. API page size), so the exact limit and its location are worth verifying before fixing.