session-logs

Search and analyze local agent session JSONL history for prior messages.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/nomad3/openclaw-k8s --skill session-logs-nomad3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-logs
Source: https://github.com/nomad3/openclaw-k8s/tree/main/package/skills/session-logs
Command: npx skills add https://github.com/nomad3/openclaw-k8s --skill session-logs-nomad3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You need to answer questions about what was said earlier in a prior or parent conversation, but that context is not available in the current chat memory.

Core Features & Use Cases

  • Session log discovery: Locates and enumerates session JSONL transcripts stored per agent under the OpenClaw session directory.
  • Targeted message extraction: Extracts user and assistant text from JSONL by role and filters for readable text content.
  • Cross-session analysis: Searches within sessions for keywords and computes per-session totals such as message counts and cost.

Quick Start

Ask the skill to search across your session JSONL logs for a specific phrase related to the question you asked earlier.

Frequently Asked Questions about session-logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search conversation history from older agent chats?

To search conversation history from older agent chats, you can scan locally stored JSONL session transcripts using keyword search to retrieve prior user and assistant messages for contextual answers.

Can I use jq to extract specific messages from session logs?

Yes, you can use jq to extract specific messages from session logs by filtering JSONL transcript structures based on message roles and readable text content fields.

What is the best way to analyze past decisions in parent conversations?

The best way to analyze past decisions in parent conversations is to locate and enumerate session JSONL transcripts stored per agent, then search within those sessions for keywords related to the historical context.

Does this approach work with the sessions.json index for cost analysis?

Yes, this approach works with the sessions.json index to compute per-session totals such as message counts and cost analysis by applying jq and rg against the stored transcript structure.

How do I debug what occurred before in earlier chats when context is lost?

To debug what occurred before in earlier chats when context is lost, search the local agent session directory to retrieve prior user and assistant messages directly from the JSONL history.

Are there limitations when searching JSONL session logs for cross-session analysis?

A limitation when searching JSONL session logs for cross-session analysis is that the history must be locally stored under the OpenClaw session directory, as prior context is not available in current chat memory.