Description
openclaw wiki bridge import consistently returns 0 artifacts despite having 4+ days of daily notes and memory files in the workspace. The wiki doctor confirms: "Bridge mode is enabled but the active memory plugin is not exporting any public memory artifacts yet."
Root Cause
The CLI command openclaw wiki bridge import calls syncMemoryWikiImportedSources which calls listActiveMemoryPublicArtifacts. This function depends on memoryPluginState.capability being populated by the memory-core plugin during gateway runtime initialization.
However, the CLI only registers plugin command surfaces via registerPluginCliCommandsFromValidatedConfig — it does not initialize the full plugin runtime. As a result, memoryPluginState.capability is undefined, and listActiveMemoryPublicArtifacts returns an empty array.
The relevant code path:
- CLI loads →
registerPluginCliCommands (registers commands only)
openclaw wiki bridge import → syncMemoryWikiBridgeSources → checks params.config.bridge.readMemoryArtifacts ✓
- → calls
listActiveMemoryPublicArtifacts({ cfg: params.appConfig }) → calls memoryPluginState.capability?.publicArtifacts?.listArtifacts
memoryPluginState.capability is undefined (never initialized) → returns []
- Result: 0 artifacts, 0 workspaces, empty vault
Steps to Reproduce
- Configure
memory-wiki in bridge mode with readMemoryArtifacts: true
- Have daily notes in
workspace/memory/ and MEMORY.md in workspace root
- Run
openclaw wiki bridge import --json
- Observe:
{"importedCount":0,"updatedCount":0,"skippedCount":0,"removedCount":0,"artifactCount":0,"workspaces":0,"pagePaths":[],"indexesRefreshed":false}
Expected Behavior
Bridge import should discover and sync workspace memory artifacts (MEMORY.md, daily notes, dream reports) into wiki source pages.
Environment
- OpenClaw 2026.4.10 (44e5b62)
- Plugins:
memory-core (dreaming enabled), memory-wiki (bridge mode)
- OS: CachyOS Linux 6.19.10-1 (x64)
Suggested Fix
Either:
- Make the CLI bridge import initialize the memory-core plugin runtime before scanning for artifacts, OR
- Have the gateway auto-sync bridge imports periodically or before wiki operations (currently
syncImportedSourcesIfNeeded runs before gateway wiki methods but is never triggered automatically)
Description
openclaw wiki bridge importconsistently returns 0 artifacts despite having 4+ days of daily notes and memory files in the workspace. The wiki doctor confirms: "Bridge mode is enabled but the active memory plugin is not exporting any public memory artifacts yet."Root Cause
The CLI command
openclaw wiki bridge importcallssyncMemoryWikiImportedSourceswhich callslistActiveMemoryPublicArtifacts. This function depends onmemoryPluginState.capabilitybeing populated by the memory-core plugin during gateway runtime initialization.However, the CLI only registers plugin command surfaces via
registerPluginCliCommandsFromValidatedConfig— it does not initialize the full plugin runtime. As a result,memoryPluginState.capabilityisundefined, andlistActiveMemoryPublicArtifactsreturns an empty array.The relevant code path:
registerPluginCliCommands(registers commands only)openclaw wiki bridge import→syncMemoryWikiBridgeSources→ checksparams.config.bridge.readMemoryArtifacts✓listActiveMemoryPublicArtifacts({ cfg: params.appConfig })→ callsmemoryPluginState.capability?.publicArtifacts?.listArtifactsmemoryPluginState.capabilityisundefined(never initialized) → returns[]Steps to Reproduce
memory-wikiin bridge mode withreadMemoryArtifacts: trueworkspace/memory/andMEMORY.mdin workspace rootopenclaw wiki bridge import --json{"importedCount":0,"updatedCount":0,"skippedCount":0,"removedCount":0,"artifactCount":0,"workspaces":0,"pagePaths":[],"indexesRefreshed":false}Expected Behavior
Bridge import should discover and sync workspace memory artifacts (MEMORY.md, daily notes, dream reports) into wiki source pages.
Environment
memory-core(dreaming enabled),memory-wiki(bridge mode)Suggested Fix
Either:
syncImportedSourcesIfNeededruns before gateway wiki methods but is never triggered automatically)