Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Control UI: Incorrect model prefix sent for glm-5-external (deepseek/ vs zai/) [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#48997•Fetched 2026-04-08 00:49:57
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
baofengbaofengbaofengbaofeng
Participants
baofengbaofengbaofengbaofengRyceRyce
Timeline (top)
labeled ×2commented ×1

Error Message

  • UI sends: deepseek/glm-5-external ✗ (causes error)
  1. Observe error in gateway logs: model not allowed: deepseek/glm-5-external

Fix Action

Fix / Workaround

Issue Description

When selecting the model "glm-5-external · zai" from the agents configuration dropdown in the Control UI, the UI sends deepseek/glm-5-external to the gateway via sessions.patch API, resulting in a GatewayRequestError: model not allowed: deepseek/glm-5-external.

Code Example

{
  "agents": {
    "defaults": {
      "models": {
        "zai/glm-5-external": {}
      }
    }
  }
}

$ openclaw models list
Model                                      Input      Ctx      Local Auth  Tags
deepseek/deepseek-chat                     text       195k     no    yes   default,configured
deepseek/deepseek-reasoner                 text       195k     no    yes   configured
zai/glm-5-external                         text       195k     no    yes   configured

### Steps to reproduce

/

### Expected behavior

/

### Actual behavior

/

### OpenClaw version

v2026.3.13

### Operating system

macOS

### Install method

npm

### Model

deepseek

### Provider / routing chain

openclaw -> webui

### Config file / key location

_No response_

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

Bug Report: Control UI incorrectly sends deepseek/glm-5-external instead of zai/glm-5-external

Environment

  • OpenClaw version: [Please specify]
  • Control UI: Compiled static assets
  • OS: macOS
  • Gateway running locally

Issue Description

When selecting the model "glm-5-external · zai" from the agents configuration dropdown in the Control UI, the UI sends deepseek/glm-5-external to the gateway via sessions.patch API, resulting in a GatewayRequestError: model not allowed: deepseek/glm-5-external.

Expected Behavior

  • Dropdown displays: "glm-5-external · zai" ✓
  • UI should send: zai/glm-5-external to gateway

Actual Behavior

  • Dropdown displays: "glm-5-external · zai" ✓
  • UI sends: deepseek/glm-5-external ✗ (causes error)

Steps to Reproduce

  1. Configure gateway with zai/glm-5-external in agents.defaults.models
  2. Open Control UI → Agents tab
  3. Select "glm-5-external · zai" from model dropdown
  4. Observe error in gateway logs: model not allowed: deepseek/glm-5-external

Configuration

Gateway config (openclaw.json):

{
  "agents": {
    "defaults": {
      "models": {
        "zai/glm-5-external": {}
      }
    }
  }
}

$ openclaw models list
Model                                      Input      Ctx      Local Auth  Tags
deepseek/deepseek-chat                     text       195k     no    yes   default,configured
deepseek/deepseek-reasoner                 text       195k     no    yes   configured
zai/glm-5-external                         text       195k     no    yes   configured

### Steps to reproduce

/

### Expected behavior

/

### Actual behavior

/

### OpenClaw version

v2026.3.13

### Operating system

macOS

### Install method

npm

### Model

deepseek

### Provider / routing chain

openclaw -> webui

### Config file / key location

_No response_

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence

```shell

Impact and severity

/

Additional information

/

extent analysis

Fix Plan

To resolve the issue, we need to update the Control UI to send the correct model name zai/glm-5-external instead of deepseek/glm-5-external.

Here are the steps:

  • Update the sessions.patch API call in the Control UI to use the correct model name.
  • Verify that the model name is correctly populated in the dropdown options.

Example code changes:

// Before
const modelName = 'deepseek/glm-5-external';

// After
const modelName = 'zai/glm-5-external';

Alternatively, if the model name is dynamically generated, ensure that the correct prefix zai/ is used instead of deepseek/.

Verification

To verify the fix, follow these steps:

  • Restart the Control UI and gateway.
  • Select the "glm-5-external · zai" model from the dropdown.
  • Check the gateway logs to ensure that the correct model name zai/glm-5-external is being sent.

Extra Tips

  • Double-check the openclaw.json configuration file to ensure that the correct model name is specified.
  • Verify that the zai/glm-5-external model is correctly configured and listed in the openclaw models list output.

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…

FAQ

Expected behavior

/

#api#ssr#installation#tensor shape#autograd error#training loop#device allocation#model download#tokenizer error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING