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.

Produces:

Portable Export

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

Produces:

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

Someone clones your repo and wants to continue your session:

What Import Does

1. Validates the export has a .cctrace-manifest.json
2. Creates a pre-import snapshot for recovery
3. Generates a new session ID (your local sessions remain unaffected)
4. Rewrites internal UUIDs while preserving message threading
5. Updates cwd paths to the local project directory
6. Copies session file to ~/.claude/projects//
7. Imports auxiliary data (file-history, todos, plans)
8. Imports config files (commands, skills, hooks, agents, rules)

What Import Preserves

Certain fields are cryptographically signed or tied to Anthropic's API and must not be modified:

- message.id (Anthropic message ID)
- requestId (Anthropic request ID)
- signature in thinking blocks
- tool_use.id (tool invocation ID)

These are left untouched. Only the session-local identifiers (sessionId, uuid, parentUuid, agentId,…