openclaw-amem@1.2.0
Minor Changes
-
#45
398a59cThanks @heichaowo! - Add an OpenAI-compatible LLM provider. SetAMEM_LLM_PROVIDER=openaito route
note construction, CRUD decisions, link judgment and memory evolution through the
Chat Completions API instead of the Anthropic Messages API, with
AMEM_LLM_BASE_URLpointing at any OpenAI-compatible endpoint — OpenAI, DeepSeek,
OpenRouter, Groq, Together, or a local server (Ollama, vLLM, LM Studio). The
default staysanthropic, so existing setups are unchanged.Reasoning models (
o1,o3,gpt-5) are handled automatically, and keyless
local servers work without an API key. In the plugin, theopenaiSDK is a
runtime dependency kept out of the bundle, so the download size is unchanged for
everyone on the default path.
Patch Changes
-
#50
d07f16cThanks @heichaowo! - Fix three issues in the OpenAI-compatible provider, found in pre-release review:OPENAI_API_KEYwas ignored. The client always passed an explicit key, so
the SDK never read the standardOPENAI_API_KEY— a user who set it (but not
AMEM_LLM_API_KEY) got 401 on every call. It now falls back to
OPENAI_API_KEY, then to the keyless-local placeholder.deepseek-reasonersent the wrong token parameter. A broad
includes('reason')match classified it as an OpenAI reasoning model and sent
max_completion_tokens, which DeepSeek's API does not accept. Reasoning
detection is now scoped to OpenAI's owno*/gpt-5names.AMEM_LLM_PROVIDERwith surrounding whitespace (e.g."openai "from a
.envfile) silently routed to the Anthropic path. The value is now trimmed,
and an unrecognised value logs a warning instead of failing invisibly.