openclaw - 💡(How to fix) Fix [Bug] Webchat model selector prefixes all models with "anthropic/" regardless of actual provider [1 comments, 2 participants]

Failed to set model: GatewayRequestError: model not allowed: anthropic/MiniMax-M2.5

Fix Plan

The fix involves updating the model selector logic to correctly prefix model IDs with the actual provider name.

Code Changes

To fix the issue, update the getModelId function in the webchat control UI model selector to use the correct provider name:

// Before
const getModelId = (model) => `anthropic/${model.id}`;

// After
const getModelId = (model) => `${model.provider}/${model.id}`;

Additionally, ensure that the model.provider property is correctly set for each model in the openclaw.json configuration file:

{
  "providers": [
    {
      "name": "anthropic",
      "models": [
        { "id": "model-1", "provider": "anthropic" }
      ]
    },
    {
      "name": "zhipu",
      "models": [
        { "id": "glm-5", "provider": "zhipu" }
      ]
    },
    {
      "name": "minimax",
      "models": [
        { "id": "MiniMax-M2.5", "provider": "minimax" }
      ]
    }
  ]
}

Verification

After applying the fix, verify that the model selector correctly prefixes model IDs with the actual provider name by:

• Switching to a non-Anthropic model using the model dropdown
• Checking the network requests sent by the webchat control UI to ensure the correct provider-prefixed model ID is used
• Verifying that the model switch is successful and the "model not allowed" error is resolved

Extra Tips

• Ensure that the openclaw.json configuration file is correctly formatted and updated with the latest provider and model information.
• Consider adding additional logging or debugging statements to the model selector logic to help identify any future issues.