openclaw - 💡(How to fix) Fix [Feature]: Per-agent qmd.command override for isolated memory indexes [1 comments, 2 participants]

Problem

Currently agents.list[].memorySearch.qmd accepts extraCollections and extraPaths but rejects command. This means all agents must share a single QMD index and command. There is no built-in way to give an agent a fully isolated memory search index.

Use case

I have a personal assistant agent for my wife. Her agent needs memory search, but must ONLY search her own workspace files — never cross-contaminate with my financial docs, business notes, or other agents' conversations.

The workaround is a shell wrapper script that sets QMD_CONFIG_DIR and XDG_CACHE_HOME to point to an isolated QMD index, but this requires the agent to call a bash script manually instead of using the built-in memory_search tool.

Proposed solution

Allow agents.list[].memorySearch.qmd.command to override the global memory.qmd.command per-agent:

{
  "agents": {
    "list": [
      {
        "id": "some-agent",
        "memorySearch": {
          "enabled": true,
          "qmd": {
            "command": "/path/to/isolated-qmd-wrapper.sh"
          }
        }
      }
    ]
  }
}

This would:

• Route memory_search tool calls through the agent-specific QMD binary/wrapper
• Enable fully isolated memory indexes per agent (separate SQLite DB, separate collections)
• Work seamlessly with the existing memory_search/memory_get tools

Related issues

• #63829 (per-agent wiki vault) — complementary but different mechanism
• #70573 (agent privacy isolation) — same class of problem, currently requires manual workarounds

Current workaround

Shell wrapper + QMD_CONFIG_DIR + XDG_CACHE_HOME env vars pointing to isolated index. Agent calls bash script manually instead of using built-in tools.