Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Control UI model picker incorrectly combines provider/model ID when switching models [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#53753•Fetched 2026-04-08 01:23:53
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
rollygpt6-cpurollygpt6-cpu
Participants
rollygpt6-cpurollygpt6-cpusteipetesteipete
Timeline (top)
closed ×1commented ×1locked ×1

Error Message

Error: model not allowed: kimi-coding/deepseek-reasoner

Root Cause

The UI appears to incorrectly prefix the current provider (kimi-coding) to the selected model ID (deepseek-reasoner) instead of using the correct provider (deepseek).

Fix Action

Fix / Workaround

Verification

  • Direct API call to switch to deepseek/deepseek-reasoner works correctly
  • Issue only occurs when using Control UI model picker
  • Workaround: Use conversation commands to switch models

Code Example

Error: model not allowed: kimi-coding/deepseek-reasoner

---

{
  "kimi-coding/kimi-k2.5": { "alias": "fast" },
  "deepseek/deepseek-chat": { "alias": "v3" },
  "deepseek/deepseek-reasoner": { "alias": "r1" }
}
RAW_BUFFERClick to expand / collapse

Bug Description

When using the Control UI to switch to a model from a different provider, the UI incorrectly constructs the model ID by prefixing the current provider to the target model ID.

Environment

  • OpenClaw version: 2026.3.13
  • OS: macOS (arm64)
  • Gateway mode: local (loopback)

Steps to Reproduce

  1. Start with current model set to kimi-coding/kimi-k2.5
  2. Open Control UI model picker
  3. Select "deepseek-reasoner" (DeepSeek R1)
  4. Error occurs

Expected Behavior

UI should send model ID: deepseek/deepseek-reasoner

Actual Behavior

UI sends model ID: kimi-coding/deepseek-reasoner

Error message:

Error: model not allowed: kimi-coding/deepseek-reasoner

Configuration

agents.defaults.models correctly configured:

{
  "kimi-coding/kimi-k2.5": { "alias": "fast" },
  "deepseek/deepseek-chat": { "alias": "v3" },
  "deepseek/deepseek-reasoner": { "alias": "r1" }
}

Verification

  • Direct API call to switch to deepseek/deepseek-reasoner works correctly
  • Issue only occurs when using Control UI model picker
  • Workaround: Use conversation commands to switch models

Root Cause

The UI appears to incorrectly prefix the current provider (kimi-coding) to the selected model ID (deepseek-reasoner) instead of using the correct provider (deepseek).

extent analysis

Fix Plan

To fix the issue, we need to update the Control UI model picker to correctly construct the model ID.

  • Update the getModelId function in the Control UI code to extract the provider from the selected model ID.
  • Use the extracted provider to construct the correct model ID.

Example code:

// Before
const getModelId = (selectedModel) => {
  const currentProvider = getCurrentProvider();
  return `${currentProvider}/${selectedModel}`;
};

// After
const getModelId = (selectedModel) => {
  const [provider, model] = selectedModel.split('/');
  return `${provider}/${model}`;
};

Verification

To verify the fix, follow these steps:

  • Start the Control UI with the updated code.
  • Select a model from a different provider using the model picker.
  • Check the constructed model ID to ensure it is correct.
  • Verify that the UI can successfully switch to the selected model.

Extra Tips

  • Ensure that the agents.defaults.models configuration is correctly updated to reflect the changes.
  • Test the fix with different models and providers to ensure it works as expected.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#tool integration#LLM response#prompt template#agent execution

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Control UI model picker incorrectly combines provider/model ID when switching models [1 comments, 2 participants]