Uninstalling QMD

[short haven]

I installed QMD but never really used it. And am noticing this in the logs:

04:25:01+00:00 warn memory {"subsystem":"memory"} qmd update failed (Error: qmd update failed (code 1): file:///home/mia/.bun/install/global/node_modules/@tobilu/qmd/dist/collections.js:112
        throw new Error(`Failed to parse ${configPath}: ${error}`);
              ^

Error: Failed to parse /home/mia/.openclaw/agents/evie/qmd/xdg-config/qmd/index.yml: YAMLParseError: Map keys must be unique at line 11, column 3:

    pattern: "**/*.md"
  memory-dir-evie:
  ^

    at loadConfig (file:///home/mia/.bun/install/global/node_modules/@tobilu/qmd/dist/collections.js:112:15)
    at getCollection (file:///home/mia/.bun/install/global/node_modules/@tobilu/qmd/dist/collections.js:147:20)
    at updateCollections (file:///home/mia/.bun/install/global/node_modules/@tobilu/qmd/dist/cli/qmd.js:432:25)
    at file:///home/mia/.bun/install/global/node_modules/@tobilu/qmd/dist/cli/qmd.js:2665:19

Node.js v22.22.2
)

I think it's maybe best I just uninstall it, but want to make sure I do it cleanly. What do I need to do?

[rose junco]

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

[soft tinsel]

Dan, yep, if you never used QMD I’d disable the OpenClaw backend first, then clean the sidecar bits. The log is QMD choking on its generated YAML collection config, not your core OpenClaw memory files.

I’d do this order:

openclaw --version
openclaw config get memory.backend
openclaw config set memory.backend builtin
openclaw config unset memory.qmd
openclaw config unset agents.defaults.memorySearch.qmd
openclaw config validate
openclaw gateway restart

Then confirm the warning is gone:

[soft tinsel]

openclaw logs --follow
# or
openclaw memory status --deep

After OpenClaw is no longer configured for QMD, the per-agent QMD directory is just sidecar state/cache. If you want a recoverable cleanup for the specific agent in your log:

mv ~/.openclaw/agents/evie/qmd ~/.openclaw/agents/evie/qmd.disabled.$(date +%Y%m%d%H%M%S)

Finally, remove the global QMD package using whatever installed it. The path in your stack trace points at a Bun global install of @tobilu/qmd; if you’re not sure, check:

command -v qmd

[soft tinsel]

Docs I checked: memory backend config says QMD is enabled by memory.backend = "qmd", and builtin is the default/recommended engine unless you intentionally operate QMD: https://docs.openclaw.ai/reference/memory-config 🦞

[short haven]

mia@MIA-PC1:~/.openclaw$ command -v qmd
/home/mia/.bun/bin/qmd

how do I uninstall it?

[soft tinsel]

That path means it’s a Bun global install. Use:

bun remove -g @tobilu/qmd
hash -r
command -v qmd

After that, command -v qmd should print nothing.

Then restart OpenClaw so the gateway stops seeing the old binary/state:

openclaw gateway restart

If bun remove -g @tobilu/qmd says it removed it but command -v qmd still returns ~/.bun/bin/qmd, check what’s left:

[soft tinsel]

ls -l ~/.bun/bin/qmd

If it’s just a stale shim/symlink, move it aside rather than deleting it:

mv ~/.bun/bin/qmd ~/.bun/bin/qmd.disabled

But I’d try the Bun global remove first. 🦞

[short haven]

That worked, thanks

[soft tinsel]

Glad that fixed it. Please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow indexes it for the next person. 🦞