Troubleshooting OpenClaw Memory: Forgetfulness, Slow Context, and Storage Bloat

Start here: Run openclaw doctor and openclaw status before deep edits. See quick diagnostics.

Symptom → diagnosis flow

SymptomLikely causeFirst fix
Agent "forgot" yesterdayHistory limit too small; wrong agent memory scopeRaise historyLimit; check per-agent memory
Slow repliesOversized context sent every turnEnable summarization; trim MEMORY.md; see patterns
Disk growing fastUnbounded session logsSet retention; archive old sessions; backup then prune
Conflicting factsMultiple channels writing same USER.mdSplit agents or namespace memory files

Diagnostic commands

openclaw doctor
openclaw status
openclaw config validate
openclaw logs --tail 100
# Check memory directory size (Linux/macOS)
du -sh ~/.openclaw/memory 2>/dev/null || du -sh %USERPROFILE%\\.openclaw\\memory

Fix checklist

  1. Confirm you are messaging the same agent ID across channels.
  2. Verify persistPath is writable (common Docker volume issue — Docker install).
  3. After upgrades, re-run migration steps.
  4. For model-side limits, pick a higher-context stack (LLM guide).

Still stuck? Cross-reference error codes and base memory guide.