Bug type

Regression (worked before, now fails)

Summary

Bug Description

When selecting a bailian provider model (e.g., bailian/qwen3.5-plus) from the Control UI model dropdown, the UI incorrectly sends the model ID to the backend as qwen-portal/qwen3.5-plus instead of bailian/qwen3.5-plus.

This causes the error: Failed to set model: GatewayRequestError: model not allowed: qwen-portal/qwen3.5-plus

Steps to Reproduce

1. Configure OpenClaw with multiple providers (e.g., qwen-portal and bailian)
2. Open Control UI
3. Select a bailian model from the dropdown (e.g., "qwen3.5-plus · bailian")
4. Observe the error message

Expected Behavior

The UI should send the correct full model ID (bailian/qwen3.5-plus) to the backend when a bailian model is selected.

Actual Behavior

The UI sends qwen-portal/qwen3.5-plus (wrong provider) to the backend.

Workaround

After selecting the bailian model, click "Refresh Chat Data" to reset the UI state. The model then works correctly.

Environment

• OpenClaw Version: 2026.3.13
• OS: Linux (WSL2)
• Browser: Control UI (web-based)
• Configuration: Multiple providers (qwen-portal with OAuth, bailian with API key)

Additional Context

• The bug only affects non-primary provider models
• Models from the first provider (qwen-portal) work correctly
• The UI displays the correct provider name in the dropdown, but the internal mapping is incorrect
• This appears to be a frontend JavaScript bug in the model selector component

Steps to reproduce

Bug Description

When selecting a bailian provider model (e.g., bailian/qwen3.5-plus) from the Control UI model dropdown, the UI incorrectly sends the model ID to the backend as qwen-portal/qwen3.5-plus instead of bailian/qwen3.5-plus.

This causes the error: Failed to set model: GatewayRequestError: model not allowed: qwen-portal/qwen3.5-plus

Steps to Reproduce

1. Configure OpenClaw with multiple providers (e.g., qwen-portal and bailian)
2. Open Control UI
3. Select a bailian model from the dropdown (e.g., "qwen3.5-plus · bailian")
4. Observe the error message

Expected Behavior

The UI should send the correct full model ID (bailian/qwen3.5-plus) to the backend when a bailian model is selected.

Actual Behavior

The UI sends qwen-portal/qwen3.5-plus (wrong provider) to the backend.

Workaround

After selecting the bailian model, click "Refresh Chat Data" to reset the UI state. The model then works correctly.

Environment

• OpenClaw Version: 2026.3.13
• OS: Linux (WSL2)
• Browser: Control UI (web-based)
• Configuration: Multiple providers (qwen-portal with OAuth, bailian with API key)

Additional Context

• The bug only affects non-primary provider models
• Models from the first provider (qwen-portal) work correctly
• The UI displays the correct provider name in the dropdown, but the internal mapping is incorrect
• This appears to be a frontend JavaScript bug in the model selector component

Expected behavior

Bug Description

When selecting a bailian provider model (e.g., bailian/qwen3.5-plus) from the Control UI model dropdown, the UI incorrectly sends the model ID to the backend as qwen-portal/qwen3.5-plus instead of bailian/qwen3.5-plus.

This causes the error: Failed to set model: GatewayRequestError: model not allowed: qwen-portal/qwen3.5-plus

Steps to Reproduce

1. Configure OpenClaw with multiple providers (e.g., qwen-portal and bailian)
2. Open Control UI
3. Select a bailian model from the dropdown (e.g., "qwen3.5-plus · bailian")
4. Observe the error message

Expected Behavior

The UI should send the correct full model ID (bailian/qwen3.5-plus) to the backend when a bailian model is selected.

Actual Behavior

The UI sends qwen-portal/qwen3.5-plus (wrong provider) to the backend.

Workaround

After selecting the bailian model, click "Refresh Chat Data" to reset the UI state. The model then works correctly.

Environment

• OpenClaw Version: 2026.3.13
• OS: Linux (WSL2)
• Browser: Control UI (web-based)
• Configuration: Multiple providers (qwen-portal with OAuth, bailian with API key)

Additional Context

• The bug only affects non-primary provider models
• Models from the first provider (qwen-portal) work correctly
• The UI displays the correct provider name in the dropdown, but the internal mapping is incorrect
• This appears to be a frontend JavaScript bug in the model selector component

Actual behavior

Bug Description

When selecting a bailian provider model (e.g., bailian/qwen3.5-plus) from the Control UI model dropdown, the UI incorrectly sends the model ID to the backend as qwen-portal/qwen3.5-plus instead of bailian/qwen3.5-plus.

This causes the error: Failed to set model: GatewayRequestError: model not allowed: qwen-portal/qwen3.5-plus

Steps to Reproduce

1. Configure OpenClaw with multiple providers (e.g., qwen-portal and bailian)
2. Open Control UI
3. Select a bailian model from the dropdown (e.g., "qwen3.5-plus · bailian")
4. Observe the error message

Expected Behavior

The UI should send the correct full model ID (bailian/qwen3.5-plus) to the backend when a bailian model is selected.

Actual Behavior

The UI sends qwen-portal/qwen3.5-plus (wrong provider) to the backend.

Workaround

After selecting the bailian model, click "Refresh Chat Data" to reset the UI state. The model then works correctly.

Environment

• OpenClaw Version: 2026.3.13
• OS: Linux (WSL2)
• Browser: Control UI (web-based)
• Configuration: Multiple providers (qwen-portal with OAuth, bailian with API key)

Additional Context

• The bug only affects non-primary provider models
• Models from the first provider (qwen-portal) work correctly
• The UI displays the correct provider name in the dropdown, but the internal mapping is incorrect
• This appears to be a frontend JavaScript bug in the model selector component

OpenClaw version

v2026.3.13

Operating system

win11

Install method

No response

Model

1

Provider / routing chain

1

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response