Skip to content

memory-wiki bridge sees 0 active public artifacts while host helper sees 1418 (2026.6.5-beta.2, memory-lancedb) #91756

Closed as not planned

Description

@islandpreneur007

memory-wiki bridge sees 0 active public artifacts while host helper sees 1418

Summary

On OpenClaw 2026.6.5-beta.2, memory-wiki bridge mode remains unable to see active memory public artifacts after restart even though the same live config can enumerate public memory artifacts through the host helper.

This blocks openclaw wiki bridge import from importing current workspace memory artifacts through the documented Gateway-backed active memory context.

Environment

OpenClaw 2026.6.5-beta.2 (131c9bf)
Gateway health: {"ok":true,"status":"live"}
Active memory slot: memory-lancedb
memory-wiki vaultMode: bridge
memory-wiki bridge.enabled: true
memory-wiki bridge.readMemoryArtifacts: true

Docs/source basis

Docs:

  • docs/cli/wiki.md says wiki bridge import imports public memory artifacts from the active memory plugin and routes active bridge artifact reads through Gateway RPC so the import uses the runtime memory plugin context.
  • docs/plugins/memory-wiki.md says bridge mode can import public memory artifacts and should use openclaw wiki status, openclaw wiki doctor, and openclaw wiki bridge import.

Source:

  • memory-lancedb/dist/index.js registers a memory capability with publicArtifacts.listArtifacts and delegates to listMemoryHostPublicArtifacts(params).
  • memory-host-core-B6bsC70V.js shows listMemoryHostPublicArtifacts enumerates configured memory workspace artifacts.
  • memory-state-CEaNZbtE.js shows listActiveMemoryPublicArtifacts returns the registered runtime memory capability's public artifacts, or [].
  • cli-DXHc47Vj.js shows wiki status and wiki bridge import use listActiveMemoryPublicArtifacts.

Reproduction

  1. Configure plugins.slots.memory = "memory-lancedb".
  2. Configure memory-wiki:
{
  "vaultMode": "bridge",
  "bridge": {
    "enabled": true,
    "readMemoryArtifacts": true,
    "indexDreamReports": true,
    "indexDailyNotes": true,
    "indexMemoryRoot": true,
    "followMemoryEvents": true
  }
}
  1. Restart Gateway.
  2. Run:
openclaw wiki status --json
openclaw wiki doctor --json

Actual:

{
  "vaultMode": "bridge",
  "bridgePublicArtifactCount": 0,
  "warnings": [
    {
      "code": "bridge-artifacts-missing",
      "message": "Bridge mode is enabled but the active memory plugin is not exporting any public memory artifacts yet."
    }
  ]
}
  1. Directly compare host helper vs active memory public artifact helper with the same live config:
node --input-type=module <<'NODE'
import { loadConfig, listMemoryHostPublicArtifacts, listActiveMemoryPublicArtifacts } from '/home/openclawops/.npm-global/lib/node_modules/openclaw/dist/plugin-sdk/memory-core.js';
const cfg = await loadConfig();
const host = await listMemoryHostPublicArtifacts({ cfg });
const active = await listActiveMemoryPublicArtifacts({ cfg });
console.log(JSON.stringify({
  hostCount: host.length,
  activeCount: active.length,
  hostSample: host.slice(0,5).map(a => ({kind:a.kind, workspaceDir:a.workspaceDir, relativePath:a.relativePath, contentType:a.contentType, agentIds:a.agentIds})),
  activeSample: active.slice(0,5).map(a => ({kind:a.kind, workspaceDir:a.workspaceDir, relativePath:a.relativePath, contentType:a.contentType, agentIds:a.agentIds}))
}, null, 2));
NODE

Actual:

{
  "hostCount": 1418,
  "activeCount": 0,
  "hostSample": [
    {
      "kind": "memory-root",
      "workspaceDir": "/home/openclawops/.openclaw/workspace",
      "relativePath": "MEMORY.md",
      "contentType": "markdown",
      "agentIds": ["main", "trent-cron"]
    },
    {
      "kind": "daily-note",
      "workspaceDir": "/home/openclawops/.openclaw/workspace",
      "relativePath": "memory/${today}.md",
      "contentType": "markdown",
      "agentIds": ["main", "trent-cron"]
    }
  ],
  "activeSample": []
}

Expected

listActiveMemoryPublicArtifacts({ cfg }) should surface the active memory plugin's registered public artifacts when the selected memory plugin is memory-lancedb and that plugin registers a publicArtifacts capability.

Then openclaw wiki status --json should report bridgePublicArtifactCount > 0, and openclaw wiki bridge import --json should import those public artifacts.

Impact

The documented bridge path stays at 0 artifacts even though workspace memory artifacts exist and the selected memory plugin's public artifact implementation delegates to the host helper that can enumerate them.

This blocks closing the current live bridge 0-artifacts gap without a workaround exporter.

Notes

This issue is separate from a future LanceDB durable-row exporter. The current native memory-lancedb public-artifacts implementation delegates to host workspace artifacts, not LanceDB table rows. This report only covers the runtime handoff split:

