session-historian

Parse JSONL session logs from Codex and Claude for cross-session analytics.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/dismantl/agent-skills --skill session-historian-dismantl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-historian
Source: https://github.com/dismantl/agent-skills/tree/main/skills/session-historian
Command: npx skills add https://github.com/dismantl/agent-skills --skill session-historian-dismantl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the fragmented session history problem across Codex and Claude, eliminating the need to manually check separate log locations to track past work, debugging attempts, or project continuity across tools.

Core Features & Use Cases

  • Unified Session Access: Read and filter session logs from both Codex and Claude through a single interface.
  • Multi-Dimension Analysis: Search sessions by text, tool usage, or error occurrence, and generate cross-session reports on tool frequency, failure rates, or common commands.
  • Use Case: When debugging a recurring project error, use this Skill to quickly find all past sessions that encountered similar issues, view the commands run, and identify patterns across both tools.

Quick Start

Use the session-historian skill to find all sessions from the last 2 weeks that mention the 'handoff' workflow and list any errors that occurred in them.

Frequently Asked Questions about session-historian

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

FAQPage Schema
How do I search across Claude and Codex session history logs at the same time?

You can unify and search across Claude and Codex session history logs by parsing local JSONL files to normalize metadata, enabling filtered text search across both tools through a single interface.

What is the best way to track project continuity across multiple AI coding tools?

Tracking project continuity across AI coding tools involves parsing fragmented JSONL session files to normalize metadata, allowing you to filter past sessions by text, tool usage, or error occurrences.

Can I find past Codex or Claude sessions that encountered a specific error?

Yes, you can find past sessions that encountered specific errors by searching filtered session logs, generating cross-session reports on tool frequency and failure rates to identify recurring patterns.

Does this session history analysis require any external dependencies?

No external dependencies are required to analyze session history; the Skill relies solely on executable Python scripts to parse local JSONL files stored in user directories.

How do I generate cross-session analytics for AI coding workflows?

Generating cross-session analytics for AI coding workflows involves parsing and normalizing JSONL session logs to produce reports on tool frequency, failure rates, and common commands across both Claude and Codex.

What format are Codex and Claude session logs stored in for cross-tool analysis?

Codex and Claude session logs are stored locally as JSONL files, which are parsed and normalized across tool-specific formats to enable unified cross-tool analysis.