Resume a Claude Code session from another account: shared history with ships

Short answer: Claude Code keeps each account's session history in that account's config folder, under projects/. So --resume on one login only sees the sessions that login started. To resume a session from another account, both logins need the same projects/ folder. crewrota calls that shared folder a ship: put two members on one ship with crew ship join, and --resume or /resume in either one finds the sessions of both. I use several Claude logins, for my job and for my own projects, each in its own config folder. I wrote about that setup in Switch Claude Code accounts without logging out. This post is about the part that setup leaves split: the history. The problem: each account keeps its own history Each login kept its own history, so --resume on one account could not find a session I had started on another. That is not a bug. It follows from where sessions live. The data usage page says: "Claude Code clients store session transcripts locally in plaintext under ~/.claude/projects/ for 30 days by default to enable session resumption." The sessions page gives the exact place: one JSONL file per session, at ~/.claude/projects//.jsonl, where is your working folder's path with every character that is not a letter or digit turned into -. Now add a second account. CLAUDE_CONFIG_DIR moves Claude Code to another folder, and the env vars page says "All settings, session history, and plugins are stored under this path." So the second login writes its sessions to its own projects/ folder, and its --resume picker reads from there. The other account's sessions sit one folder over, and Claude Code does not look there. How to resume a Claude Code session from another account To resume a Claude Code session from another account, give both logins the same projects/ folder. With crewrota, make a ship, put both members on it, then start the second member with --resume: crew ship create home crew ship join main home crew ship join side home crew side -- --resume The joins put main and side on the ship home; if you skip crew ship create, the join asks to create it. The last line starts Claude Code as side and passes --resume on, so the picker lists the sessions main started in that project folder too. Inside a running session, /resume finds them the same way. The picker starts with the current worktree, and Ctrl+A widens it to every project. The docs guide Share history between members with a ship walks through every ship command, from create to delete. Here is the second join on a demo crew where each member already had one session: PS E:\demo-crew-b04> crew ship join side home [i] Copied this member's history into the ship. The original folder is kept at E:\demo-crew-b04\home\.crewrota\members\side\projects.before-crewrota-20261103 side shares history through ship home. After that, side's own projects folder holds both sessions, its own and the one main started. What Claude Code already gives Claude Code can already open a transcript by path. The sessions page lists claude --resume , which "Resumes the session stored in the .jsonl transcript file at that absolute path". The page does not cover a file in another account's folder. It is one session at a time, and the next one lands in the other folder again. To share Claude Code history between accounts all the time, the folder itself has to be shared. What a ship shares A ship is a folder under ~/.crewrota/ships//. Each member on it links five folders to the ship: projects, todos, file-history, session-env and shell-snapshots. The link is a junction on Windows and a symlink elsewhere. projects holds the transcripts and Claude Code's auto memory, so members on a ship share history and memory. crew ship join puts a member on a ship. The member's existing history is copied into the ship, and its old folder is kept beside it, renamed, not deleted. crew add --ship makes a new member straight onto a ship. Without --ship, crew add asks "Share history with other members?" and offers to keep it isolated, join a ship or create one. crew ship leave makes a member isolated again, with an empty history folder. The ship keeps its files. A ship also carries MCP servers, kept in its mcp.json and given to each member at launch. crew ship mcp list|add|remove manages them, and a new ship starts with a copy of the servers in your ~/.claude.json. crew backup takes every ship to a new machine; see Move Claude Code to a new computer. When to keep members on separate ships Sharing is a choice per member, and isolated is the default in crew add. Every member on a ship sees its transcripts, memory and MCP servers with their keys. In the demo crew above, main and side share the home ship, and team sits alone on work. Work history stays with work, and your own projects stay with you. Your accounts and Anthropic's terms crewrota is for one person using their own Claude subscriptions. Each member logs in through Claude Code's own login. crewrota never copies or moves a login; to read usage, quota-axi uses each member's own sign-in on your machine. A ship shares history, never a login. crewrota runs the real claude program; nothing goes through a proxy. Read Anthropic's Consumer Terms and Usage Policy for your plan before you use more than one account. Questions about crewrota Can I resume a Claude Code session from another account? Yes, when both accounts read the same history folder. Claude Code keeps sessions under each config folder's projects/, so put both crewrota members on one ship with crew ship join, and --resume or /resume in either one finds the sessions of both. Which folders does a ship share? Five: projects, todos, file-history, session-env and shell-snapshots. Each member links them to the ship's folder. Logins stay in each member's own folder. Does joining a ship delete a member's own history? No. Its existing history is copied into the ship, and the old folder is kept beside it under a new name. crew ship leave makes the member isolated again, and the ship keeps its files. Is crewrota free? Yes. crewrota is open source under the MIT license, on npm and GitHub. Windows is the main platform; macOS and Linux are in beta. If you try ships and something does not show up in --resume, I'd like to hear about it: open an issue on GitHub.