Extract and recover content from Claude Code's session history files stored in ~/.claude/projects/.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionclaude-code-history-files-finderExecute the skills CLI command in your project's root directory to begin installation:
Fetches claude-code-history-files-finder from daymade/claude-code-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate claude-code-history-files-finder. Access via /claude-code-history-files-finder in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
784
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
784
stars
Extract and recover content from Claude Code's session history files stored in ~/.claude/projects/.
Session files are stored at ~/.claude/projects/<normalized-path>/<session-id>.jsonl.
For detailed JSONL structure and extraction patterns, see references/session_file_format.md.
Find all session files for a specific project:
python3 scripts/analyze_sessions.py list /path/to/project
Shows most recent sessions with timestamps and sizes.
Optional: --limit N to show only N sessions (default: 10).
Locate sessions containing specific content:
python3 scripts/analyze_sessions.py search /path/to/project keyword1 keyword2
Returns sessions ranked by keyword frequency with:
Optional: --case-sensitive for exact matching.
Extract files from session history:
python3 scripts/recover_content.py /path/to/session.jsonl
Extracts all Write tool calls and saves files to ./recovered_content/, preserving the original directory structure.
Filtering by keywords:
python3 scripts/recover_content.py session.jsonl -k ModelLoading FRONTEND deleted
Recovers only files matching any keyword in their path.
Custom output directory:
python3 scripts/recover_content.py session.jsonl -o ./my_recovery/
Get detailed session metrics:
python3 scripts/analyze_sessions.py stats /path/to/session.jsonl
Reports:
Optional: --show-files to list all file operations.
For detailed workflow examples including file recovery, tracking file evolution, and batch operations, see references/workflow_examples.md.
recover_content.py automatically keeps only the latest version of each file. If a file was written multiple times in a session, only the final version is saved.
Choose distinctive keywords that appear in:
Create descriptive output directories:
# Bad
python3 scripts/recover_content.py session.jsonl -o ./output/
# Good
python3 scripts/recover_content.py session.jsonl -o ./recovered_deleted_docs/
python3 scripts/recover_content.py session.jsonl -o ./feature_xy_history/
After recovery, always verify content:
# Check directory structure (files preserved in subdirectories)
find ./recovered_content/ -type f
# Read recovery report (shows full output paths)
cat ./recovered_content/recovery_report.txt
# Spot-check content (use actual path from report)
head -20 ./recovered_content/src/components/ImportantFile.jsx
✅ Files written using Write tool ✅ Code shown in markdown blocks (partial extraction) ✅ File paths from Edit/Read operations
❌ Files never written to disk (only discussed) ❌ Files deleted before session start ❌ Binary files (images, PDFs) - only paths available ❌ External tool outputs not captured in session
# Verify project path normalization
ls ~/.claude/projects/ | grep -i "project-name"
# Check actual projects directory
ls -la ~/.claude/projects/
Possible causes:
Solutions:
--show-edits flag to see Edit operationsFor sessions >100MB:
Session files may contain:
Always sanitize before sharing:
# Remove absolute paths
sed -i '' 's|~/|<home>/|g' file.js
# Verify no credentials
grep -i "api_key\|password\|token" recovered_content/*
Recovered content inherits sensitivity from original sessions. Store securely and follow organizational policies for handling session data.
After finding relevant session history, suggest continuing the work:
Found [N] relevant sessions with recoverable context.
Options:
A) Resume work — run /continue-claude-work to pick up where you left off (Recommended)
B) Just show me the content — I'll decide what to do with it
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
JuliusBrussee/caveman
asyrafhussin/agent-skills
shadcn/improve
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
wispbit-ai/skills
Registry listing for claude-code-history-files-finder matched our evaluation — installs cleanly and behaves as described in the markdown.
claude-code-history-files-finder fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
claude-code-history-files-finder is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added claude-code-history-files-finder from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: claude-code-history-files-finder is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: claude-code-history-files-finder is focused, and the summary matches what you get after install.
I recommend claude-code-history-files-finder for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
claude-code-history-files-finder reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: claude-code-history-files-finder is focused, and the summary matches what you get after install.
claude-code-history-files-finder has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 38