sugarforever/claude-session-manager
Manage Claude Code session transcripts from local JSONL storage, including listing candidate sessions, exporting full or selected sessions to organized Markdown, inspecting archives, and summarizing tool-call history. Use when the user asks to scan, parse, archive, inspect, recover, summarize, manage, or convert Claude Code sessions, `~/.claude/projects` data, `.jsonl` transcripts, tool-call history, or hard-to-read Claude Code conversation logs.
npx skills add https://github.com/sugarforever/01coder-agent-skills --skill claude-session-manager
Claude Code stores session transcripts as JSONL files under ~/.claude/projects/<project-key>/<session-id>.jsonl. Use the bundled manager to list candidates or export sessions into project-organized Markdown transcripts with a digest, a clean user/Claude conversation, and linked tool-call details.
Default output folder: ~/.claude/session-markdown. Tell the user before exporting there, and mention any custom output folder they requested.
Let the user's wording choose the mode when it is clear; otherwise ask them to choose before exporting:
Run from any directory:
python3 /path/to/claude-session-manager/scripts/manage_claude_sessions.py
Equivalent explicit form:
python3 /path/to/claude-session-manager/scripts/manage_claude_sessions.py \
--source ~/.claude/projects \
--output ~/.claude/session-markdown
Useful options:
--mode full: export all matching sessions. This is the default.--mode specific --list-candidates: print a numbered candidate table and do not export.--mode specific --pick N: export the Nth candidate from the same filtered candidate list.--project <text>: only export project folders whose key contains this text.--session <text>: only export sessions whose id or filename contains this text.--since YYYY-MM-DD: only export sessions modified on or after this date.--limit N: export the N most recently modified matching sessions.--include-tool-details-inline: embed full tool inputs/results in the main session Markdown. By default, the main transcript keeps compact collapsible tool summaries and links full payloads through the sidecar file.Use this flow when the user wants one session, is unsure which session they need, or asks to inspect recent sessions before converting.
--limit 20 by default unless the user asks for a different count.python3 /path/to/claude-session-manager/scripts/manage_claude_sessions.py \
--mode specific \
--list-candidates \
--limit 20
python3 /path/to/claude-session-manager/scripts/manage_claude_sessions.py \
--mode specific \
--list-candidates \
--project my-repo \
--since 2026-06-01 \
--limit 20
--pick N:python3 /path/to/claude-session-manager/scripts/manage_claude_sessions.py \
--mode specific \
--pick 3 \
--limit 20
If the user already gives an exact session id or unique fragment, use --mode specific --session <id-or-fragment> --list-candidates first when there is any ambiguity. Export with --pick 1 only when the candidate list has exactly one match.
The exporter writes:
~/.claude/session-markdown/
├── index.md
└── <project-key>/
├── index.md
├── <session-id>.md
└── tool-details/
└── <session-id>.tools.md
Keep the original Claude project key as the folder name. It is stable and avoids guessing at path decoding.
Each session Markdown includes:
## Timeline section as numbered third-level headers in ISO-8601 format: ### N. user - <ISO> for user turns and ### N. assistant - <ISO> for assistant turns.<tool_call_000001> Bash - command: npm test - result inside the relevant assistant turn, with matching sections in the sidecar details file by default.### N. attachment - <ISO>, ### N. permission-mode, ### N. file-history-snapshot, ### N. last-prompt, etc.) and [thinking] blobs in assistant turns are emitted as their own numbered events in the timeline. Readers should skip them as noise; they do not carry conversation content.<tool_call_000001> reference as a pointer into tool-details/<session-id>.tools.md.~/.claude/projects.~/.claude/session-markdown.--pick..jsonl files.Take sugarforever/claude-session-manager from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.