Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

With memory-wiki enabled in bridge mode and memory-core active, the wiki vault initializes successfully but bridge import consistently finds 0 artifacts and 0 workspaces.

Steps to reproduce

1. Enable memory-wiki in bridge mode in openclaw.json while keeping memory-core enabled.
2. Restart the gateway after applying the config.
3. Run openclaw wiki status.
4. Run openclaw wiki bridge import.
5. Observe that the wiki vault is ready, but bridge import reports 0 artifacts across 0 workspaces.

Expected behavior

When memory-wiki is enabled in bridge mode with memory-core as the active memory plugin, bridge import should discover at least some public memory artifacts or the docs should clearly describe what additional conditions are required before any artifacts become available.

Actual behavior

The wiki vault is created successfully and reports are generated, but openclaw wiki bridge import reports synced 0 artifacts across 0 workspaces, and openclaw wiki status warns that the active memory plugin is not exporting any public memory artifacts yet.

OpenClaw version

2026.4.8

Operating system

Ubuntu 24.04

Install method

npm global

Model

openai-codex/gpt-5.4

Provider / routing chain

openclaw -> gateway local runtime -> openai-codex

Additional provider/model setup details

The issue does not appear model-specific. The effective chat model in this environment is openai-codex/gpt-5.4. The active memory plugin is memory-core, and memory-wiki is enabled in bridge mode with search.backend: shared and search.corpus: all.

Logs, screenshots, and evidence

`openclaw wiki status` output:

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

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

`openclaw wiki bridge import` output:

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

Relevant config:


{
  plugins: {
    entries: {
      "memory-core": {
        config: {
          dreaming: {
            enabled: true,
            frequency: "0 17 * * *"
          }
        }
      },
      "memory-wiki": {
        enabled: true,
        config: {
          vaultMode: "bridge",
          vault: {
            path: "~/.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
          }
        }
      }
    }
  }
}
openclaw doctor did not report an obvious configuration problem.

Impact and severity

Affected: users trying to use memory-wiki bridge with memory-core as the active memory plugin
Severity: Medium, because bridge mode appears enabled and healthy but produces no imported knowledge
Frequency: 100% in observed tests
Consequence: users may assume bridge mode is working, but no wiki content is imported from memory-core, which blocks the intended automatic knowledge compilation workflow

Additional information

This was tested specifically to avoid maintaining a separate wiki by hand. The intended workflow is to keep using project AGENTS.md and memory files as the primary source of truth, and let memory-wiki bridge compile them automatically. If this behavior is expected, it would help if the docs explicitly described what conditions are required before bridge mode can see exported/public memory artifacts from memory-core.