Feature request: Session portability across machines

Resolved 💬 3 comments Opened Mar 18, 2026 by kedimbilir Closed Mar 22, 2026

Problem

Claude Code conversation history is stored locally in ~/.claude/ and cannot be transferred to another machine. This means when switching between computers (e.g., home and work), users lose all conversation context and history.

For a CLI tool, this is an unexpected limitation — CLI tools are generally expected to be more portable, not less.

Current workarounds

  • CLAUDE.md files can carry project context, but not the actual conversation history
  • claude --resume only works on the same machine
  • There is no --export / --import mechanism for sessions

Proposed solution

Any of the following would help:

  1. Export/import commandsclaude --export <session_id> > session.json and claude --import session.json
  2. Session sync — Optional cloud sync of conversation history (like claude.ai already does for web)
  3. Portable session files — Store session data in the project directory (opt-in), so it travels with the project

Use case

Users who work on the same project from multiple machines (desktop + laptop, home + office) and want to continue conversations seamlessly.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