openclaw - 💡(How to fix) Fix memory-wiki bridge still imports 0 artifacts with QMD backend on 2026.4.26 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#73418Fetched 2026-04-29 06:20:10
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
1
Timeline (top)
closed ×1commented ×1

The documented QMD + memory-wiki bridge setup still reports 0 exported artifacts on OpenClaw 2026.4.26, even after QMD is installed, selected as the memory backend, indexed successfully, and memory-core is loaded as the active memory plugin.

This looks related to, or a still-reproducible variant of:

Root Cause

The documented QMD + memory-wiki bridge setup still reports 0 exported artifacts on OpenClaw 2026.4.26, even after QMD is installed, selected as the memory backend, indexed successfully, and memory-core is loaded as the active memory plugin.

This looks related to, or a still-reproducible variant of:

Code Example

{
  "memory": {
    "backend": "qmd",
    "qmd": {
      "sessions": {
        "enabled": true
      }
    }
  },
  "plugins": {
    "entries": {
      "memory-core": {
        "config": {
          "dreaming": {
            "enabled": true
          }
        }
      },
      "active-memory": {
        "enabled": true,
        "config": {
          "enabled": true,
          "agents": ["main"],
          "allowedChatTypes": ["direct"],
          "queryMode": "recent",
          "promptStyle": "balanced",
          "timeoutMs": 45000,
          "maxSummaryChars": 220,
          "persistTranscripts": false,
          "logging": false
        }
      },
      "memory-wiki": {
        "enabled": true,
        "config": {
          "vaultMode": "bridge",
          "vault": {
            "path": "/opt/hive/openclaw/wiki/main",
            "renderMode": "native"
          },
          "bridge": {
            "enabled": true,
            "readMemoryArtifacts": true,
            "indexDreamReports": true,
            "indexDailyNotes": true,
            "indexMemoryRoot": true,
            "followMemoryEvents": true
          },
          "ingest": {
            "autoCompile": true,
            "maxConcurrentJobs": 1,
            "allowUrlIngest": true
          },
          "search": {
            "backend": "shared",
            "corpus": "all"
          },
          "context": {
            "includeCompiledDigestPrompt": false
          },
          "render": {
            "preserveHumanBlocks": true,
            "createBacklinks": true,
            "createDashboards": true
          }
        }
      }
    }
  }
}

---

npm install -g @tobilu/qmd
   qmd --version

---

qmd 2.1.0

---

openclaw config set --batch-json '[{"path":"memory.backend","value":"qmd"},{"path":"memory.qmd.sessions.enabled","value":true}]' --strict-json

---

openclaw gateway restart

---

openclaw memory index --force --verbose

---

