ce-session-inventory

Extract session metadata from Claude Code, Codex, and Cursor JSONL logs.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-session-inventory-diestok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-session-inventory
Source: https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026/tree/main/.agents/skills/compound-engineering/skills/ce-session-inventory
Command: npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-session-inventory-diestok

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a unified, automated way to locate session transcripts across Claude Code, Codex, and Cursor, and emit structured metadata for each session to support indexing, searching, and auditing.

Core Features & Use Cases

  • Cross-platform discovery scans session stores for three platforms to collect per-session data such as timestamps, session IDs, file paths, and platform origin.
  • Structured metadata output outputs per-session JSON objects and a final _meta summary for pipeline consumption, enabling downstream filtering and ranking.
  • Optional filtering and keyword scoring supports a cwd-filter to prune results by repository, and a keyword scoring mode to prioritize relevant sessions.

Quick Start

Run the included discovery scripts to scan for session logs and emit per-session metadata in JSONL format.

Frequently Asked Questions about ce-session-inventory

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

FAQPage Schema
How do I extract session metadata from Claude Code, Cursor, and Codex logs?

Session metadata extraction scans platform-specific JSONL stores to emit structured fields like platform, ts, session, file, and size. It parses each session format and outputs one JSON object per session, plus a final _meta summary line for pipeline consumption.

What is the best way to inventory AI agent session files across multiple repositories?

Inventorying AI agent session files across repositories requires unified discovery scripts that parse JSONL session stores. This approach extracts per-session data such as timestamps, session IDs, file paths, and platform origin into structured JSONL format for indexing and auditing.

Can I filter session logs by repository directory and keywords?

Filtering session logs by repository is supported through the optional --cwd-filter to prune results to a specific working directory. The --keyword option enables keyword scoring mode to prioritize and rank relevant sessions within the structured output.

Does extracting session transcripts work across Claude Code, Codex, and Cursor platforms?

Extracting session transcripts works across Claude Code, Codex, and Cursor platforms by scanning their specific JSONL stores. The discovery scripts parse each platform's unique format to collect structured metadata including optional fields like branch, cwd, and model.

What format are the extracted session metadata files output in?

Extracted session metadata files are output in JSONL format, with one JSON object per session followed by a final _meta summary line. This structured output enables downstream filtering, ranking, and pipeline consumption for auditing purposes.

What fields are included when parsing AI coding session logs?

Parsing AI coding session logs emits structured fields including platform, ts, last_ts, session, file, and size, alongside optional fields like branch, cwd, and model. These fields support comprehensive indexing and auditing of session transcripts across platforms.