Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix wiki.bridge.import returns 0 artifacts on 4.21 despite memory-core publicArtifacts registered [1 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#70242•Fetched 2026-04-23 07:27:19
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
dcstahl01dcstahl01
Participants
dcstahl01dcstahl01

Code Example

{
  "artifactCount": 0,
  "workspaces": 0
}
RAW_BUFFERClick to expand / collapse

Environment

  • OpenClaw 2026.4.21 (f788c88)
  • macOS Tahoe 26.4.1 arm64
  • memory-core, active-memory, and memory-wiki all loaded

Config

  • memory-wiki: bridge mode, bridge.enabled=true, readMemoryArtifacts=true, indexDailyNotes=true, indexMemoryRoot=true
  • memory-core: dreaming.enabled=true (cron 0 3 * * *)
  • active-memory: enabled=true, queryMode=recent
  • 5 agents configured in agents.list with explicit workspace paths

Problem

openclaw wiki bridge import --json consistently returns:

{
  "artifactCount": 0,
  "workspaces": 0
}

All three plugins show as loaded in openclaw plugins list. The main workspace has MEMORY.md and 29 daily note files in memory/. Dreaming has been enabled and triggered manually — dreaming promotion complete (workspaces=5, candidates=0, applied=0, failed=0) appears in the gateway log, confirming the dreaming runtime sees all 5 workspaces correctly.

However, listActiveMemoryPublicArtifacts returns [], causing bridge import to find 0 artifacts and 0 workspaces.

Diagnosis

PR #69219 (shipped in 4.20) fixed a bug where restoreMemoryPluginState was omitting the capability field, effectively wiping publicArtifacts after non-activating plugin loads. This fix appears to not fully resolve the issue — possibly a code path that still triggers the wipe after the fix.

Evidence:

  • collectWorkspaceArtifacts should find MEMORY.md and memory/*.md files in all 5 workspaces
  • resolveMemoryDreamingWorkspaces returns 5 workspaces during dreaming runtime (confirmed by log)
  • But bridge import sees 0 workspaces, suggesting the capability is empty/wiped when bridge import runs

Expected

openclaw wiki bridge import should return artifacts for MEMORY.md and daily notes across all configured agent workspaces.

Steps to Reproduce

  1. Enable memory-wiki in bridge mode with all bridge index flags true
  2. Enable memory-core dreaming
  3. Have MEMORY.md and memory/*.md files in workspace
  4. Run openclaw wiki bridge import --json
  5. Observe artifactCount=0, workspaces=0

extent analysis

TL;DR

Verify that the restoreMemoryPluginState function is correctly preserving the capability field, specifically the publicArtifacts data, after plugin loads and dreaming runtime execution.

Guidance

  • Review the implementation of restoreMemoryPluginState to ensure it handles the capability field correctly, considering the fix in PR #69219.
  • Check the logging of collectWorkspaceArtifacts and resolveMemoryDreamingWorkspaces to confirm they are finding the expected artifacts and workspaces.
  • Verify that the publicArtifacts data is not being wiped after the dreaming runtime execution, potentially by adding additional logging or debugging statements.
  • Test the listActiveMemoryPublicArtifacts function directly to see if it returns the expected artifacts, which may help isolate the issue.

Example

No specific code snippet can be provided without modifying the existing codebase, but adding logging statements to track the state of publicArtifacts throughout the execution of restoreMemoryPluginState, collectWorkspaceArtifacts, and resolveMemoryDreamingWorkspaces could help identify where the data is being lost.

Notes

The issue seems to be related to the preservation of the publicArtifacts data after plugin loads and dreaming runtime execution. However, without direct access to the codebase, it's challenging to provide a definitive solution. The steps outlined are intended to help diagnose and potentially resolve the issue.

Recommendation

Apply a workaround by modifying the restoreMemoryPluginState function to ensure it correctly handles the capability field, specifically preserving the publicArtifacts data. This is based on the evidence suggesting that the fix in PR #69219 may not fully resolve the issue, and further modifications may be necessary to correctly preserve the publicArtifacts data.

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…
#logging issue#authentication issue#prompt issue#agent setup#task chaining

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 wiki.bridge.import returns 0 artifacts on 4.21 despite memory-core publicArtifacts registered [1 participants]