get-history

What problem does it solve?

For auditing, compliance, or deep analysis, access to the raw, unfiltered conversation history is essential. Main agent summaries can be insufficient or biased. This Skill provides direct access to the complete session logs, ensuring transparency and accuracy.

Core Features & Use Cases

• Direct Log Access: Retrieves the raw JSON Lines conversation file for the current session (.jsonl).
• Session ID Integration: Leverages the automatically injected session ID from the get-session-id hook for reliable access.
• Conversation Structure Parsing: Guides on using jq to extract specific event types (user messages, tool uses, tool results) and their content.
• Audit & Analysis Support: Enables verification of user approvals, extraction of tool call context (like working directories), and analysis of agent invocations.
• Use Case: During a compliance audit, use this Skill to retrieve the complete, raw conversation history. This allows an independent audit agent to verify protocol adherence, tool usage, and user approval checkpoints without relying on the main agent's potentially filtered view.

Quick Start

The session ID is automatically provided at SessionStart. Look for: ✅ Session ID: {uuid} Then, use it to access the conversation file: SESSION_ID="<your-session-id>" cat /home/node/.config/projects/-workspace/${SESSION_ID}.jsonl