#active memory plugin

23 messages · Page 1 of 1 (latest)

dawn epoch
#

How do I install the active memory plugin I asked my claw and it gave me this response back - Right now, you do not have the new Active Memory block exposed in your current config schema. In your installed 2026.4.12 config, memory-core only shows config.dreaming, not an activeMemory section yet.

So the practical answer is:

• Dreaming is available now
• that new Active Memory plugin/config you quoted is not active in your current install/config surface
• to get it, you likely need a newer build/version where that feature is included and surfaced in schema/UI

How you’ll know it’s available:

• under plugins.entries.memory-core.config, you should see something like an activeMemory section
• or a separate Active Memory plugin/config block in the UI

So for now:

• you can use Dreaming
• you can use memory search/recall
• but the automatic pre-reply dedicated memory sub-agent feature does not look enabled/exposed yet on this install

If you want, I can check whether this feature needs a self-update or whether it’s hidden behind another config path.

proper orbitBOT
dusky coralBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

proper orbitBOT
dawn epoch
#

@sinful scaffold

sinful scaffoldBOT
#

Let me verify the exact config path, then I’ll give you the clean answer.

#

I checked the docs/source, and the earlier answer is a bit off.

Active Memory is not a memory-core.config.activeMemory block. In current OpenClaw docs it is a separate plugin:

plugins.entries.active-memory

So the practical answer is:

  • memory-core = dreaming + normal memory stuff
  • active-memory = the pre-reply memory sub-agent
  • if your install does not show plugins.entries.active-memory, you likely need a newer OpenClaw build

First, check your version:

openclaw --version
#

Then update:

openclaw update

After that, enable it in openclaw.json like this:

{
  plugins: {
    entries: {
      "active-memory": {
        enabled: true,
        config: {
          agents: ["main"],
#
          allowedChatTypes: ["direct"],
          queryMode: "recent",
          promptStyle: "balanced",
          timeoutMs: 15000,
          maxSummaryChars: 220,
          logging: true
        }
      }
    }
  }
}

Then restart the gateway:

#

So, short version: you probably do not need to “install” a separate package, you need a new enough version and then enable the active-memory plugin.

If you paste your openclaw --version, I can tell you right away whether your current build should have it.

dawn epoch
#

OpenClaw 2026.4.12

sinful scaffoldBOT
#

Yep, that version is the issue.

2026.4.12 appears to predate the Active Memory config surface, so there is not a separate plugin install you can do on that build.

What to do instead:

openclaw update
openclaw gateway restart

Then look for:

plugins.entries["active-memory"]
#

Not:

plugins.entries["memory-core"].config.activeMemory

If it shows up, enable it like this:

{
  plugins: {
    entries: {
      "active-memory": {
        enabled: true,
        config: {
          agents: ["main"],
#
          allowedChatTypes: ["direct"],
          queryMode: "recent",
          promptStyle: "balanced",
          timeoutMs: 15000,
          maxSummaryChars: 220,
          logging: true
        }
      }
    }
  }
}

Then test with:

leaden void
#

@sinful scaffold does the above also affect version:
OpenClaw 2026.4.5 (3e72c03)

`openclaw gateway restart
Config warnings:\n- plugins.entries.active-memory: plugin not found: active-memory (stale config entry ignored; remove it from plugins config)

  • plugins.entries.memory-wiki: plugin not found: memory-wiki (stale config entry ignored; remove it from plugins config)`
    my current config:
    "plugins": {
    "slots": {
    "memory": "memory-core",
    "contextEngine": "lossless-claw"
    },
    "entries": {
    "memory-core": {
    "config": {
    "dreaming": {
    "enabled": true,
    }
    }
    },
    "active-memory": {
    "enabled": true,
    "config": {
    "enabled": true,
    "agents": ["main"]
    }
    },
    "memory-wiki": {
    "enabled": true,
    "config": {
    "vaultMode": "isolated",
    "vault": {
    "path": "~/.openclaw/wiki/main",
    "renderMode": "obsidian"
    },
    "obsidian": {
    "enabled": true,
    "useOfficialCli": true,
    "vaultName": "OpenClaw Wiki",
    "openAfterWrites": false
    },
    "bridge": {
    "enabled": false, .........
    },
    "ingest": {
    "autoCompile": true,
    "maxConcurrentJobs": 1,
    "allowUrlIngest": true
    },
    "search": {
    "backend": "shared",
    "corpus": "all"
    },
    "context": {
    "includeCompiledDigestPrompt": false
    },
    "render": {
    "preserveHumanBlocks": true,
    "createBacklinks": true,
    "createDashboards": true
    }
    }
    },
    "openclaw-web-search": {
    "enabled": true,
    "config": {}
    },
    "lossless-claw": {
    "enabled": true,
    },
sinful scaffoldBOT
#

Yep, same issue, and even more clearly on 2026.4.5.

That warning is the key part:

  • plugin not found: active-memory
  • plugin not found: memory-wiki

That means your current build does not include those plugins at all, so OpenClaw is ignoring those config blocks as stale entries.

So on 2026.4.5:

  • memory-core works
  • dreaming under memory-core works
  • active-memory does not exist in that install
  • memory-wiki does not exist in that install

What to do

#

Option 1, recommended

Update OpenClaw first:

openclaw update
openclaw gateway restart

Then check whether those warnings disappear.

Option 2, if you must stay on 2026.4.5

Remove these stale blocks from config for now:

  • plugins.entries.active-memory
  • plugins.entries.memory-wiki

and keep only the plugins your installed version actually has.

#

and I can tell you whether a straight update should be enough.

leaden void
#

@sinful scaffold this is ok after the update

sinful scaffoldBOT
#

Yep, if the plugin not found warnings are gone after the update, you should be good. 🎉

Quick sanity check:

/active-memory status

Optional debug:

/verbose on
/trace on

If that looks right, you’re past the version/plugin issue.