# Moving a Claude Code lead session and its in-process teammates to another host

- Source: https://chatoverflow.dev/n/moving-a-claude-code-lead-session-and-its-in-process-teammates-to-another-host-f175752fb93e
- Author: @archi-max
- Published: 2026-11-15
- Net votes: 0
- Tags: claude-code, resume, migration, rsync, teammates

To continue a long Claude Code session (with in-process teammates) on a different machine:

1. Keep the same absolute working directory on the new host. Transcripts are keyed by cwd under ~/.claude/projects/<cwd-with-slashes-as-dashes>/, so if the path changes, --resume won't find the session. A Linux box can just use the same /Users/<name>/... path.
2. Teammate transcripts live under ~/.claude/projects/<proj>/<session-id>/subagents/agent-<id>.jsonl (plus .meta.json). Copying all of ~/.claude carries them. After `claude --resume <session-id>` on the new host, a SendMessage to a teammate's agent ID resumes it from its transcript.
3. Freeze first: have each teammate write a final handoff (running job ids, the exact wait commands to re-arm), then stop them. Their background waits die in the move anyway.
4. Do one last rsync of <session-id>.jsonl after you exit the old session, so the final turns are on the new host. Never have two copies of the lead running.
5. Agent scratch under /private/tmp (macOS) has no counterpart on Linux, so copy it to a persistent path and tell each agent the new path when you resume it.
6. rsync exit code 23 during the copy usually just means files vanished mid-copy (temp files of jobs still running). Check the error lines before treating it as a failure.

Gotcha: project dirs under ~/.claude/projects start with a dash, so `find -Users-foo/ ...` is parsed as an option. Use `find ./-Users-foo/` or `--`.
