own memorySearch.extraPaths | Friends of the Crustacean 🦞🤝 | Page 1

haughty sand Apr 18, 2026, 1:01 AM

#

Hi Krill — quick config question before I wire up a second agent.

I'm adding a support/maintenance agent (separate from the main user agent) to an existing openclaw.json that uses agents.list[]. I want this agent to have its own memorySearch.extraPaths pointing at a local knowledge base (GOTCHAS.md, BUGS.md, a few .md files), but I don't want those paths polluting the main agent's memory searches.

Two questions:

Does memorySearch.extraPaths work when set per-agent inside agents.list[], or only under agents.defaults?
If per-agent scoping isn't supported, what's the recommended pattern for giving a specific agent docs-first access to a local knowledge folder?

Running v2026.4.15. Thanks.

runic tigerBOT Apr 18, 2026, 1:01 AM

#

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

split juniperBOT Apr 18, 2026, 1:01 AM

#

sacred lionBOT Apr 18, 2026, 1:03 AM

#

Yes, on v2026.4.15 this is supported.

agents.list[].memorySearch.extraPaths works per agent.
It is merged with agents.defaults.memorySearch.extraPaths for that agent, not replaced.
So for your setup, the clean pattern is:
- keep agents.defaults.memorySearch.extraPaths empty, or only truly shared paths there
- put the KB paths only on the support agent under agents.list[].memorySearch.extraPaths

Example:

{
  agents: {
    defaults: {
      memorySearch: {

#

        enabled: true
      }
    },
    list: [
      { id: "main" },
      {
        id: "support",
        memorySearch: {
          extraPaths: [
            "~/kb/GOTCHAS.md",
            "~/kb/BUGS.md",
            "~/kb/support-notes"
          ]
        }
      }

#

    ]
  }
}

A couple of useful details:

relative extraPaths resolve against that agent’s workspace
by default, each agent gets its own memory DB/store, so this does not leak into the main agent unless you intentionally share paths or store.path
if you want docs-first behavior, give the support agent its own AGENTS.md / prompt instructions to check that KB first. extraPaths gives it access, prompt/workspace guidance gives it priority

If you are using QMD and mean cross-agent transcript search specifically, use agents.list[].memorySearch.qmd.extraCollections, not broad memory.qmd.paths.

Refs:

#own memorySearch.extraPaths