session-logs

You can search conversation history stored in JSONL session logs by using jq and rg to parse and filter data from the ~/.openclaw/agents/<agentId>/sessions directory. This allows you to retrieve specific prompts, responses, and timestamps from prior sessions.

Yes, you can extract costs and timestamps when analyzing session logs by querying the structured JSONL files with jq. This enables auditing of assistant responses and accurate reconstruction of historical conversation trails across multiple sessions.

The best way to reconstruct prior conversation trails for debugging is to query the sessions.json index and individual <session-id>.jsonl files. Using rg and jq filters historical context from stored session logs to recover older prompts and assistant responses.

No external dependencies are required to use this session log search tool. It operates independently by relying on standard jq and rg command-line utilities to parse JSONL files directly from the local ~/.openclaw/agents/<agentId>/sessions path.

To retrieve historical context from older agent sessions, you parse the JSONL files located in the standard sessions directory. The tool indexes user and assistant messages across sessions to help you recall prior prompts and inform current decisions.

Session logs must be stored in JSONL format within per-session files and a sessions.json index. The conversation analysis tool specifically reads these structured files from the standard ~/.openclaw/agents/<agentId>/sessions path to parse and filter log data.