Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix openclaw status: false lossless-claw provenance warnings, missing cfg in memory-search path [1 comments, 2 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#61957•Fetched 2026-04-08 03:10:45
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
1
Author
jeadesjeades
Participants
jason-zimmerjason-zimmerjeadesjeades
Timeline (top)
commented ×1cross-referenced ×1

`openclaw status` and `openclaw status --deep` emit false trust/provenance warnings for the `lossless-claw` plugin even though `openclaw plugins list --verbose` and `openclaw plugins inspect lossless-claw` are clean.

The false warnings observed were:

  • `plugins.allow is empty`
  • `loaded without install/load-path provenance`

Root Cause

The status memory-search path calls `resolveMemorySearchConfig()`, which calls `getMemoryEmbeddingProvider(...)` without passing `cfg`.

That falls through to `resolvePluginCapabilityProviders(...)`, which activates a runtime plugin registry without the active config/sourceConfig and emits bogus trust/provenance warnings.

RAW_BUFFERClick to expand / collapse

Summary

`openclaw status` and `openclaw status --deep` emit false trust/provenance warnings for the `lossless-claw` plugin even though `openclaw plugins list --verbose` and `openclaw plugins inspect lossless-claw` are clean.

The false warnings observed were:

  • `plugins.allow is empty`
  • `loaded without install/load-path provenance`

Environment

  • OpenClaw: v2026.4.5
  • OS: macOS

Reproduction

  1. Confirm `lossless-claw` is configured and `openclaw plugins list --verbose` / `openclaw plugins inspect lossless-claw` are clean.
  2. Run `openclaw status` or `openclaw status --deep`.
  3. Observe the false warnings above, even though the plugin inspection commands are clean.

Expected

`openclaw status` should not emit trust/provenance warnings for a correctly configured `lossless-claw` plugin.

Actual

`openclaw status` and `openclaw status --deep` emit false trust/provenance warnings that do not appear in direct plugin inspection.

Root Cause

The status memory-search path calls `resolveMemorySearchConfig()`, which calls `getMemoryEmbeddingProvider(...)` without passing `cfg`.

That falls through to `resolvePluginCapabilityProviders(...)`, which activates a runtime plugin registry without the active config/sourceConfig and emits bogus trust/provenance warnings.

Minimal Fix

Pass `cfg` into all `getMemoryEmbeddingProvider(...)` calls in memory-search config resolution.

Related Issues

  • #43655 is related because it reports the same false lossless-claw provenance warning symptom, but it does not isolate this specific status memory-search root cause.
  • #57095 is related because it is another CLI status memory-path bug involving provider/adapter resolution, but it manifests as a different failure mode rather than these false provenance warnings.

extent analysis

TL;DR

Passing the configuration object cfg to getMemoryEmbeddingProvider calls in memory-search config resolution is likely to fix the false trust/provenance warnings.

Guidance

  • Review the resolveMemorySearchConfig function to ensure it correctly passes cfg to getMemoryEmbeddingProvider.
  • Verify that the getMemoryEmbeddingProvider function is called with the correct configuration object cfg to prevent fallback to the runtime plugin registry.
  • Check the resolvePluginCapabilityProviders function to ensure it handles cases where the active config/sourceConfig is not provided, to prevent emitting bogus trust/provenance warnings.
  • Test the fix by running openclaw status and openclaw status --deep after applying the changes to confirm the false warnings are resolved.

Example

// Example of passing cfg to getMemoryEmbeddingProvider
const memoryEmbeddingProvider = getMemoryEmbeddingProvider(cfg, ...);

Notes

The provided root cause analysis suggests a specific issue with the resolveMemorySearchConfig and getMemoryEmbeddingProvider functions. However, without access to the full codebase, it's difficult to provide a comprehensive solution. The suggested fix should be verified through thorough testing to ensure it resolves the issue without introducing new problems.

Recommendation

Apply the workaround by passing cfg to getMemoryEmbeddingProvider calls, as this directly addresses the identified root cause of the false trust/provenance warnings.

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…
#docker error#permission error#memory optimization#batch processing#GPU compatibility

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING