Skip to content

Memory search never returns results from memory files (only sessions) #46570

Description

@matthewcarano

Steps to reproduce

  1. Write content to a memory file: echo '## Test Entry' >> ~/.openclaw/workspace/memory/test.md
  2. Force reindex: openclaw memory index --force
  3. Verify indexed: openclaw memory status → shows memory files indexed with chunks
  4. Search for the content: openclaw memory search 'Test Entry'

Expected

Results include matches from memory files (memory/*.md).

Actual

All results come from session transcripts. Memory files are indexed (54 files, 936 chunks) but never appear in search results, even when the exact queried content exists in a memory file.

Tested with multiple queries, including exact phrases known to exist only in memory files. Hybrid mode (vector + FTS). Consistent across force reindexes.

Environment

  • OpenClaw 2026.3.11
  • Memory search provider: local
  • Model: embeddinggemma-300m-qat-q8_0
  • Mode: hybrid
  • 54 memory files indexed, ~550 session files indexed

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.staleMarked as stale due to inactivity

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions