MemoryRouter
OpenClaw memory

OpenClaw memory: a workspace that remembers its work

OpenClaw is built around a workspace: instructions, user profile, memory notes, and session history. It is one of the few agent runtimes that treats memory as a first-class file system.

OpenClaw. Sources checked 2026-09-25.

How OpenClaw handles memory today

Each agent gets a workspace with AGENTS.md for continuity rules, USER.md for durable user directives, MEMORY.md for notes, and daily memory logs, per the OpenClaw docs. Sessions are stored and can be resumed.

That design is file-based and local. The published mr-memory plugin adds a MemoryRouter relay so recall and capture run in the agent loop, and the vault survives workspace moves, machine changes, and long-running work.

What OpenClaw forgets

Files are durable and shallow. Long sessions are deep and fragile.

The fix with MemoryRouter

The mr-memory plugin wires MemoryRouter into the agent loop, so retrieval happens before model input and capture at agent end. Your workspace stays; the memory becomes durable.

  1. 1

    Install the plugin

    Install from npm and approve the third-party source, then add your MemoryRouter key to the plugin configuration.

    Install the plugin

    openclaw plugins install npm:mr-memory
  2. 2

    Verify

    Check status, then inspect the plugin runtime to confirm the hooks are active.

    Status check

    openclaw mr status
  3. 3

    Upload prior history if you have it

    The plugin can upload workspace and session history so a new vault starts with the work you already did.

    Import history

    openclaw mr upload
Install mr-memory for OpenClaw

Plugin install, key setup, and history import on the OpenClaw page. 14-day free trial.

Related

OpenClaw memory FAQ

Sources

Sources checked 2026-09-25. Tool behavior changes; check the vendor docs before relying on a detail.

Start free