openclaw - 💡(How to fix) Fix Bug: openclaw memory status fails when memorySearch.provider is bedrock [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#63444Fetched 2026-04-09 07:53:39
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
Participants
Timeline (top)
renamed ×1

Error Message

  1. CLI crashes with: Error: Unknown memory embedding provider: bedrock

Root Cause

Root cause (suspected): The CLI embedded MemoryIndexManager initializes providers separately from the gateway process, and the bedrock embedding adapter is not registered in the CLI provider registry even though it is supported and works via the gateway.

RAW_BUFFERClick to expand / collapse

What: Running openclaw memory status (with bedrock as the memory embedding provider) throws Unknown memory embedding provider: bedrock, even though memory search works correctly via the gateway.

Steps to reproduce:

  1. Set agents.defaults.memorySearch.provider to "bedrock" in openclaw.json
  2. Run openclaw memory status
  3. CLI crashes with: Error: Unknown memory embedding provider: bedrock

Expected: The command should succeed. The gateway handles Bedrock memory embeddings correctly.

Evidence:

  • memory_search tool calls work correctly (via gateway)
  • The bedrock provider is documented as a valid memory embedding provider in the memory config reference
  • The CLI failure is specifically at getAdapter in manager-CKYnEo0k.js:313, which cannot find the bedrock adapter in the CLI/provider registry

Root cause (suspected): The CLI embedded MemoryIndexManager initializes providers separately from the gateway process, and the bedrock embedding adapter is not registered in the CLI provider registry even though it is supported and works via the gateway.

Impact: Blocks ability to run memory diagnostics (embedding probe, reindex, fix operations) when using Bedrock for memory embeddings.

extent analysis

TL;DR

The issue can likely be resolved by registering the Bedrock adapter in the CLI provider registry.

Guidance

  • Verify that the bedrock provider is correctly configured in openclaw.json and that the memory_search tool works as expected via the gateway.
  • Check the manager-CKYnEo0k.js file to understand how the getAdapter function is trying to find the bedrock adapter and why it's not registered.
  • Investigate how to register the bedrock adapter in the CLI provider registry, potentially by adding it to the registry or modifying the MemoryIndexManager initialization.
  • Consider comparing the gateway process initialization with the CLI initialization to identify differences in provider registration.

Example

No code snippet is provided as the issue does not contain sufficient code details.

Notes

The solution may involve modifying the MemoryIndexManager or the provider registry, but without more information about the codebase, it's difficult to provide a specific fix.

Recommendation

Apply workaround: Register the Bedrock adapter in the CLI provider registry, as this is likely the cause of the issue and resolving it should allow the openclaw memory status command to succeed.

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