Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix memorySearch.extraPaths ignored - documented feature not implemented [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#57302•Fetched 2026-04-08 01:51:20
View on GitHub
Comments
1
Participants
2
Timeline
10
Reactions
0
Author
oddthebot510-aioddthebot510-ai
Participants
oddthebot510-aioddthebot510-aivincentkocvincentkoc
Timeline (top)
referenced ×6closed ×1commented ×1cross-referenced ×1

Fix Action

Workaround

Use qmd CLI directly:

qmd query "search term"
qmd update && qmd embed

PR fix notes

PR #57315: fix: wire memorySearch.extraPaths to QMD indexing

Description (problem / solution / changelog)

The agents.defaults.memorySearch.extraPaths config field is documented as adding extra directories to the memory index beyond default memory files. But the paths were never actually passed to the QMD backend — only memory.qmd.paths worked.

The Problem

Users configure:

memorySearch:
  extraPaths:
    - odd-vault
    - /Users/odd/workspace

Expecting those directories to be indexed. But openclaw memory status only shows the default "memory" source. The extra paths are completely ignored.

The Fix

In resolveMemoryBackendConfig(), the function now reads memorySearch.extraPaths from the config and maps them to QMD custom path collections before building the final collections array.

The extra paths are combined with any existing memory.qmd.paths entries, so both config locations work.

Files Changed

  • packages/memory-host-sdk/src/host/backend-config.ts — 12 lines added

Testing

  • Configure memorySearch.extraPaths in openclaw.json
  • Run openclaw memory index --force
  • Run openclaw memory status
  • Verify extra paths appear as indexed sources

Closes #57302

Changed files

  • CHANGELOG.md (modified, +1/-0)
  • packages/memory-host-sdk/src/host/backend-config.test.ts (modified, +171/-0)
  • packages/memory-host-sdk/src/host/backend-config.ts (modified, +29/-3)

Code Example

"Adds extra directories or .md files to the memory index beyond 
default memory files. Use this when key reference docs live 
elsewhere in your repo."

---

"memorySearch": {
  "enabled": true,
  "extraPaths": [
    "odd-vault",
    "/Users/odd/.openclaw/workspace",
    "/Users/odd/self-improving",
    "/Users/odd/proactivity"
  ]
}

---

qmd query "search term"
qmd update && qmd embed
RAW_BUFFERClick to expand / collapse

Bug Description

memorySearch.extraPaths is documented to "add extra directories or .md files to the memory index beyond default memory files", but the feature is not implemented.

Documentation

From config.schema.lookup:

"Adds extra directories or .md files to the memory index beyond 
default memory files. Use this when key reference docs live 
elsewhere in your repo."

Actual Behavior

  • extraPaths configuration is completely ignored
  • openclaw memory status shows only "memory" source
  • Only MEMORY.md + memory/*.md are indexed

Reproduction Steps

  1. Configure memorySearch.extraPaths in openclaw.json:
"memorySearch": {
  "enabled": true,
  "extraPaths": [
    "odd-vault",
    "/Users/odd/.openclaw/workspace",
    "/Users/odd/self-improving",
    "/Users/odd/proactivity"
  ]
}
  1. Run openclaw memory index --force
  2. Run openclaw memory status

Expected: Extra paths included in sources Actual: Only "memory" source shown

Workaround

Use qmd CLI directly:

qmd query "search term"
qmd update && qmd embed

Environment

  • OpenClaw: 2026.3.28
  • Node: 25.8.2
  • macOS: Darwin 25.3.0 (arm64)

Impact

Users cannot use memorySearch tool to search files outside of MEMORY.md and memory/ directory, despite documentation promising this capability.

extent analysis

Fix Plan

To implement the memorySearch.extraPaths feature, we need to modify the openclaw code to include the extra paths in the memory index. Here are the steps:

  • Modify the memorySearch function to accept the extraPaths configuration and add the extra directories or files to the memory index.
  • Update the openclaw memory index command to include the extra paths in the indexing process.

Example code changes:

// In memorySearch.js
const extraPaths = config.memorySearch.extraPaths;
if (extraPaths) {
  extraPaths.forEach((path) => {
    // Add the extra path to the memory index
    memoryIndex.addPath(path);
  });
}

// In openclaw.js
const memoryIndex = new MemoryIndex();
// ...
memoryIndex.index(extraPaths);
  • Update the openclaw memory status command to display the extra paths in the sources list.
// In openclaw.js
const sources = memoryIndex.getSources();
if (extraPaths) {
  sources.push(...extraPaths);
}
console.log(`Sources: ${sources.join(', ')}`);

Verification

To verify that the fix worked, follow these steps:

  1. Update the openclaw code with the above changes.
  2. Configure memorySearch.extraPaths in openclaw.json with the desired extra paths.
  3. Run openclaw memory index --force to re-index the memory.
  4. Run openclaw memory status to check if the extra paths are included in the sources list.
  5. Test the memorySearch tool with a search term to ensure it returns results from the extra paths.

Extra Tips

  • Make sure to handle errors and edge cases when adding extra paths to the memory index.
  • Consider adding a validation step to ensure the extra paths exist and are readable before adding them to the index.
  • Update the documentation to reflect the correct behavior of the memorySearch.extraPaths feature.

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…
#database connection#vector store#embedding generation#cache error#pipeline error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING