dvcrn Session History
Search through past OpenClaw session transcripts (JSONL files in ~/.openclaw/agents/*/sessions/).
Quick Reference
# Search for conversations about a topic
python3 scripts/search_sessions.py "gclid pipeline error"
# List recent sessions
python3 scripts/search_sessions.py --list --days 3
# Search specific agent's history
python3 scripts/search_sessions.py "flight monitor" --agent main
# Wider time range
python3 scripts/search_sessions.py "quantum encryption" --days 30 --max-results 5
Workflow
- Run
search_sessions.pywith the user's query terms to find relevant sessions - Use
sessions_historytool with thesessionKeyto pull full context from a match - If
sessions_historydoesn't work (old/closed sessions), read the JSONL file directly withread - Summarize what was found — don't dump raw transcripts
When to Use
- User says "remember when we discussed X?" or "we talked about Y last week"
- Resuming a thread that isn't captured in memory files
- Finding a decision, code snippet, or error from a past session
- Cross-referencing what was said vs what's in MEMORY.md
Tips
- Also check
memory_searchfirst — it indexes session transcripts too - Combine both:
memory_searchfor semantic matching,search_sessions.pyfor keyword/exact matching - The script searches user AND assistant messages
- JSONL path format:
~/.openclaw/agents/{agent_id}/sessions/{session_uuid}.jsonl