openclaw - 💡(How to fix) Fix Control UI may resolve short model IDs to the wrong provider unless alias is defined [1 comments, 2 participants]

Failed to set model: GatewayRequestError: model not allowed: minimax-portal/gpt-5.3-codex

TL;DR

Adding an explicit alias for each model without one may resolve the issue, as it ensures correct routing to the intended provider.

Guidance

• Verify that all models have unique names or aliases to prevent conflicts across providers.
• Check the model picker/resolver logic in Control UI to understand how it prioritizes alias/short-name matching.
• Consider updating the model configuration to include aliases for all models, especially those without unique short names.
• Review the provider configuration to ensure that the default provider/model path is correctly set up and does not interfere with model resolution.

Example

For a model like openai-codex/gpt-5.3-codex, adding an alias as shown can fix the routing issue:

"openai-codex/gpt-5.3-codex": { "alias": "gpt-5.3-codex" }

Notes

This approach may not be ideal as it makes aliases seem required for correct routing, which contradicts the expectation that they should be optional.

Recommendation

Apply workaround: Add explicit aliases to models without them to ensure correct routing, as this is a confirmed method to resolve the issue, even though it may not be the desired long-term solution.