session-logs

To search past conversation logs in JSONL format, you can use command-line tools like jq and rg to filter and extract historical context, user messages, and assistant responses from session files. This enables quick retrieval of previous interactions.

Yes, you need jq and ripgrep installed to analyze session history. These command-line tools are required dependencies for efficient JSONL log parsing and pattern matching when retrieving cost data and conversation transcripts.

You extract specific user messages and assistant responses from JSONL session files by utilizing jq to parse the structured data and rg to match patterns. This allows you to filter transcripts and summarize information from agent sessions.

The best way to retrieve historical context from previous agent sessions is querying the JSONL logs stored in your agents directory. Using jq and rg for pattern matching allows you to quickly find specific discussions and decisions from past conversations.

Yes, you can analyze cost data and tool usage from past conversation logs. The session-logs capability utilizes jq to filter and summarize this information directly from the JSONL transcripts stored in your local agent session directories.

Limitations of using command-line tools for session log analysis include the requirement to have jq and ripgrep installed. Additionally, you must manually construct search patterns to query the raw JSONL files rather than using a visual interface.