ce:sessions

Search and synthesize past AI coding sessions across Claude Code, Codex, and Cursor.

6|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/Jerrylalala/compound-engineering --skill ce-sessions-jerrylalala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce:sessions
Source: https://github.com/Jerrylalala/compound-engineering/tree/main/plugins/compound-engineering/skills/ce-sessions
Command: npx skills add https://github.com/Jerrylalala/compound-engineering --skill ce-sessions-jerrylalala

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When debugging or planning new work, developers often forget what was already tried in previous AI assistant sessions. This Skill searches historical session transcripts across Claude Code, Codex, and Cursor to surface what was attempted, what failed, and what decisions were made, so you never repeat dead ends. ## Core Features & Use Cases - Cross-platform session discovery: Finds JSONL session files from Claude Code, Codex, and Cursor filtered by repo, time window, and git branch. - Keyword-based relevance filtering: Ranks sessions by keyword matches in actual user/assistant text, excluding tool outputs and metadata noise. - Skeleton and error extraction: Condenses multi-megabyte transcripts into compact conversation skeletons and error logs without loading full files into context. - Subagent synthesis: Dispatches a historian subagent to summarize findings into sections like what was tried, what didn't work, and key decisions. - Use Case: Before fixing a recurring auth bug, ask what was tried last week and get a summary of prior debugging attempts across all your AI tools. ## Quick Start Ask the assistant to search your session history for what was tried when debugging the auth middleware last week.

Frequently Asked Questions about ce:sessions

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

FAQPage Schema
How do I search my Claude Code session history?▼

Invoke the skill with a question or topic, and it discovers JSONL session files under ~/.claude/projects matching your repo, filters by branch and keywords, then synthesizes findings. Sessions are never loaded in full; extraction scripts produce compact skeletons first.

Can I search sessions across Claude Code, Codex, and Cursor at once?▼

Yes, the discovery script scans all three platforms by default: Claude Code projects, Codex session directories, and Cursor agent transcripts. You can restrict to one platform with the --platform flag on the discovery script.

How far back does session history search go?▼

The scan window is inferred from your question, ranging from 1 day to 90 days. Claude Code retains sessions for roughly 30 days by default, so wider windows may return nothing unless retention was extended.

Why does session search return no relevant prior sessions?▼

This happens when no session files exist in the time window, the branch filter matches nothing, and keyword filtering finds zero matches in user or assistant text. It can also occur if sessions belong to a different repo directory than the one being scanned.

Does session extraction include tool outputs and thinking blocks?▼

No, extraction deliberately excludes tool call inputs and outputs, thinking blocks, and encrypted reasoning content. Only user and assistant text is summarized, protecting context size and avoiding noise from credentials or internal reasoning.