OpenClaw

Use the published mr-memory@3.7.9 npm plugin for relay-based recall/capture and an optional, separate historical workspace/session upload. ClawHub listing status is unverified; the explicit npm source below is the audited path.

Quick Start (under a minute)

Step 1: Install the plugin

openclaw plugins install npm:mr-memory@3.7.9

Step 2: Add your memory key

openclaw mr <your-memory-key>

Step 3: Upload your existing history

openclaw mr upload

This is a separate historical-import operation. It scans the configured workspace and session paths and uploads the supported content it finds. Installing or enabling the relay alone does not import old history. Check openclaw mr status after the upload and supply explicit paths for content outside the configured locations.

Get your Memory Key at app.memoryrouter.ai.

How Your Memory Stays in Sync

After the initial upload, MemoryRouter keeps everything current automatically:

New direct user/assistant conversation is captured at agent_end. Tool use, subagent work, and internal processing are excluded. That ongoing capture is separate from file sync and historical upload.

Sync is debounced at 60 seconds. If startup sync just ran, the first session won't re-sync. But if you edit a file 2 minutes later and start a new session, it catches it.

Smart hash manifest: only files that actually changed get updated. No rebuilding the entire index every time.

Starting fresh

If you ever need to nuke your vault and rebuild from scratch:

openclaw mr delete    # Clear the vault
openclaw mr upload    # Rebuild from your current workspace + sessions

How It Works

User → OpenClaw (+ relevant memories injected locally) → Provider → Response

MemoryRouter replaces OpenClaw's built-in memory with persistent, sub-100ms cloud memory. When you chat, it retrieves relevant memories and injects them into the system prompt. At agent_end, it stores the direct user/assistant conversation while excluding tool use, subagent work, and internal processing. Workspace-file sync and historical upload remain separate operations.

Relay, not proxy. Memories are retrieved and injected through OpenClaw hooks. Inference and provider API keys remain inside OpenClaw and do not pass through MemoryRouter. Memory content is sent to MemoryRouter for storage/retrieval according to the plugin configuration.

openclaw mr off restores everything to stock: built-in memory, workspace indexing, all defaults.

What Makes It Faster

OpenClaw's built-in memory rebuilds the vector index on every search. The more files you have, the longer that takes, often 30-60 seconds per response.

MemoryRouter retrieves your memories in under 100ms and injects them before the model even starts. Same model, same prompt, and responses go from 30-60 seconds down to 2-3 seconds. We call it OpenClaw Instant.

Cron Jobs & Scheduled Tasks

Without MemoryRouter, your cron jobs and scheduled tasks run with zero context. With MemoryRouter, they remember everything you've ever discussed. Your morning email triage knows your priorities. Your code review agent knows your architecture. Every automated task runs with full context, never from scratch.

Commands

Upload Options

Already been using OpenClaw? All your conversation history and workspace knowledge is sitting on disk. openclaw mr upload discovers and uploads everything:

What gets uploaded automatically:

• Workspace files: MEMORY.md, memory/**/*.md, AGENTS.md, TOOLS.md
• Session transcripts from ~/.openclaw/agents/main/sessions/

Custom paths:

openclaw mr upload [path]              # Specific file or directory
openclaw mr upload --workspace <dir>   # Custom workspace directory
openclaw mr upload --brain <dir>       # Custom state dir (sessions from another agent)

After the initial upload, supported workspace-file sync can continue through the documented triggers. Direct user/assistant conversation is captured at agent_end; the plugin does not capture every internal event or tool trace.

Smart Storage

Only direct user ↔ AI conversation is stored. The following are excluded automatically:

• Tool use iterations (function calls, tool results)
• Subagent work
• Internal processing
• System noise (heartbeats, compaction flushes, audit messages)

This keeps your memory vault clean and relevant, with no noise from intermediate tool calls or system overhead.

Provider boundary

The relay is provider-independent because it runs in OpenClaw before model input and at agent end. It does not intercept or proxy provider requests. Provider credentials and inference remain with OpenClaw; only configured memory content is sent to MemoryRouter.

Configuration

After running openclaw mr <key>, the config is stored in your OpenClaw config:

{
  "plugins": {
    "entries": {
      "mr-memory": {
        "enabled": true,
        "config": {
          "key": "mk_xxx",
          "endpoint": "https://api.memoryrouter.ai"
        }
      }
    }
  }
}

Multi-Agent

Running multiple agents on one gateway? Each agent gets its own memory vault. See the Multi-Agent Setup guide.

Custom Endpoint

If you're running a self-hosted MemoryRouter instance, the endpoint is configurable in the plugin config.

Disable / Remove

# Disable (restores all OpenClaw defaults, keeps your memories in the vault)
openclaw mr off

# Delete all memories
openclaw mr delete

# Uninstall the plugin entirely
openclaw plugins uninstall mr-memory

openclaw mr off restores everything to stock: built-in memory, workspace indexing, all defaults.

After OpenClaw Updates

After running openclaw update, update the plugin:

openclaw plugins update mr-memory

Pricing

Get your Memory Key at app.memoryrouter.ai.