← ClaudeAtlas

claude-sessionlisted

Find and inspect local Claude Code conversations by session GUID, title, phrase, or recent activity. Use when the user runs `/claude-session`, asks what Claude Code work they have been doing lately, says a Claude Code conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named conversation, or wants to continue it in Claude or Codex.
stewartcelani/skills · ★ 2 · AI & Automation · score 70
Install: claude install-skill stewartcelani/skills
# Claude Session Find persisted local Claude Code conversations on the current machine, inspect what happened, and recover the work. A handoff to a new Claude conversation or Codex is an optional use after the conversation is found and understood. ## What to Use ```text /claude-session What have I been working on lately? List recent local conversations. /claude-session <GUID> Inspect one known Claude Code conversation. /claude-session latest Inspect the most recent local conversation. /claude-session "Blah Blah" Find a conversation by title or a remembered phrase. ``` Use this when a prior Claude Code conversation died from context exhaustion, a crash, login or usage trouble, or an interrupted session. Its local transcript can still reveal the user intent, work completed, decisions, errors, referenced files, and last next step. ## Scope - Read Claude Code records stored in the current user's `.claude` directory: project transcripts, session metadata, history, and subagent files. - Work on Windows, macOS, and Linux. Resolve the default local directory from the current user's home directory, or pass `--claude-home` for a copied or mounted store. - Read a Desktop-driven remote conversation only if it was persisted by Claude Code in the same store. - Do not claim to read ordinary local Claude Desktop chat history; that is a separate application store and is not supported yet. ## Local Discovery Workflow ```text [recent | GUID | title | phrase]