Agent Memory maintains two parallel version lines: 0.x as an embedded OpenClaw plugin for single-machine use, and 1.x as a standalone Gateway service for multi-agent and service deployments. Each version line contains breaking changes (slot renames, tokenizer defaults, timing adjustments) and bug fixes; upgrading requires reviewing which changes affect your deployment model and configuration. In Agent Memory, L1 and L2 are distinct processing stages: L1 is a fast first-pass memory capture, and L2 is a slower, deeper extraction step that runs after L1 completes.
v1.0.0 and 0.x are maintained in parallel: the 0.x line (main branch) is the embedded OpenClaw plugin for lightweight single-machine use, while the 1.x line (feat/server branch) is the standalone Memory service for multi-agent, multi-framework, and service deployments.[1] In v1.0.0, the memory engine was split from an embedded OpenClaw plugin into an independent Gateway service process, changing both deployment and integration methods — see Hermes & Gateway hosts for the resulting architecture.[1]
v0.2.1 was deprecated because a missing undici dependency caused the plugin to fail to start; users should migrate to v0.2.2 or later, where the issue is fixed.[2]
In v0.3.6, the l3TiktokenEncoding default changed from o200k_base to cl100k_base to better match mainstream domestic and open-source model tokenizers (DeepSeek, GLM, MiniMax); only users explicitly depending on o200k_base need to override it.[3] Also in v0.3.6, the contextEngine slot ID was renamed from openclaw-context-offload to memory-tencentdb to prevent openclaw doctor --fix from resetting the slot.[3] In v0.3.5, the l2DelayAfterL1Seconds default was reduced from 90 s to 10 s so that cold-start users no longer wait roughly 90 seconds before seeing L2 scene extraction results.[4]
v0.3.6 fixed an infinite-recursion bug in the install script: when run as root, su - root re-entered the script, which saw EUID=0 again and looped indefinitely.[3]
Sources