listMemoryHostPublicArtifacts({ cfg }) -> 1418
listActiveMemoryPublicArtifacts({ cfg }) -> 0
wiki status bridgePublicArtifactCount -> 0

Activity

  1. clawsweeper commented on Jun 9, 2026

    @clawsweeper
    Contributor

    Thanks for the context here. I swept through the related work, and this is now duplicate or superseded.

    Close as duplicate/superseded: this is a fresh, useful beta reproduction of the same memory-wiki bridge public-artifact handoff already tracked by the open canonical issue and the open LanceDB bridge PR, so keeping another issue open would split the fix discussion.

    Canonical path: Keep the remaining code and maintainer decision concentrated on #85655 and #84896, preserving this issue as linked beta evidence.

    So I’m closing this here and keeping the remaining discussion on #85655 and #84896.

    Review details

    Best possible solution:

    Keep the remaining code and maintainer decision concentrated on #85655 and #84896, preserving this issue as linked beta evidence.

    Do we have a high-confidence way to reproduce the issue?

    Yes, source inspection supports the reported split: host artifact listing can return workspace artifacts while the active helper returns an empty array if the memory capability handoff is missing. I did not run the live Gateway repro in this read-only cleanup pass.

    Is this the best way to solve the issue?

    Yes for triage cleanup: the best path is to close this duplicate and keep review on the existing canonical issue and open PR, rather than opening another parallel fix lane.

    Security review:

    Security review: Non-PR issue triage; no patch security review applies.

    AGENTS.md: found and applied where relevant.

    What I checked:

    • Current bridge import still depends on active memory capability state: syncMemoryWikiBridgeSources reads public artifacts through listActiveMemoryPublicArtifacts, so the reported host-helper-versus-active-helper split is on the current bridge handoff path. (extensions/memory-wiki/src/bridge.ts:227, 370cef2e3bdc)
    • Active helper returns whatever public artifact provider is registered: listActiveMemoryPublicArtifacts returns the registered process memory capability's publicArtifacts.listArtifacts result, or an empty array when that capability is absent. (src/plugins/memory-state.ts:312, 370cef2e3bdc)
    • memory-lancedb currently delegates public artifacts to the host helper: Current main registers a memory-lancedb publicArtifacts provider that delegates to listMemoryHostPublicArtifacts, matching the reporter's expectation that active artifacts should mirror host workspace artifacts. (extensions/memory-lancedb/index.ts:1502, 370cef2e3bdc)
    • Latest release still has the same unresolved handoff surface: The v2026.6.5 tag contains the same bridge Gateway routing and loader snapshot restore behavior, so this is not safe to close as implemented-on-main or shipped-fixed. (src/plugins/loader.ts:2708, 5181e4f7c82b)
    • Canonical open issue already tracks the same remaining symptom: GitHub search found open issue [Bug]: memory-wiki bridge import reports 0 artifacts while memory-core exports 683 #85655 for memory-wiki bridge import/status reporting 0 artifacts while direct memory public artifact listing returns hundreds; it is already labeled as a P2 regression with session-state impact.
    • Open PR tracks the memory-lancedb bridge fix path: Open PR fix(memory): export LanceDB artifacts for wiki bridge #84896 changes memory-lancedb, memory-wiki, and loader snapshot behavior for LanceDB/wiki bridge artifacts, has supplied proof, and remains the active maintainer-review lane for this behavior. (d49a99edf898)

    Likely related people:

    • brokemac79: Authored the merged PR commits that added memory-lancedb public artifact registration and memory sidecar capability preservation. (role: introduced current public-artifact behavior; confidence: high; commits: 280e99210a0e, ad595eb30468; files: extensions/memory-lancedb/index.ts, src/plugins/memory-state.ts)
    • vincentkoc: Authored the commit that routed memory-wiki bridge CLI paths through Gateway, which is central to the reported documented runtime handoff. (role: gateway bridge routing contributor; confidence: medium; commits: e2f3044b8fb7; files: extensions/memory-wiki/src/cli.ts)
    • manisandher: Authored the open PR that specifically targets LanceDB/wiki bridge artifact export and snapshot memory discovery behavior. (role: current canonical PR author; confidence: high; commits: cd06b05e5d5b, d4cc8ed358a6, d49a99edf898; files: extensions/memory-lancedb/index.ts, src/plugins/loader.ts, extensions/memory-wiki/src/markdown.ts)
    • steipete: Recent commits touched memory-wiki CLI, memory-lancedb, and plugin loader surfaces adjacent to the handoff and review boundary. (role: recent adjacent area contributor; confidence: medium; commits: 3430a2d26f52, 1d4c1ba56dcc, 6082f01b971e; files: extensions/memory-wiki/src/cli.ts, extensions/memory-lancedb/index.ts, src/plugins/loader.ts)

    Codex review notes: model gpt-5.5, reasoning high; reviewed against 370cef2e3bdc.

  2. added
    P2Normal backlog priority with limited blast radius.
    impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.
    on Jun 9, 2026
  3. locked as resolved and limited conversation to collaborators on Jun 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions