openclaw - 💡(How to fix) Fix [Bug]: memory-wiki CLI status/doctor hang even though direct underlying functions succeed [1 comments, 2 participants]

Summary

On OpenClaw 2026.4.29, bundled memory-wiki loads and openclaw wiki --help works, but openclaw wiki status and openclaw wiki doctor hang when invoked through the top-level CLI.

The underlying wiki functions complete successfully when called directly from Node in isolated mode, so this appears to be a CLI/plugin-bootstrap issue rather than a memory-wiki logic failure.

Environment

• OpenClaw: 2026.4.29
• Host: archWS-lxc
• OS: Linux 6.19.14-arch1-1
• memory-wiki configured under plugins.entries.memory-wiki
• tested in both bridge and isolated modes

What works

• memory-wiki plugin is present, enabled, and loaded
• openclaw plugins list --json shows memory-wiki with status: "loaded" and commands: ["wiki"]
• openclaw wiki --help works and lists subcommands
• direct calls to the underlying functions succeed in isolated mode:
  • initializeMemoryWikiVault(...)
  • syncMemoryWikiImportedSources(...)
  • resolveMemoryWikiStatus(...)

Direct-call result in isolated mode was healthy, e.g.:

• vaultMode: "isolated"
• vaultPath: "/root/.openclaw/wiki/main"
• vaultExists: true
• warnings: []

What fails

These hang through the top-level CLI wrapper:

openclaw wiki status --json
openclaw wiki doctor --json

Even with timeout 20s, they do not return and have to be killed.

Reproduction

1. Enable bundled memory-wiki in config.
2. Restart gateway and refresh registry if needed:

openclaw plugins registry --refresh

1. Confirm:

openclaw wiki --help

1. Run:

openclaw wiki status --json
openclaw wiki doctor --json

Additional findings

• The plugin CLI was initially missing until openclaw plugins registry --refresh was run.
• After refresh, openclaw wiki --help became available.
• The top-level hang still persisted afterward.
• Switching from bridge to isolated did not resolve the hang, so this does not appear to be purely a bridge/public-artifact issue.

Likely culprit

Reading the installed runtime suggests runWikiStatus / runWikiDoctor both call:

• syncMemoryWikiImportedSources(...)
• then resolveMemoryWikiStatus(...)

In isolated mode, direct invocation of those exact functions completes immediately.

That suggests the hang is in the full openclaw wiki ... CLI/plugin wrapper path rather than in the underlying memory-wiki status/sync logic.

Why this matters

This makes the bundled feature look broken even when the vault is actually healthy and the internal wiki functions are working.