Skip to content

fix(openclaw): default memory search to local FTS#2297

Merged
btc69m979y-dotcom merged 2 commits into
release/2026.7.8from
fix/default-memory-fts-search
Jul 8, 2026
Merged

fix(openclaw): default memory search to local FTS#2297
btc69m979y-dotcom merged 2 commits into
release/2026.7.8from
fix/default-memory-fts-search

Conversation

@btc69m979y-dotcom

@btc69m979y-dotcom btc69m979y-dotcom commented Jul 8, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Generate OpenClaw memorySearch config even when embedding search is disabled.
  • Use provider none, fallback none, disable vector storage, and keep trigram FTS for the default local keyword-search path.
  • Add a gateway-startup migration for upgraded users whose existing memory index was built with an embedding provider: when the current main-agent config is FTS-only and the index meta is stale, run openclaw memory index --force --agent main before starting the gateway.
  • Keep current embedding-enabled configurations untouched; the migration skips when the effective main-agent memory search config still uses an embedding provider.

Validation

  • npm test -- openclawConfigSync.runtime
  • npm test -- openclawMemoryIndexMigration
  • npx eslint --ext ts,tsx --report-unused-disable-directives --max-warnings 0 src/main/libs/openclawConfigSync.ts src/main/libs/openclawConfigSync.runtime.test.ts
  • npx eslint --ext ts,tsx --report-unused-disable-directives --max-warnings 0 src/main/libs/openclawMemoryIndexMigration.ts src/main/libs/openclawMemoryIndexMigration.test.ts src/main/libs/openclawEngineManager.ts
  • npm run compile:electron
  • git diff --check

@btc69m979y-dotcom btc69m979y-dotcom merged commit 699aaeb into release/2026.7.8 Jul 8, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant