Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: Regression: memory index shows 0 chunks on 2026.3.23-2 (works on 2026.3.12) [1 pull requests, 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#53666•Fetched 2026-04-08 01:25:08
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
OqpdbqpOOqpdbqpO
Participants
OqpdbqpOOqpdbqpO
Timeline (top)
labeled ×2closed ×1cross-referenced ×1locked ×1

After upgrading OpenClaw from 2026.3.12 to 2026.3.23-2, openclaw memory index --verbose reports success but openclaw memory status remains Indexed: 0/25 files · 0 chunks with provider qmd and source MEMORY.md + ~/.openclaw/workspace/memory/*.md. Rolling back to 2026.3.12 on the same host restores normal behavior (25/25 files · 25 chunks).

Root Cause

After upgrading OpenClaw from 2026.3.12 to 2026.3.23-2, openclaw memory index --verbose reports success but openclaw memory status remains Indexed: 0/25 files · 0 chunks with provider qmd and source MEMORY.md + ~/.openclaw/workspace/memory/*.md. Rolling back to 2026.3.12 on the same host restores normal behavior (25/25 files · 25 chunks).

Fix Action

Fixed

PR fix notes

PR #53683: fix(memory): report qmd status counts from real qmd manager

Description (problem / solution / changelog)

Summary

  • Remove the lightweight QMD status-only shim that always returned files=0 / chunks=0.
  • Reuse QmdMemoryManager in mode: \"status\" so openclaw memory status reads real index counts while still avoiding boot/update side effects.
  • Update search-manager cache test expectations for status-only requests to verify we cache the QMD manager path.

Fixes #53666 Fixes #53558

AI Assistance

  • AI-assisted: yes (implemented with Cursor/Codex agent)
  • Testing level: lightly tested + targeted regression checks
  • Local codex review --base origin/main: unavailable in this environment (codex command not found)

Test plan

  • pnpm test -- src/memory/search-manager.test.ts
  • pnpm test -- src/cli/memory-cli.test.ts -t \"status\"
  • pnpm build
  • pnpm check (also enforced by scripts/committer)
  • pnpm test (started, but appeared hung in this environment after starting unit-fast; command was terminated)

Made with Cursor

Changed files

  • src/memory/search-manager.test.ts (modified, +37/-7)
  • src/memory/search-manager.ts (modified, +84/-77)

Code Example

Validation performed

• Memory files exist and are non-empty under ~/.openclaw/workspace/memory/*.md
• MEMORY.md exists
• Removed sqlite and reindexed:
• rm -f ~/.openclaw/agents/main/qmd/xdg-cache/qmd/index.sqlite
• openclaw memory index --verbose
• still 0 chunks

Rollback confirmation

1. openclaw gateway stop
2. npm i -g [email protected]
3. openclaw gateway start
4. openclaw memory index --verbose
5. openclaw memory status

After rollback: Indexed: 25/25 files · 25 chunks (working again)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

After upgrading OpenClaw from 2026.3.12 to 2026.3.23-2, openclaw memory index --verbose reports success but openclaw memory status remains Indexed: 0/25 files · 0 chunks with provider qmd and source MEMORY.md + ~/.openclaw/workspace/memory/*.md. Rolling back to 2026.3.12 on the same host restores normal behavior (25/25 files · 25 chunks).

Steps to reproduce

  1. Upgrade from 2026.3.12 to 2026.3.23-2
  2. Run:

• openclaw memory index --verbose • openclaw memory status

  1. Observe status output

Expected behavior

Non-zero indexed files/chunks (same dataset previously indexed fine)

Actual behavior

Actual on 2026.3.23-2

• Indexed: 0/25 files · 0 chunks • Index command reports success and sqlite file is created/updated

OpenClaw version

OpenClaw: 2026.3.23-2 (7ffe7e4)

Operating system

OS: Linux 6.8.0-101-generic x64

Install method

Install method: npm global

Model

qmd

Provider / routing chain

Provider: qmd (requested: qmd), Model: qmd

Additional provider/model setup details

Environment

• OpenClaw: 2026.3.23-2 (7ffe7e4) affected • OpenClaw: 2026.3.12 (6472949) works • OS: Linux 6.8.0-101-generic x64 • Node: 22.22.1 • Install method: npm global • Memory provider: qmd • Workspace: ~/.openclaw/workspace • Sources shown by CLI: MEMORY.md + ~/.openclaw/workspace/memory/*.md

Logs, screenshots, and evidence

Validation performed

• Memory files exist and are non-empty under ~/.openclaw/workspace/memory/*.md
• MEMORY.md exists
• Removed sqlite and reindexed:
• rm -f ~/.openclaw/agents/main/qmd/xdg-cache/qmd/index.sqlite
• openclaw memory index --verbose
• still 0 chunks

Rollback confirmation

1. openclaw gateway stop
2. npm i -g [email protected]
3. openclaw gateway start
4. openclaw memory index --verbose
5. openclaw memory status

After rollback: Indexed: 25/25 files · 25 chunks (working again)

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

The fix involves modifying the openclaw configuration to ensure compatibility with the upgraded version.

  • Check the openclaw configuration file for any deprecated settings.
  • Update the qmd provider configuration to match the new version's requirements.
  • Verify that the MEMORY.md and ~/.openclaw/workspace/memory/*.md files are correctly formatted and accessible.

Example code snippet to update the qmd provider configuration:

// Update the qmd provider configuration
const qmdConfig = {
  // Add any new required settings for the upgraded version
  'indexing': {
    'enabled': true,
    'verbose': true
  }
};

// Save the updated configuration
fs.writeFileSync('~/.openclaw/config/qmd.json', JSON.stringify(qmdConfig, null, 2));
  • Run the openclaw memory index --verbose command again to re-index the memory files.
  • Restart the openclaw gateway service to apply the changes.

Verification

To verify that the fix worked, run the openclaw memory status command and check that the indexed files and chunks are non-zero.

Example output:

Indexed: 25/25 files · 25 chunks

Extra Tips

  • Regularly check the openclaw documentation for any changes to the configuration settings or provider requirements.
  • Consider setting up automated tests to detect any regressions in the openclaw functionality.

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…

FAQ

Expected behavior

Non-zero indexed files/chunks (same dataset previously indexed fine)

#model compatibility#GPU setup#container setup#orchestration issue#cache issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Bug]: Regression: memory index shows 0 chunks on 2026.3.23-2 (works on 2026.3.12) [1 pull requests, 1 participants]