Memory Index (main)
Provider: qmd (requested: qmd)
Model: qmd
Sources: memory (MEMORY.md + /opt/hive/openclaw/agents/main/workspace/memory/*.md), sessions (/opt/hive/openclaw/agents/main/sessions/*.jsonl)

QMD index: /opt/hive/openclaw/agents/main/qmd/xdg-cache/qmd/index.sqlite (1097728 bytes)
Memory index updated (main).

---

backend: qmd
provider: qmd
requestedProvider: qmd
files: 59
chunks: 59
sources: memory, sessions
sourceCounts:
  memory: 53 files / 53 chunks
  sessions: 6 files / 6 chunks
audit issues: []

---

No plugin issues detected.

---

Gateway: reachable
Gateway service: systemd installed · enabled · running
Memory: 59 files · 59 chunks · sources memory, sessions · plugin memory-core · vector off
Plugin compatibility: none
Tasks: 0 active · 0 queued · 0 running · no issues · audit clean

---

Bridge import synced 0 artifacts across 0 workspaces (0 new, 0 updated, 0 unchanged, 0 removed). Indexes not refreshed (no-import-changes).

---

Wiki doctor: 1 issue(s) found

Wiki vault mode: bridge
Vault: ready (/opt/hive/openclaw/wiki/main)
Render mode: native
Obsidian CLI: missing
Bridge: enabled (0 exported artifacts)
Unsafe local: disabled
Pages: 3 sources, 0 entities, 0 concepts, 5 syntheses, 6 reports
Source provenance: 2 native, 0 bridge, 0 bridge-events, 0 unsafe-local, 1 other

Warnings:
- Bridge mode is enabled but the active memory plugin is not exporting any public memory artifacts yet.

Suggested fixes:
- Use a memory plugin that exports public artifacts, create/import memory artifacts first, or switch the wiki back to isolated mode.

---

OPENCLAW_DISABLE_PLUGIN_DISCOVERY_CACHE=1 \
OPENCLAW_DISABLE_PLUGIN_MANIFEST_CACHE=1 \
openclaw wiki bridge import

---

Bridge import synced 0 artifacts across 0 workspaces (0 new, 0 updated, 0 unchanged, 0 removed). Indexes not refreshed (no-import-changes).
RAW_BUFFERClick to expand / collapse

Summary

The documented QMD + memory-wiki bridge setup still reports 0 exported artifacts on OpenClaw 2026.4.26, even after QMD is installed, selected as the memory backend, indexed successfully, and memory-core is loaded as the active memory plugin.

This looks related to, or a still-reproducible variant of:

Environment

  • OpenClaw: 2026.4.26 (be8c246)
  • OS: Ubuntu 26.04 / Linux 7.0.0-14-generic x64
  • Node: v24.14.1
  • npm: 11.13.0
  • Install method: npm global
  • npm prefix: /home/jakub/.local
  • State dir: /opt/hive/openclaw
  • Config: /opt/hive/openclaw/openclaw.json
  • QMD: qmd 2.1.0, installed via npm install -g @tobilu/qmd

Relevant Config

{
  "memory": {
    "backend": "qmd",
    "qmd": {
      "sessions": {
        "enabled": true
      }
    }
  },
  "plugins": {
    "entries": {
      "memory-core": {
        "config": {
          "dreaming": {
            "enabled": true
          }
        }
      },
      "active-memory": {
        "enabled": true,
        "config": {
          "enabled": true,
          "agents": ["main"],
          "allowedChatTypes": ["direct"],
          "queryMode": "recent",
          "promptStyle": "balanced",
          "timeoutMs": 45000,
          "maxSummaryChars": 220,
          "persistTranscripts": false,
          "logging": false
        }
      },
      "memory-wiki": {
        "enabled": true,
        "config": {
          "vaultMode": "bridge",
          "vault": {
            "path": "/opt/hive/openclaw/wiki/main",
            "renderMode": "native"
          },
          "bridge": {
            "enabled": true,
            "readMemoryArtifacts": true,
            "indexDreamReports": true,
            "indexDailyNotes": true,
            "indexMemoryRoot": true,
            "followMemoryEvents": true
          },
          "ingest": {
            "autoCompile": true,
            "maxConcurrentJobs": 1,
            "allowUrlIngest": true
          },
          "search": {
            "backend": "shared",
            "corpus": "all"
          },
          "context": {
            "includeCompiledDigestPrompt": false
          },
          "render": {
            "preserveHumanBlocks": true,
            "createBacklinks": true,
            "createDashboards": true
          }
        }
      }
    }
  }
}

Steps Performed

  1. Updated OpenClaw to 2026.4.26.

  2. Ran openclaw doctor and openclaw doctor --fix.

  3. Installed QMD per docs:

    npm install -g @tobilu/qmd
    qmd --version

    Output:

    qmd 2.1.0
  4. Enabled QMD backend and session indexing:

    openclaw config set --batch-json '[{"path":"memory.backend","value":"qmd"},{"path":"memory.qmd.sessions.enabled","value":true}]' --strict-json
  5. Set memory-wiki search corpus to all per the documented QMD + bridge example.

  6. Restarted gateway:

    openclaw gateway restart
  7. Forced memory indexing:

    openclaw memory index --force --verbose

Evidence

openclaw memory index --force --verbose succeeded:

Memory Index (main)
Provider: qmd (requested: qmd)
Model: qmd
Sources: memory (MEMORY.md + /opt/hive/openclaw/agents/main/workspace/memory/*.md), sessions (/opt/hive/openclaw/agents/main/sessions/*.jsonl)

QMD index: /opt/hive/openclaw/agents/main/qmd/xdg-cache/qmd/index.sqlite (1097728 bytes)
Memory index updated (main).

openclaw memory status --json reports QMD as active and indexed:

backend: qmd
provider: qmd
requestedProvider: qmd
files: 59
chunks: 59
sources: memory, sessions
sourceCounts:
  memory: 53 files / 53 chunks
  sessions: 6 files / 6 chunks
audit issues: []

openclaw memory search roe --max-results 5 returns results from both memory files and QMD session exports, so QMD recall itself is working.

openclaw plugins doctor reports:

No plugin issues detected.

openclaw status --deep reports the gateway as healthy and memory as indexed:

Gateway: reachable
Gateway service: systemd installed · enabled · running
Memory: 59 files · 59 chunks · sources memory, sessions · plugin memory-core · vector off
Plugin compatibility: none
Tasks: 0 active · 0 queued · 0 running · no issues · audit clean

But openclaw wiki bridge import still reports zero artifacts:

Bridge import synced 0 artifacts across 0 workspaces (0 new, 0 updated, 0 unchanged, 0 removed). Indexes not refreshed (no-import-changes).

And openclaw wiki doctor reports:

Wiki doctor: 1 issue(s) found

Wiki vault mode: bridge
Vault: ready (/opt/hive/openclaw/wiki/main)
Render mode: native
Obsidian CLI: missing
Bridge: enabled (0 exported artifacts)
Unsafe local: disabled
Pages: 3 sources, 0 entities, 0 concepts, 5 syntheses, 6 reports
Source provenance: 2 native, 0 bridge, 0 bridge-events, 0 unsafe-local, 1 other

Warnings:
- Bridge mode is enabled but the active memory plugin is not exporting any public memory artifacts yet.

Suggested fixes:
- Use a memory plugin that exports public artifacts, create/import memory artifacts first, or switch the wiki back to isolated mode.

Expected Behavior

With the documented QMD + memory-wiki bridge setup, after QMD indexing succeeds and memory/session sources are visible, openclaw wiki bridge import should discover/import public memory artifacts, daily notes, dream reports, memory root files, and/or memory events.

Actual Behavior

QMD memory indexing and search work, memory-core is loaded, plugin diagnostics are clean, but memory-wiki bridge import still sees 0 artifacts and 0 workspaces.

Notes

I also tried the documented plugin cache-disable environment variables for the bridge import command:

OPENCLAW_DISABLE_PLUGIN_DISCOVERY_CACHE=1 \
OPENCLAW_DISABLE_PLUGIN_MANIFEST_CACHE=1 \
openclaw wiki bridge import

The result was unchanged:

Bridge import synced 0 artifacts across 0 workspaces (0 new, 0 updated, 0 unchanged, 0 removed). Indexes not refreshed (no-import-changes).

This may still be related to the registry/capability restore path described in #63157, or there may be another condition required for the QMD + bridge example that is not currently surfaced by wiki doctor or the docs.

extent analysis

TL;DR

The issue might be resolved by configuring the memory-core plugin to export public memory artifacts or by creating/importing memory artifacts first.

Guidance

  1. Verify memory artifact export: Check the memory-core plugin configuration to ensure it is set up to export public memory artifacts.
  2. Create/import memory artifacts: Try creating or importing memory artifacts manually to see if the memory-wiki bridge import can discover them.
  3. Check plugin compatibility: Ensure that the memory-core plugin is compatible with the QMD backend and the memory-wiki bridge.
  4. Review wiki doctor output: Examine the output of openclaw wiki doctor for any warnings or errors that may indicate the root cause of the issue.
  5. Test with isolated mode: Temporarily switch the wiki to isolated mode to see if the issue persists, which can help determine if the problem is related to the bridge setup.

Example

No code snippet is provided as the issue seems to be related to configuration and plugin setup rather than code.

Notes

The issue may be related to the registry/capability restore path described in #63157, and further investigation into this area may be necessary.

Recommendation

Apply workaround: Try configuring the memory-core plugin to export public memory artifacts or create/importing memory artifacts first to see if this resolves the issue. This approach is recommended as it directly addresses the potential root cause of the problem, which is the lack of exported memory artifacts.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix memory-wiki bridge still imports 0 artifacts with QMD backend on 2026.4.26 [1 comments, 2 participants]