Connect OpenClaw to Agent Memory Service

Prerequisites

Before you begin, ensure you meet the following requirements:

• You have added an agent identity in the AMS console and copied the corresponding API key.

• You have created an endpoint in the AMS console and obtained the endpoint alias.

• OpenClaw is installed and its gateway starts properly.

• The OpenClaw CLI is installed locally, and you can successfully run openclaw --version.

• The OpenClaw version is compatible with the openclaw-mem0 plugin version. For details on configuration differences between versions, see the Version compatibility section.

Configure the AMS Mem0-compatible address in the following format:

http://<endpoint alias>:1995/mem0

In this address, 1995 is the fixed port and /mem0 is the prefix for the Mem0-compatible protocol.

Integration information

Version compatibility

• Recommended versions: OpenClaw v2026.4.24 or later, and @mem0/openclaw-mem0 1.0.11.

• For earlier versions of OpenClaw, such as v2026.3.23, you can use @mem0/openclaw-mem0 1.0.6 for a compatible integration. For more information, see the "How to connect an older OpenClaw version" section in the FAQ.

Step 1: Install the plugin

Run the following command to install the OpenClaw Mem0 plugin:

openclaw plugins install @mem0/openclaw-mem0

After the installation is complete, view the plugin information:

openclaw plugins inspect openclaw-mem0

To check your OpenClaw version, run the following command:

openclaw --version

Step 2: Configure the plugin

Enable openclaw-mem0 in the OpenClaw configuration file. The configuration file is typically located at:

~/.openclaw/openclaw.json

When automatically capturing session conversations, we recommend using autoCapture and autoRecall. Newer versions of OpenClaw require you to add hooks.allowConversationAccess to the plugin entry.

{
  "plugins": {
    "slots": {
      "memory": "openclaw-mem0"
    },
    "entries": {
      "openclaw-mem0": {
        "enabled": true,
        "config": {
          "mode": "platform",
          "apiKey": "${MEM0_API_KEY}",
          "baseUrl": "http://<endpoint alias>:1995/mem0",
          "userId": "openclaw-user",
          "autoCapture": true,
          "autoRecall": true,
          "topK": 5
        },
        "hooks": {
          "allowConversationAccess": true
        }
      }
    }
  }
}

Parameter descriptions:

Example of setting an environment variable:

export MEM0_API_KEY="<Your AMS API key>"

Step 3: Restart the gateway

After modifying the configuration, restart the OpenClaw gateway:

openclaw gateway restart

Validate the configuration file format:

openclaw config validate

Check the plugin connection status:

openclaw mem0 status --json

If connected is true in the returned result, the plugin is connected to AMS:

{
  "ok": true,
  "mode": "platform",
  "connected": true,
  "userId": "openclaw-user"
}

Step 4: Verify the integration

When verifying auto capture for an OpenClaw session, we recommend using a fixed session ID. Use the same session for the entire conversation, and then use the /reset command to end the current session.

If you use the WebUI for the entire conversation, open the following URL:

http://localhost:18789/chat?session=ams-openclaw-demo

If you use the CLI for the conversation and then enter /reset in the WebUI, you must open the URL that corresponds to the explicit CLI session:

http://localhost:18789/chat?session=agent%3Amain%3Aexplicit%3Aams-openclaw-demo

Here, agent:main:explicit:ams-openclaw-demo corresponds to the CLI's --session-id ams-openclaw-demo.

Example CLI conversation:

  openclaw agent --session-id ams-openclaw-demo \
  --message "I'm writing an integration guide for connecting OpenClaw to AMS. It includes a small example called 'Nanping Teabreak 0527'. I want the steps to feel like a casual chat." \
  --thinking off

Auto capture uses the config.userId from openclaw.json. In this example, it is openclaw-user.

Example conversation:

I'm writing an integration guide for connecting OpenClaw to AMS. It includes a small example called "Nanping Teabreak 0527". I want the steps to feel like a casual chat: chat a bit, then enter /reset, and then see if the memory was saved.

In the same session, enter /reset and choose Reset the current session. Do not create a new session instead of using /reset; creating a new session does not end the current one.
As another note for this example, I want to emphasize that the baseUrl should use the endpoint alias from the AMS console, with :1995/mem0 appended to the address. Don't use a local test address.

In the same session, enter /reset and select Reset the current session. Do not create a new session instead of using /reset; a new session will not end the current one.

Then, switch to a different topic in the same session:

Let's switch to a lighter topic. I might spend half a day near Xixi this weekend. I'm looking for a place where I can get coffee, take a slow walk, but that isn't too crowded or touristy. It would be great if there were more trees and fewer people, perfect for an afternoon around 3 or 4 PM.

After thinking about it, I've settled on a little plan for my weekend half-day: 'Huawu Slow Walk 0527'. I'll enter from the Xixi Huawu entrance around 3 PM, walk along the water, and find a quiet shop for an iced Americano. I don't want to rush through attractions; lots of shade and few people is all I need.

Changing topics, let's put the weekend plans aside for now. Tonight, I'm going to review the curl examples in the AMS Quick Start guide again, mainly to confirm that the baseUrl is written as the console endpoint alias plus :1995/mem0.

View the background events:

openclaw mem0 event list --json

If the event status is SUCCEEDED and payload.messages contains the conversation from this session, it indicates that autoCapture has sent the conversation to AMS:

{
  "ok": true,
  "events": [
    {
      "event_type": "ADD",
      "status": "SUCCEEDED",
      "payload": {
        "user_id": "openclaw-user",
        "run_id": "<user_id_hash>_group"
      }
    }
  ]
}

To confirm that long-term memory has been generated, wait for the background processing to complete after the event succeeds. Then, search for a stable keyword from the conversation:

openclaw mem0 search "Huawu Slow Walk 0527" --user-id openclaw-user --top-k 5 --json

If the result contains the corresponding keyword, this means that AMS has completed memory extraction and written it to the search index:

[
  {
    "scope": "long-term",
    "categories": ["travel"],
    "memory": "The user has decided on the 'Huawu Slow Walk 0527' plan..."
  }
]

Plugin capabilities

# Check connection
openclaw mem0 status --json

# View background events
openclaw mem0 event list --json
openclaw mem0 event status <event_id> --json

# List memories
openclaw mem0 list --user-id openclaw-user --top-k 10 --json

# Search memories
openclaw mem0 search "user preference" --user-id openclaw-user --top-k 5 --json

# Manually add a memory
openclaw mem0 add "User preference: Use Chinese for technical documents and maintain the Alibaba Cloud Help Center style." --user-id openclaw-user --json

FAQ

openclaw plugins install @mem0/openclaw-mem0@1.0.6

npm install -g @mem0/openclaw-mem0@1.0.6
npm root -g
openclaw plugins install /path/to/node_modules/@mem0/openclaw-mem0

~/.openclaw/extensions/openclaw-mem0/openclaw.plugin.json

{
  "plugins": {
    "slots": {
      "memory": "openclaw-mem0"
    },
    "entries": {
      "openclaw-mem0": {
        "enabled": true,
        "config": {
          "mode": "platform",
          "baseUrl": "http://<endpoint alias>:1995/mem0",
          "apiKey": "<Your AMS API key>",
          "userId": "openclaw"
        }
      }
    }
  }
}