Feature request: Session portability across machines
Status Closed — duplicate
Maintainer reply None cached
Workaround ✓ Mentioned in description ↑
Activity 3 comments · opened Mar 18, 2026 · 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.mdfiles can carry project context, but not the actual conversation historyclaude --resumeonly works on the same machine- There is no
--export/--importmechanism for sessions
Proposed solution
Any of the following would help:
- Export/import commands —
claude --export <session_id> > session.jsonandclaude --import session.json - Session sync — Optional cloud sync of conversation history (like claude.ai already does for web)
- 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.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