ce-session-inventory

Discover session files and extract metadata from Claude Code, Codex, and Cursor platforms.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Zeptiny/opencode-setup --skill ce-session-inventory-zeptiny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-session-inventory
Source: https://github.com/Zeptiny/opencode-setup/tree/main/skills/ce-session-inventory
Command: npx skills add https://github.com/Zeptiny/opencode-setup --skill ce-session-inventory-zeptiny

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the discovery of session files and extraction of metadata across Claude Code, Codex, and Cursor platforms, making it easier to manage and analyze past coding sessions.

Core Features & Use Cases

  • Session File Discovery: Automatically locate session files across different platforms.
  • Metadata Extraction: Extracts session metadata such as timestamps, branch, working directory, and file size.
  • Use Case: When you need to review past coding sessions and quickly gather metadata without manually searching for each file.

Quick Start

Discover and extract metadata for sessions in the 'my-project' repository over the past 7 days:

skill ce-session-inventory my-project 7

Frequently Asked Questions about ce-session-inventory

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

FAQPage Schema
How do I discover session files across Claude Code, Codex, and Cursor automatically?

Session file discovery is automated by scanning platform directories to locate Claude Code, Codex, and Cursor session files without manual layout knowledge. The tool requires script execution to find and inventory coding session histories across these platforms.

How do I extract metadata from JSONL coding session files?

Metadata extraction from JSONL session files is handled by processing each file to pull timestamps, branch names, working directories, and file sizes. Running the script with a repository name and time range automates this extraction for agent research.

Can I gather session metadata for a specific repository over a custom time range?

Yes, gathering session metadata for a specific repository is supported by passing the repository name and a day count as arguments. For example, running the command with 'my-project' and '7' extracts metadata for sessions from the past 7 days.

What coding session metadata fields can I extract without manually searching files?

Extracted session metadata includes timestamps, git branch information, working directory paths, and file sizes. This data is pulled directly from discovered JSONL files across Claude Code, Codex, and Cursor platforms without manual searching.

Does this session inventory tool work with multiple coding platforms or just one?

The session inventory tool works across multiple platforms, specifically supporting Claude Code, Codex, and Cursor. It standardizes session file discovery and metadata extraction across all three platforms without requiring manual layout knowledge for each.

What are the limitations of automating session file discovery across different coding platforms?

Session file discovery requires script execution and processes JSONL files, meaning platforms must store sessions in that format. The tool is designed for agent research into session history and does not require manual layout knowledge but depends on compatible file structures.