Description

openclaw wiki bridge import (CLI) returns 0 artifacts across 0 workspaces and removes previously synced bridge sources, while the runtime bridge (in-process wiki_status tool) correctly sees all artifacts.

Reproduction

# CLI — broken
$ openclaw wiki bridge import
Bridge import synced 0 artifacts across 0 workspaces (0 new, 0 updated, 0 unchanged, 155 removed). Indexes refreshed (4 files).

$ openclaw wiki status
Bridge: enabled (0 exported artifacts)
Pages: 147 sources, 0 bridge provenance

Meanwhile, the in-process runtime tool returns:

Bridge: enabled (155 exported artifacts)
Pages: 302 sources, 149 bridge provenance

Analysis

The CLI standalone process calls listActiveMemoryPublicArtifacts but the memory-core plugin does not wire up its public artifacts export for out-of-process (CLI) invocations. The runtime (in-process) path works because the memory plugin is fully initialized in the gateway process.

This means every CLI wiki bridge import invocation destructively removes all bridge-sourced pages (155 removed in the example above), which are then only restored when the runtime bridge runs again.

Environment

• OpenClaw version: 2026.4.21 (f788c88)
• OS: macOS (Darwin 25.2.0, arm64)
• Node: v22.22.0
• Wiki vault mode: bridge

Expected Behavior

CLI wiki bridge import should see the same artifacts as the runtime bridge and sync them correctly.

Workaround

Avoid running openclaw wiki bridge import from the CLI. The runtime bridge handles sync correctly in-process.