openclaw - 💡(How to fix) Fix [Bug][Regression] memorySearch provider "gemini" unknown after steipete@3eb2a9d [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#73527Fetched 2026-04-29 06:18:45
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
Timeline (top)
closed ×1commented ×1

After updating to 2026.4.23 (commit steipete@3eb2a9d "fix(plugin-sdk): drop unavailable memory host exports"), agents.defaults.memorySearch.provider: "gemini" fails at runtime with:

[memory] sync failed (search): Error: Unknown memory embedding provider: gemini

Error Message

[memory] sync failed (search): Error: Unknown memory embedding provider: gemini

Root Cause

The commit cleaned up memory-host exports but appears to have removed the Gemini embedding provider registration from the runtime provider map. The config schema still lists "gemini" as a valid provider, but the embedding registry no longer recognizes it.

Fix Action

Fix / Workaround

Impact

  • Memory search is broken for anyone using Gemini embeddings
  • Workarounds: switch to openai/voyage/mistral temporarily, or disable memorySearch

Code Example

[memory] sync failed (search): Error: Unknown memory embedding provider: gemini

---

"memorySearch": {
    "enabled": true,
    "provider": "gemini",
    "model": "gemini-embedding-001",
    "remote": { "apiKey": "***" }
  }
RAW_BUFFERClick to expand / collapse

Summary

After updating to 2026.4.23 (commit steipete@3eb2a9d "fix(plugin-sdk): drop unavailable memory host exports"), agents.defaults.memorySearch.provider: "gemini" fails at runtime with:

[memory] sync failed (search): Error: Unknown memory embedding provider: gemini

Environment

  • OpenClaw version: 2026.4.23 (container, steipete@3eb2a9d + related memory-host changes)
  • Config unchanged and valid according to schema:
    "memorySearch": {
      "enabled": true,
      "provider": "gemini",
      "model": "gemini-embedding-001",
      "remote": { "apiKey": "***" }
    }
  • The same config worked before 2026.4.23

Root Cause

The commit cleaned up memory-host exports but appears to have removed the Gemini embedding provider registration from the runtime provider map. The config schema still lists "gemini" as a valid provider, but the embedding registry no longer recognizes it.

Impact

  • Memory search is broken for anyone using Gemini embeddings
  • Workarounds: switch to openai/voyage/mistral temporarily, or disable memorySearch

Expected Fix

Reinstate Gemini in the embedding provider registry (src/memory/embeddings or plugin-sdk) so config-spec and runtime behavior match again.

extent analysis

TL;DR

The most likely fix is to reinstate the Gemini embedding provider registration in the runtime provider map to match the config schema.

Guidance

  • Verify that the Gemini embedding provider was indeed removed from the runtime provider map in the src/memory/embeddings or plugin-sdk modules.
  • Check the config schema to ensure it still lists "gemini" as a valid provider and update it if necessary.
  • Consider switching to an alternative provider like "openai", "voyage", or "mistral" as a temporary workaround.
  • Review the changes made in commit steipete@3eb2a9d to understand the removal of the Gemini embedding provider registration.

Example

No code snippet is provided as the issue does not require a specific code change, but rather a registration update.

Notes

The fix relies on the assumption that the Gemini embedding provider was removed from the runtime provider map. If this is not the case, further investigation is needed.

Recommendation

Apply a workaround by switching to an alternative provider like "openai", "voyage", or "mistral" until the Gemini embedding provider registration is reinstated, as this is a quicker solution than waiting for the fix.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING