fix(zai): fall back to default baseUrl when template lacks one for catalog models

xydttsw · claude · xydttsw · commit e1e8dbb2d432 · 2026-06-18T11:28:38.000+08:00
Static catalog model entries from the plugin manifest do not carry a per-model baseUrl - it is only set at the provider level. When ctx.providerConfig is undefined (no user config for zai provider) and the template model from the registry also lacks baseUrl, the resolved runtime model ends up without a baseUrl. This causes the OpenAI-compatible transport to fall back to OpenAI's default API host, producing confusing 401 errors for what should be Z.ai API calls. Add ZAI_GLOBAL_BASE_URL as the final fallback so catalog models always resolve with their expected base URL. Fixes #94269 Co-Authored-By: Claude <noreply@anthropic.com>
diff --git a/extensions/zai/index.ts b/extensions/zai/index.ts
@@ -34,7 +34,7 @@ import { fetchZaiUsage } from "openclaw/plugin-sdk/provider-usage";
 import { normalizeLowercaseStringOrEmpty } from "openclaw/plugin-sdk/string-coerce-runtime";
 import { detectZaiEndpoint, type ZaiEndpointId } from "./detect.js";
 import { zaiMediaUnderstandingProvider } from "./media-understanding-provider.js";
-import { buildZaiModelDefinition } from "./model-definitions.js";
+import { buildZaiModelDefinition, ZAI_GLOBAL_BASE_URL } from "./model-definitions.js";
 import { applyZaiConfig, applyZaiProviderConfig, resolveZaiModelId } from "./onboard.js";
 
 const PROVIDER_ID = "zai";
@@ -104,7 +104,7 @@ function resolveGlm5ForwardCompatModel(
     ...template,
     id: def.id,
     name: def.name,
-    baseUrl: ctx.providerConfig?.baseUrl ?? template?.baseUrl,
+    baseUrl: ctx.providerConfig?.baseUrl ?? template?.baseUrl ?? ZAI_GLOBAL_BASE_URL,
     api: "openai-completions",
     provider: PROVIDER_ID,
     reasoning: def.reasoning,
