openclaw - 💡(How to fix) Fix 2026.4.5 regression: memory plugin fails — "embedding: must have required property 'embedding'" (framework config validation) [1 comments, 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#61780Fetched 2026-04-08 02:54:38
View on GitHub
Comments
1
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
closed ×1commented ×1

After updating to 2026.4.5, third-party memory plugins fail to initialize with:

memory-lancedb-pro invalid config: embedding: must have required property 'embedding'
1 plugin(s) failed to initialize (validation: memory-lancedb-pro)

This does not occur on 2026.4.4 with the same config.

Error Message

The AJV error instancePath: "/embedding", message: "must have required property 'embedding'" also suggests the validator may be running the plugin's configSchema against the wrong nesting level — passing config.embedding as the root instead of config.

Root Cause

After updating to 2026.4.5, third-party memory plugins fail to initialize with:

memory-lancedb-pro invalid config: embedding: must have required property 'embedding'
1 plugin(s) failed to initialize (validation: memory-lancedb-pro)

This does not occur on 2026.4.4 with the same config.

Fix Action

Workaround

None without modifying framework files directly.

Code Example

memory-lancedb-pro invalid config: embedding: must have required property 'embedding'
1 plugin(s) failed to initialize (validation: memory-lancedb-pro)

---

["embedding", "dbPath", "autoCapture", "autoRecall", "captureMaxChars"]
RAW_BUFFERClick to expand / collapse

Summary

After updating to 2026.4.5, third-party memory plugins fail to initialize with:

memory-lancedb-pro invalid config: embedding: must have required property 'embedding'
1 plugin(s) failed to initialize (validation: memory-lancedb-pro)

This does not occur on 2026.4.4 with the same config.

Affected component

dist/config-DCcTsPpK.jsmemoryConfigSchema

Diagnosis

The built-in memoryConfigSchema in the framework only allows 5 root config keys:

["embedding", "dbPath", "autoCapture", "autoRecall", "captureMaxChars"]

Third-party memory plugins (e.g. memory-lancedb-pro) use additional config keys that are fully declared in their own configSchema in openclaw.plugin.json. These get rejected by the framework's stock schema.

The AJV error instancePath: "/embedding", message: "must have required property 'embedding'" also suggests the validator may be running the plugin's configSchema against the wrong nesting level — passing config.embedding as the root instead of config.

The embedding sub-schema additionally only allows lowercase baseUrl, but the OpenAI SDK standard uses baseURL (uppercase).

Expected behavior

Plugins that declare their own configSchema should be validated against that schema only, not against the framework's built-in stock memoryConfigSchema. The stock schema is appropriate as a default for plugins without their own schema.

Workaround

None without modifying framework files directly.

Environment

  • OpenClaw: 2026.4.5
  • Plugin: memory-lancedb-pro 1.1.0-beta.10
  • Host: Debian 13 LXC

extent analysis

TL;DR

Update the framework's memoryConfigSchema to allow third-party plugins to validate against their own schema or modify the plugin's configSchema to comply with the framework's stock schema.

Guidance

  • Review the memoryConfigSchema in dist/config-DCcTsPpK.js to understand the current validation rules.
  • Check the configSchema in openclaw.plugin.json for the memory-lancedb-pro plugin to see the expected validation rules.
  • Consider modifying the framework's memoryConfigSchema to allow for additional config keys or updating the plugin's configSchema to use lowercase baseUrl instead of baseURL.
  • Verify that the embedding sub-schema is being validated correctly by checking the nesting level of the config object.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The issue seems to be related to a change in the framework's validation rules in version 2026.4.5. The workaround requires modifying framework files directly, which may not be desirable.

Recommendation

Apply a workaround by modifying the plugin's configSchema to comply with the framework's stock schema, specifically by using lowercase baseUrl instead of baseURL. This is a safer approach than modifying the framework's files directly.

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…

FAQ

Expected behavior

Plugins that declare their own configSchema should be validated against that schema only, not against the framework's built-in stock memoryConfigSchema. The stock schema is appropriate as a default for plugins without their own schema.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING