Cctrace

cctrace

Export and import Claude Code sessions.

Claude Code stores conversation history in `~/.claude/projects//*.jsonl`. This tool extracts those sessions into portable formats for archival, analysis, or sharing.

What's New

**v2.0** adds portable sessions: export a session to your git repository, push it, and let someone else import it to continue where you left off. The original export functionality remains unchanged.

Two Modes of Operation

Classic Export

Exports to `~/claude_sessions/exports/` with timestamped directories. This is the original behavior and remains the default.

python3 export_claude_session.py

Produces:

~/claude_sessions/exports/2025-07-02_16-45-00_f33cdb42/
├── raw_messages.jsonl     # Original session data
├── conversation_full.md   # Human-readable markdown
├── conversation_full.xml  # Structured XML with full metadata
├── session_info.json      # Session metadata
└── summary.txt            # Statistics

Portable Export

Exports to `.claude-sessions//` within your repository. Designed to be committed and shared.

python3 export_claude_session.py --in-repo --export-name my-session

Produces:

.claude-sessions/my-session/
├── .cctrace-manifest.json    # Required for import
├── RENDERED.md               # Renders on GitHub
├── session/
│   ├── main.jsonl            # Session transcript
│   ├── file-history/         # File snapshots from undo history
│   ├── todos.json            # Todo state
│   └── plan.md               # Plan file if present
├── config/
│   ├── commands/             # Slash commands
│   ├── skills/               # Skills
│   └── ...                   # Other .claude/ config
└── [legacy files]            # For backwards compatibility

The portable export includes everything needed to resume the session: conversation history, file snapshots, todos, plans, and project-specific Claude Code configuration.

Importing a Session

...