From fea4a6bba8540a6df955e86bd0f26fc11ed34120 Mon Sep 17 00:00:00 2001 From: wcmolin Date: Fri, 6 Feb 2026 15:31:44 +0800 Subject: [PATCH] fix: use correct ZAI_API_KEY for Zhipu/GLM models LiteLLM's zai provider reads ZAI_API_KEY, not ZHIPUAI_API_KEY. This fixes authentication errors when using Zhipu/GLM models. --- nanobot/providers/litellm_provider.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nanobot/providers/litellm_provider.py b/nanobot/providers/litellm_provider.py index d010d81..d2880e1 100644 --- a/nanobot/providers/litellm_provider.py +++ b/nanobot/providers/litellm_provider.py @@ -52,7 +52,7 @@ class LiteLLMProvider(LLMProvider): elif "gemini" in default_model.lower(): os.environ.setdefault("GEMINI_API_KEY", api_key) elif "zhipu" in default_model or "glm" in default_model or "zai" in default_model: - os.environ.setdefault("ZHIPUAI_API_KEY", api_key) + os.environ.setdefault("ZAI_API_KEY", api_key) elif "groq" in default_model: os.environ.setdefault("GROQ_API_KEY", api_key)