Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Custom provider sharing baseUrl with built-in provider still broken in latest release (Regression from 4.29)

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…

Root Cause

Summary: I have two accounts with the same AI provider (Zhipu/ZAI, base URL https://open.bigmodel.cn/api/coding/paas/v4). To use both, I defined a custom provider zai-light in openclaw.json with the same base URL but a different API key. Issue #79640 was closed because it was thought to be fixed in main, but after upgrading to the latest version, the issue is still not resolved. The custom provider's API key is still incorrectly resolving to the built-in zai-api-key.

RAW_BUFFERClick to expand / collapse

This is a follow-up to closed issue #79640.

Bug type: Regression (worked before, now fails)

Summary: I have two accounts with the same AI provider (Zhipu/ZAI, base URL https://open.bigmodel.cn/api/coding/paas/v4). To use both, I defined a custom provider zai-light in openclaw.json with the same base URL but a different API key. Issue #79640 was closed because it was thought to be fixed in main, but after upgrading to the latest version, the issue is still not resolved. The custom provider's API key is still incorrectly resolving to the built-in zai-api-key.

Steps to reproduce:

  1. Define two providers in openclaw.json: zai and zai-light, both using https://open.bigmodel.cn/api/coding/paas/v4 but with different API keys
  2. Define models under both providers (e.g., zai/glm-5-turbo and zai-light/glm-5-turbo)
  3. On latest release, try selecting a zai-light/* model via Telegram /models command
  4. Observe that the API key still incorrectly points to the built-in ZAI key.

Expected behavior: The custom provider zai-light should use its own configured API key from models.json, not the built-in zai-api-key.

Operating system: WSL2 (Ubuntu) on Windows 11

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#model download#tokenizer error#prompt formatting#chain 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

openclaw - 💡(How to fix) Fix [Bug]: Custom provider sharing baseUrl with built-in provider still broken in latest release (Regression from 4.29)