Mem0 Plugin for NemoClaw — Quickstart

Add persistent long-term memory to your NemoClaw OpenClaw agent using the @mem0/openclaw-mem0 plugin.

Note: This plugin requires Mem0 Platform mode (i.e., a Mem0 API key from app.mem0.ai). Open-source mode is not supported in NemoClaw sandboxes because the sandbox proxy blocks /v1/embeddings requests required by the open-source backend. See Known Limitations for details.

Prerequisites

Accounts required:

• NVIDIA — sign up at build.nvidia.com, generate an API key at build.nvidia.com/settings/api-keys (starts with nvapi-)
• Mem0 — sign up at app.mem0.ai, generate an API key from the dashboard (starts with m0-)

Supported platforms: Ubuntu 22.04+, macOS (via Docker), Windows (WSL 2 + Docker)

Choose Your Path

Option A: Full Setup (NemoClaw + Mem0 Plugin)

Use this if you don't have NemoClaw installed yet. The script handles everything: Docker, Node.js, NemoClaw installation, onboarding, Mem0 plugin installation, network policy, and configuration.

# Download
curl -fsSL https://raw.githubusercontent.com/mem0ai/mem0/main/examples/nemoclaw/setup-mem0-nemoclaw.sh -o setup-mem0-nemoclaw.sh

# Run
chmod +x setup-mem0-nemoclaw.sh
./setup-mem0-nemoclaw.sh

The script runs through 7 phases:

Option B: Plugin Only (NemoClaw Already Installed)

Use this if you already have NemoClaw installed and onboarded with a sandbox in Ready state.

# Download
curl -fsSL https://raw.githubusercontent.com/mem0ai/mem0/main/examples/nemoclaw/install-mem0-plugin.sh -o install-mem0-plugin.sh

# Run
chmod +x install-mem0-plugin.sh
./install-mem0-plugin.sh

The script auto-detects your sandbox and runs 3 steps:

Verify the Installation

After either script completes, connect to the sandbox and start the gateway:

source ~/.bashrc
nemoclaw <sandbox-name> connect
nemoclaw-start

Look for this line in the startup output:

openclaw-mem0: registered (mode: platform, user: your-user-id, graph: false, autoRecall: true, autoCapture: true)

You can also verify with:

openclaw plugins list

The Memory (Mem0) plugin should show status loaded.

Test the Integration

All test commands run inside the sandbox.

Test 1: Auto-capture (storing memories)

openclaw agent --agent main --local \
  -m "My name is Alice and I work on distributed systems" \
  --session-id test1

Look for: openclaw-mem0: auto-captured 1 memories

Test 2: Auto-recall (retrieving memories across sessions)

Start a new session (different --session-id):

openclaw agent --agent main --local \
  -m "What do you know about me?" \
  --session-id test2

Look for: openclaw-mem0: injecting 1 memories into context (1 long-term, 0 session)

The agent should respond with information from the previous session ("Alice", "distributed systems").

Test 3: Interactive TUI

openclaw tui

Send messages and the plugin will automatically capture and recall memories in the background.

Plugin Configuration Reference

All options are set inside the sandbox via:

openclaw config set plugins.entries.openclaw-mem0.config.<key> <value>

Agent Memory Tools

Once the plugin is active, the agent can use these tools during conversations:

CLI Commands

Run these inside the sandbox:

# Search all memories (long-term + session)
openclaw mem0 search "what languages does the user know"

# Search only long-term memories
openclaw mem0 search "user preferences" --scope long-term

# Search only session memories
openclaw mem0 search "current task" --scope session

# Memory stats
openclaw mem0 stats

Troubleshooting

For detailed troubleshooting steps, see the troubleshooting guide included in this directory.

Common Issues

npm tar TAR_ENTRY_ERROR ENOENT during NemoClaw installation

This is a known npm bug where concurrent tar extraction races cause ENOENT errors on deeply nested packages. The setup-mem0-nemoclaw.sh script works around this by cloning the NemoClaw repo and installing with --maxsockets=1 to serialize downloads. If you installed NemoClaw manually and hit this error:

git clone --depth 1 https://github.com/NVIDIA/NemoClaw.git ~/.nemoclaw-src
cd ~/.nemoclaw-src
npm install --maxsockets=1
npm link

sandbox not found during onboarding step 7

The gateway restarted during onboarding and lost the sandbox state. Re-run nemoclaw onboard. When prompted that the sandbox already exists, choose y to recreate it.

npm error 403 Forbidden when installing plugin inside sandbox

The OpenShell gateway's TLS proxy blocks scoped npm packages (the %2f in the URL). Use the manual installation method (Method 2 in the scripts) which downloads outside the sandbox and uploads the tarball.

capture failed: Connection error or recall failed: Connection error

The network policy is not applied or missing the mem0_api entry. Re-run the plugin install script or manually apply the policy:

openshell policy set <sandbox-name> --policy /tmp/nemoclaw-mem0-policy.yaml --wait

Telemetry event capture failed: TypeError: fetch failed

This is harmless. The Mem0 SDK's telemetry endpoint (us.i.posthog.com) is blocked by the sandbox proxy. It does not affect memory functionality.

Plugin shows disabled in openclaw plugins list

The memory slot is not set to openclaw-mem0. Inside the sandbox, run:

openclaw config set plugins.slots.memory openclaw-mem0

K8s namespace not ready on Ubuntu 24.04

Ubuntu 24.04 defaults to cgroup v2 which causes k3s (used by NemoClaw) to fail. Apply the cgroup fix:

sudo python3 -c "
import json, os
p = '/etc/docker/daemon.json'
c = json.load(open(p)) if os.path.exists(p) else {}
c['default-cgroupns-mode'] = 'host'
json.dump(c, open(p, 'w'), indent=2)
"
sudo systemctl restart docker

Then re-run nemoclaw onboard.

Known Limitations

Open-source mode is not supported in NemoClaw sandboxes. The Mem0 open-source mode requires calling /v1/embeddings on an external LLM provider. NemoClaw's sandbox proxy intercepts all OpenAI-compatible API requests but only allows /v1/chat/completions through. Use platform mode instead.

Files in This Directory

Links

• Mem0 Documentation
• NemoClaw Documentation
• @mem0/openclaw-mem0 on npm
• Mem0 Dashboard