Keep every Claude Code session

Steps

1. Connect Claude Code. Press “connect” on the Claude Code card. The panel opens in your .claude folder with hidden files shown: press “Select this folder”. Exporter reads the projects folder inside it and nothing else.
2. Pick where the notes go. Press “select export folder”. A folder inside a vault is used as it is; a folder right in your home gets a claude-code-sessions-export folder inside it.
3. Choose the format. On the “saves to” line pick markdown, the original, or both. Both is the default: the note to read, the log to restore.
4. Press “sync now”. Every session becomes a note under a folder per project, named by its date, time and title. A session that is running right now rewrites its note as you go.
5. Find one later. The search field on the card matches a title, a first prompt or a project; the “running” pill shows what is live, “busiest” the longest sessions.

What you get

One note per session: front matter with the project, the branch, the model, the times, the counts and the files the session touched, then a paragraph per turn with the time and a block id. Tool calls are short fences with what they ran, edits are diff fences, pasted images are files beside the note. Thinking, tool results and the harness’s own notices are left out, so the note reads like the conversation did. The original JSONL log sits under originals/, byte for byte. Copy it back into ~/.claude/projects and claude --resume finds the session again, long after Claude Code has purged it.

Pitfalls

• Sessions hold what you pasted into them, tokens and terminal output included. Export into a folder you trust, or one that does not sync to a shared vault.
• Your 50 most recent sessions are free. Older ones need the one-time unlock, and a session Claude Code deleted keeps its files either way.
• A subagent’s log is not a session of its own; it folds into its parent. If a session looks short, its work may have run in subagents.