Agent Memory installs into OpenClaw via the native openclaw plugins install command and requires enabling in config and applying a one-time patch to hook after-tool-call messages for correct behavior. v2.0.0 Docker deployment splits Agent Memory across three images with multi-arch support; start-all.sh auto-initializes the admin account and prints the claude startup command once ready. The after-tool-call hook is an OpenClaw lifecycle event fired immediately after any tool executes; Agent Memory uses it to offload tool results to storage and recover context between turns.
Installing and enabling the plugin in OpenClaw takes two commands: openclaw plugins install @tencentdb-agent-memory/memory-tencentdb followed by openclaw gateway restart.[1] Use the native openclaw plugins install command (not npm directly) to avoid semantic-version-range issues that can disable the plugin; the same rule applies when upgrading via openclaw plugins update @tencentdb-agent-memory/memory-tencentdb.[1] Minimal zero-config OpenClaw setup requires adding { "memory-tencentdb": { "enabled": true } } to ~/.openclaw/openclaw.json.[1]
The openclaw-after-tool-call-messages.patch.sh script must be applied once per OpenClaw installation to hook after-tool-call messages for correct offload and recovery; the patch must be re-applied after each OpenClaw upgrade — see OpenClaw integration for behavioral details.[1]
A postinstall hook runs node scripts/postinstall.mjs automatically after npm install.[2]
v2.0.0 Docker deployment uses three images — agentmemory/memory-core, agentmemory/memory-hub, and agentmemory/memory-proxy — with multi-arch support (linux/amd64 + linux/arm64).[3] Running start-all.sh auto-initializes the admin account and generates .admin-key on first start, then prints a ready-to-use claude startup command once self-checks pass.[3] stop-all.sh --purge completely removes volumes and the admin key, making environment resets straightforward.[3]
Sources