# Claude Code

How the Claude Code export works, from connecting to fixing problems.

## Connect

Press "connect" on the Claude Code card. The panel opens in your `.claude` folder, hidden files shown: press "Select this folder". Exporter reads the `projects` folder inside it and nothing else. Then press "select export folder".

## Where the files go

One Markdown note per session under a folder per project, named by the session's start and its title (`wander.md/2026-08-23 2233 fix the changelog header link.md`). The original log is copied to `originals/<project>/<id>.jsonl`. Pasted images land in `<project>/attachments/`.

## What is exported

The sessions ticked on the card. The pills only filter the list: recent (newest first), busiest (most prompts first) and running (the log moved in the last two minutes). The search field matches a session's title, its first prompt and its project.

"saves to" chooses the format: markdown, the original, or both. A session's title is the name you gave it with `/rename`, else the title Claude Code chose, else the first prompt.

## Format

Markdown: front matter, then a paragraph per turn with the time and a block id. Tool calls are fences with what they ran, edits are diff fences, pasted images are embeds. Thinking, tool results, snapshots and the harness's own notices never land in the note.

## The file

| key | holds |
| --- | --- |
| `agent`, `session` | `claude-code` and the session id |
| `title`, `project`, `cwd`, `branch` | what the session was about and where |
| `model`, `version` | the model and the Claude Code version |
| `started`, `ended` | the first and last line's time |
| `turns`, `prompts`, `tools` | how much happened |
| `tokens_in`, `tokens_out` | fresh input and output, cache reads left out |
| `files` | the files the session edited or wrote |

```markdown
**you** · 22:33 ^turn-1

see the changelog page, the header link goes to /contact

**claude** · 22:34 ^turn-2

I'll look at the live page first.

```tool Bash "find docs route" ^toolu_01A
ls src
```
```

## Free and unlocked

Your 50 most recent sessions are free, and they stay free. A session Claude Code deleted keeps its files ([pricing](https://exporter.dev/pricing)).

## Sync and full resync

After the first "sync now", a running session rewrites its note as the log grows, and only logs that changed are read again.

"full resync" asks first, then removes the session files Exporter wrote and exports again what Claude Code still has. Sessions Claude Code already deleted do not come back: back up the folder before you ever press it.

## Problems and fixes

- "no session logs in that folder (pick the .claude folder in your home)": press "connect" again and select the folder the panel opens in
- a session is missing: it is unticked, or it is a subagent's log, which folds into its parent
- new sessions stop arriving: the free 50 are used. Unlock Claude Code and press "sync now"
- a note is empty: the session has no prompt yet, only Claude Code's own records

## Related

- [Claude Code](https://exporter.dev/claude-code): Every session as a note, the original kept
- [Claude Code guides](https://exporter.dev/guides/claude-code): Keep every session as a note
- [MCP server](https://exporter.dev/docs/mcp): Connect Claude and other agents

---

human version: https://exporter.dev/docs/claude-code
every page: https://exporter.dev/llms.txt