pi-session-reader

You can monitor Pi agent activity by locating the latest JSONL session file and using jq to parse the final message, extracting the role and stopReason fields to determine whether the agent is currently busy or idle.

Read Pi agent session history by using the tail command on the JSONL session file and piping the output through jq to filter message types and extract conversational roles along with their text content for audit or debugging review.

Check agent status across projects by listing JSONL session files sorted by modification time within each project directory, then extracting the stopReason from the latest file to quickly assess busy or idle states.

Parsing JSONL session files with jq filters message entries by type and extracts structured fields like role, content arrays, and stopReason, converting raw session logs into readable conversation histories and status indicators.

Yes, you can retrieve recent conversation history by using the tail command with a line count on the JSONL session file, then piping only those last lines through jq to extract and format the message roles and content snippets.

Monitoring agent sessions requires only standard command-line utilities like ls, tail, and jq to locate and parse JSONL files, needing no external libraries or frameworks to review Pi agent activity and status.