openclaw - 💡(How to fix) Fix [Feature]: Support configurable embedding provider for memory semantic search

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…

Body: Feature Request: Configurable embedding provider Problem memory_search currently fails if no embedding provider is configured: No API key found for provider "openai". Use Case Users running local GPU inference with Ollama (mxbai-embed-large) do not want to rely on cloud embedding services. The infrastructure is ready; only the configuration opening is missing. Suggested Solution Add a memory.embedding or memory.embeddingProvider config field that accepts a provider/model ID string: Example: memory: { backend: "builtin", embeddingProvider: "ollama/mxbai-embed-large:latest" } memory_search would then use the specified provider for vectorizing queries instead of hardcoding "openai". Environment OpenClaw version: 2026.5.27 Ollama running locally with embedding models available (mxbai-embed-large) Local GPU available for embedding inference

Root Cause

Body: Feature Request: Configurable embedding provider Problem memory_search currently fails if no embedding provider is configured: No API key found for provider "openai". Use Case Users running local GPU inference with Ollama (mxbai-embed-large) do not want to rely on cloud embedding services. The infrastructure is ready; only the configuration opening is missing. Suggested Solution Add a memory.embedding or memory.embeddingProvider config field that accepts a provider/model ID string: Example: memory: { backend: "builtin", embeddingProvider: "ollama/mxbai-embed-large:latest" } memory_search would then use the specified provider for vectorizing queries instead of hardcoding "openai". Environment OpenClaw version: 2026.5.27 Ollama running locally with embedding models available (mxbai-embed-large) Local GPU available for embedding inference

RAW_BUFFERClick to expand / collapse

Summary

Body: Feature Request: Configurable embedding provider Problem memory_search currently fails if no embedding provider is configured: No API key found for provider "openai". Use Case Users running local GPU inference with Ollama (mxbai-embed-large) do not want to rely on cloud embedding services. The infrastructure is ready; only the configuration opening is missing. Suggested Solution Add a memory.embedding or memory.embeddingProvider config field that accepts a provider/model ID string: Example: memory: { backend: "builtin", embeddingProvider: "ollama/mxbai-embed-large:latest" } memory_search would then use the specified provider for vectorizing queries instead of hardcoding "openai". Environment OpenClaw version: 2026.5.27 Ollama running locally with embedding models available (mxbai-embed-large) Local GPU available for embedding inference

Problem to solve

Body: Feature Request: Configurable embedding provider Problem memory_search currently fails if no embedding provider is configured: No API key found for provider "openai". Use Case Users running local GPU inference with Ollama (mxbai-embed-large) do not want to rely on cloud embedding services. The infrastructure is ready; only the configuration opening is missing. Suggested Solution Add a memory.embedding or memory.embeddingProvider config field that accepts a provider/model ID string: Example: memory: { backend: "builtin", embeddingProvider: "ollama/mxbai-embed-large:latest" } memory_search would then use the specified provider for vectorizing queries instead of hardcoding "openai". Environment OpenClaw version: 2026.5.27 Ollama running locally with embedding models available (mxbai-embed-large) Local GPU available for embedding inference

Proposed solution

Body: Feature Request: Configurable embedding provider Problem memory_search currently fails if no embedding provider is configured: No API key found for provider "openai". Use Case Users running local GPU inference with Ollama (mxbai-embed-large) do not want to rely on cloud embedding services. The infrastructure is ready; only the configuration opening is missing. Suggested Solution Add a memory.embedding or memory.embeddingProvider config field that accepts a provider/model ID string: Example: memory: { backend: "builtin", embeddingProvider: "ollama/mxbai-embed-large:latest" } memory_search would then use the specified provider for vectorizing queries instead of hardcoding "openai". Environment OpenClaw version: 2026.5.27 Ollama running locally with embedding models available (mxbai-embed-large) Local GPU available for embedding inference

Alternatives considered

No response

Impact

Body: Feature Request: Configurable embedding provider Problem memory_search currently fails if no embedding provider is configured: No API key found for provider "openai". Use Case Users running local GPU inference with Ollama (mxbai-embed-large) do not want to rely on cloud embedding services. The infrastructure is ready; only the configuration opening is missing. Suggested Solution Add a memory.embedding or memory.embeddingProvider config field that accepts a provider/model ID string: Example: memory: { backend: "builtin", embeddingProvider: "ollama/mxbai-embed-large:latest" } memory_search would then use the specified provider for vectorizing queries instead of hardcoding "openai". Environment OpenClaw version: 2026.5.27 Ollama running locally with embedding models available (mxbai-embed-large) Local GPU available for embedding inference

Evidence/examples

No response

Additional information

No response

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

openclaw - 💡(How to fix) Fix [Feature]: Support configurable embedding provider for memory semantic search