Summary

Summary

The memory_search tool (invoked via the agent/tool chain, not CLI) has two related bugs when the gateway process has been running for a while:

1. Stale index — After workspace files are created, renamed, or deleted, memory_search continues returning results based on the old index state. The CLI command openclaw memory search returns correct results for the same query at the same time.
2. Ghost paths — Search results include file paths that no longer exist on disk, causing downstream read failures.

Both stem from the gateway's long-lived memory manager not re-syncing its index with the filesystem before serving queries.

Problem to solve

Expected vs Actual

Proposed solution

Steps to Reproduce

# 1. Start gateway
openclaw gateway start

# 2. Query via tool: memory_search("user preferences")
# Note the results.

# 3. Create a new file highly relevant to the query
# e.g. memory/user-preferences-test.md with matching content

# 4. Without restarting gateway, query again
# → new file does NOT appear (stale index)

# 5. Delete a file that appeared in step 2, then query again
# → deleted file's path still appears (ghost path)

# Control: `openclaw memory search "user preferences"` via CLI
# returns correct results — it creates a fresh manager each time.

### Alternatives considered

_No response_

### Impact

。

### Evidence/examples

_No response_

### Additional information

_No response_