How do I install the Session Recovery skill?

Run npx skillmds add majiayu000/session-recovery-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Session Recovery safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Session Recovery?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Session Recovery free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Session Recovery?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Session Recovery by majiayu000 — Agent Skill

Name: Session Recovery
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

Claude Code Session Recovery Skill

Quick Reference

When to use this skill:

"No conversations found to resume" when running claude -r
New conversations not creating session files
Sessions appearing in wrong locations (/tmp/ instead of ~/.claude/projects/)
Session history missing after environment changes
IDE/terminal settings affecting session creation
Need to migrate or recover 600+ legacy sessions

Official Session Storage

Standard Location: ~/.claude/projects/

Structure:

~/.claude/projects/
├── -home-username-my-project/     # Encoded absolute path
│   └── 364695f1-13e7-4cbb-ad4b-0eb416feb95d.jsonl
└── -tmp-another-project/
    └── a8e39846-ceca-421d-b4bd-3ba0eb1b3145.jsonl

Format: One JSON event per line (JSONL), UUID-based filenames

Critical Pitfall: HOME Variable

Problem

Claude Code uses $HOME environment variable to determine session storage location. If $HOME is incorrect, sessions go to wrong directory or disappear.

Symptoms

claude -r shows "No conversations found to resume"
New conversations work but files don't appear in expected location
Sessions found in /tmp/ or other unexpected paths
Works on one machine but not another

Diagnosis

/usr/bin/env bash << 'PREFLIGHT_EOF'
# Step 1: Check current HOME
echo "Current HOME: $HOME"

# Step 2: Check system expectation
echo "Expected HOME: $(getent passwd $(whoami) | cut -d: -f6)"

# Step 3: Find where Claude is actually writing
find /tmp -name "*.jsonl" -path "*/.claude/projects/*" 2>/dev/null
PREFLIGHT_EOF

Reference Documentation

For detailed diagnostic steps and solutions, see:

Troubleshooting Guide - Detailed diagnostic procedures and fixes

---name: session-recovery-2description: Troubleshoot Claude Code session issues. Use when encountering "No conversations found" errors, missing sessions, or session file corruption problems.--- # Claude Code Session Recovery Skill ## Quick Reference **When to use this skill:** - "No conversations found to resume" when running `claude -r` - New conversations not creating session files - Sessions appearing in wrong locations (`/tmp/` instead of `~/.claude/projects/`) - Session history missing after environment changes - IDE/terminal settings affecting session creation - Need to migrate or recover 600+ legacy sessions ## Official Session Storage **Standard Location:** `~/.claude/projects/` **Structure:** ``` ~/.claude/projects/ ├── -home-username-my-project/ # Encoded absolute path │ └── 364695f1-13e7-4cbb-ad4b-0eb416feb95d.jsonl └── -tmp-another-project/ └── a8e39846-ceca-421d-b4bd-3ba0eb1b3145.jsonl ``` **Format:** One JSON event per line (JSONL), UUID-based filenames ## Critical Pitfall: HOME Variable ### Problem Claude Code uses `$HOME` environment variable to determine session storage location. If `$HOME` is incorrect, sessions go to wrong directory or disappear. ### Symptoms - `claude -r` shows "No conversations found to resume" - New conversations work but files don't appear in expected location - Sessions found in `/tmp/` or other unexpected paths - Works on one machine but not another ### Diagnosis ```bash /usr/bin/env bash << 'PREFLIGHT_EOF' # Step 1: Check current HOME echo "Current HOME: $HOME" # Step 2: Check system expectation echo "Expected HOME: $(getent passwd $(whoami) | cut -d: -f6)" # Step 3: Find where Claude is actually writing find /tmp -name "*.jsonl" -path "*/.claude/projects/*" 2>/dev/null PREFLIGHT_EOF ``` --- ## Reference Documentation For detailed diagnostic steps and solutions, see: - [Troubleshooting Guide](./TROUBLESHOOTING.md) - Detailed diagnostic procedures and fixes

Frequently asked questions