#persistent-memory #memory-recall #cross-ai-memory #semantic-search

MemoryRouter Memory

Persistent memory for OpenClaw, powered by MemoryRouter. Relay-based AI agent memory across sessions, compaction, and model changes.

John Rood@john-rood

Install

openclaw plugins install clawhub:mr-memory

mr-memory

Persistent memory for OpenClaw, powered by MemoryRouter.

mr-memory is an AI agent memory plugin that gives OpenClaw relevant context from prior conversations. It retrieves memory before agent/model input and captures the direct user-to-assistant exchange after each run, so useful context remains available across sessions, compaction, and model changes.

Use it when you want OpenClaw memory that does not restart from zero every session. Historical workspace and session data stays opt-in through an explicit upload command.

Install

bash

openclaw plugins install npm:mr-memory@3.7.10

The explicit npm: source and version make the audited install deterministic. mr-memory@3.7.10 is published on npm. A ClawHub listing has not been verified and is not required for this path.

Setup

bash

openclaw mr <your-memory-key>   # Get a key at memoryrouter.ai
openclaw mr upload               # Upload workspace + session history

Commands

bash

openclaw mr status           # Vault stats
openclaw mr upload           # Upload workspace + sessions
openclaw mr upload --brain ~/.notopenclaw   # Upload from a different agent
openclaw mr off              # Disable
openclaw mr delete           # Clear vault
openclaw mr <key>            # Enable with key

Upload Options

bash

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)

How It Works

When enabled, relay hooks retrieve memory before agent/model input and capture the direct user-to-assistant conversation at agent_end. Inference and provider API keys remain inside OpenClaw; the plugin does not route provider calls through MemoryRouter and is not a provider-key proxy.

Only direct user-to-AI conversation is stored. Tool use, subagent work, and internal processing are excluded. Historical workspace/session upload is a separate explicit openclaw mr upload operation; installing or enabling the relay does not imply an import already happened.

Config

After openclaw mr <key>, config is stored at:

json

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

Cross-AI and MCP Memory

The OpenClaw plugin uses relay hooks. Separately, the same MemoryRouter vault can connect to supported ChatGPT, Claude, Claude Code, Codex, and compatible MCP clients. Each host follows its own integration contract. Hosted ChatGPT and Claude connectors are model-directed, do not passively capture every conversation, and do not import old conversations just by connecting.

See the cross-AI and MCP memory guide for supported setup paths, permissions, verification steps, and host-specific limits.

Public Links

License

MIT