Chat Package Export/Import: Git-compatible format for team collaboration

Problem

Claude Code conversations are currently stored locally in ~/.claude/projects/ and cannot be shared with team members. This limits collaboration scenarios:

• Knowledge sharing - Can't share valuable debugging sessions or architectural discussions with the team
• Code review context - Can't show teammates the reasoning behind implementation decisions
• Onboarding - Can't provide new team members with example conversations demonstrating best practices
• Continuity - Can't hand off an in-progress conversation to another team member
• Documentation - Can't preserve important conversations in the repository as living documentation

Proposed Solution

Add "Chat Package" export/import functionality that allows conversations to be saved in a git-compatible format and resumed by any team member.

Key capabilities:

1. Export - Save a chat conversation to a portable format in the repository
2. Import - Load an exported chat and continue the conversation from that state
3. Git-compatible - Text-based format (JSONL/JSON) that works with version control
4. Resumable - Full conversation state, not just read-only transcript
5. Deep linkable - Can be referenced via URI (works with #10366)

Proposed workflow:

# Export important chat to repo
claude-code export-chat abc123-def456 .roundtable/chats/architecture-decision.jsonl

# Commit to git
git add .roundtable/chats/architecture-decision.jsonl
git commit -m "Add architecture decision chat for reference"

# Teammate clones repo and opens chat
# Click link: vscode://anthropic.claude-code/chat/repo/architecture-decision
# Or import manually: claude-code import-chat .roundtable/chats/architecture-decision.jsonl

Directory structure example:

.roundtable/chats/
├── architecture-decision-2025-10-26.jsonl
├── bug-investigation-auth.jsonl
├── feature-planning-mobile.jsonl
└── README.md  # Index of important chats

Use Cases

Team collaboration:

• Share conversation in GitHub issue: "See design discussion: vscode://anthropic.claude-code/chat/repo/architecture-decision"
• Team member clicks link, chat opens in their Claude Code
• They can review the conversation and continue it with new questions

Code review:

• Export chat showing how you arrived at a solution
• Reviewers can see your reasoning process
• Reviewers can fork the conversation to explore alternatives

Documentation:

• Preserve important troubleshooting sessions in the repo
• Create "example conversations" for common tasks
• Living documentation that can be continued/updated

Onboarding:

• New developers import example chats
• Continue conversations to learn interactively
• See how experienced developers use Claude Code

Implementation Considerations

Export format options:

Option 1: Direct JSONL copy

• Use same format as ~/.claude/projects/ files
• Pro: No format conversion needed
• Con: May include sensitive local paths/data

Option 2: Portable format

• Strip/sanitize sensitive data (file paths, API keys)
• Normalize paths to be project-relative
• Pro: Safe to share
• Con: Requires format conversion

Import behavior:

Option A: Fork (create new local chat)

• Import creates a new chat in ~/.claude/projects/
• User continues their own copy
• Multiple people can work independently

Option B: Direct reference (shared state)

• Claude Code reads directly from .roundtable/chats/ file
• Updates append to the repo file
• Everyone shares the same conversation state
• Requires handling merge conflicts

Deep linking integration:

vscode://anthropic.claude-code/chat/local/{sessionId}    # Local chat
vscode://anthropic.claude-code/chat/repo/{filename}       # Repo chat package

Privacy/security considerations:

• Option to redact specific messages before export
• Auto-strip sensitive patterns (API keys, credentials, absolute paths)
• Confirmation prompt showing what will be exported
• .gitignore patterns for sensitive chats

Related Features

• Depends on or complements #10366 (Deep linking for local chats)
• Could integrate with chat history search/filtering
• Could support selective message export (not just full conversation)