openclaw - ✅(Solved) Fix [Bug]: `memory index` fails with `Unknown memory embedding provider: ollama` [1 pull requests, 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#66688Fetched 2026-04-15 06:24:56
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×2commented ×1cross-referenced ×1referenced ×1

openclaw memory index --agent robotik --force fails when agents.defaults.memorySearch.provider is set to "ollama".

Error:

Memory index failed (robotik): Unknown memory embedding provider: ollama

Error Message

Error: Error:

Root Cause

openclaw memory index --agent robotik --force fails when agents.defaults.memorySearch.provider is set to "ollama".

Error:

Memory index failed (robotik): Unknown memory embedding provider: ollama

Fix Action

Fixed

PR fix notes

PR #66844: fix(memory): recognize ollama as valid embedding provider

Description (problem / solution / changelog)

Summary

  • Fixes #66688 — openclaw memory index fails with "Unknown memory embedding provider: ollama"
  • The getMemoryEmbeddingProvider() had a short-circuit guard: when any providers were already registered in the runtime map, it returned undefined for providers not in that map, without falling through to the plugin capability system
  • This meant ollama (which loads via a bundled plugin) was never discovered when other providers like openai or local were already registered

Changes

  • Removed the short-circuit guard in memory-embedding-provider-runtime.ts
  • Now always consults resolvePluginCapabilityProviders() when requested ID is not in the registered map
  • Updated existing test that encoded the buggy behavior
  • Added regression test tagged with #66688

Test plan

  • pnpm test passes for memory embedding provider tests
  • Verify openclaw memory index works with ollama provider configured

🤖 Generated with Claude Code

Changed files

  • src/plugins/memory-embedding-provider-runtime.test.ts (modified, +13/-2)
  • src/plugins/memory-embedding-provider-runtime.ts (modified, +8/-4)

Code Example

Memory index failed (robotik): Unknown memory embedding provider: ollama

---

{
  "agents": {
    "defaults": {
      "memorySearch": {
        "enabled": true,
        "provider": "ollama"
      }
    }
  }
}

---

openclaw memory index --agent robotik --force

---

Memory index failed (robotik): Unknown memory embedding provider: ollama

---
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

openclaw memory index --agent robotik --force fails when agents.defaults.memorySearch.provider is set to "ollama".

Error:

Memory index failed (robotik): Unknown memory embedding provider: ollama

Steps to reproduce

  1. Set:
{
  "agents": {
    "defaults": {
      "memorySearch": {
        "enabled": true,
        "provider": "ollama"
      }
    }
  }
}
  1. Configure models.providers.ollama and run local Ollama with an embedding model such as nomic-embed-text.
  2. Run:
openclaw memory index --agent robotik --force

Expected behavior

Memory indexing should work and use Ollama embeddings.

Actual behavior

Error:

Memory index failed (robotik): Unknown memory embedding provider: ollama

OpenClaw version

2026.4.12

Operating system

Ubuntu 24.04.3 LTS

Install method

docker official

Model

Ollama embedding model: nomic-embed-text

Provider / routing chain

chat model routing: openai-codex/gpt-5.4 -> memory embedding routing: ollama/nomic-embed-text

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can likely be resolved by ensuring that the Ollama memory embedding provider is properly registered or configured in the OpenClaw system.

Guidance

  • Verify that the ollama provider is correctly set up in the models.providers configuration, including any necessary dependencies or settings for the nomic-embed-text model.
  • Check the OpenClaw documentation for any specific requirements or guidelines for using the Ollama provider, as the error message suggests it is not recognized.
  • Confirm that the openclaw command is being run with the correct configuration and environment settings, ensuring that it can access and utilize the Ollama provider.
  • If using a custom or modified version of the Ollama provider, verify that it is compatible with the current version of OpenClaw (2026.4.12).

Example

No code snippet is provided as the issue seems to be related to configuration rather than code.

Notes

The solution may depend on the specific implementation details of the Ollama provider and its integration with OpenClaw, which are not fully described in the issue.

Recommendation

Apply workaround: Verify and correct the Ollama provider configuration to ensure it is properly registered and accessible to OpenClaw.

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

Memory indexing should work and use Ollama embeddings.

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 - ✅(Solved) Fix [Bug]: `memory index` fails with `Unknown memory embedding provider: ollama` [1 pull requests, 1 comments, 2 participants]