Switch Claude Code Accounts Without Losing Your Conversation
Hitting a limit on one account does not have to end the task. Claude Code keeps conversations on your computer, so you can sign in with another account and reopen the same thread. Here is where those files live and which command brings the conversation back.
Where Claude Code stores conversations
Claude Code saves session transcripts locally under ~/.claude/projects. They are files on your machine. Each project folder gets its own history, which is why the continue command can find the right conversation when you run it from that folder.
Changing accounts does not delete these files. The transcript stays where it is, and the next session can read it again.
Switch accounts with /login
Inside Claude Code, run /login and sign in with the other account. The plan and the limits that apply are the ones on the account you are signed into.
The conversation itself is still local. After signing in, open the same project folder in a terminal and continue the thread with the command below. You do not need to copy the chat or rebuild the context by hand.
Continue with --continue or --resume
Claude Code has two ways to reopen local history:
claude --continue(or-c) continues the most recent conversation in that folder.claude --resume(or-r) lets you choose a conversation from a list, or pass a session id.
claude --continue
claude --resume
Run either command from the project directory. --continue is the quick path when you only have one recent thread; --resume is better when you have several and want to pick the right one.
Tip: Before you switch, write one line about where you stopped and what comes next. It costs a few seconds and saves you from rereading the last twenty turns on the other account.
Keep the usage terms in mind
Using more than one account is your choice, but Anthropic's usage terms still apply. A different account has its own plan and its own limits; switching is a way to continue working, not a way around the limits attached to each account.
How Foxpit handles a limit
Foxpit is a desktop app that runs Claude Code, Codex and OpenCode as one team. It uses your own subscriptions and does not resell or work around limits. When Claude Code hits its 5-hour limit, you do not have to watch the clock:
- Fox parks the turn. The lead agent pauses, and the app shows the reset time.
- It resumes by itself. At the reset, Foxpit sends "continue" so the same conversation picks up without you typing anything.
- Usage panel. One panel shows remaining quota and reset time for every agent that reports it.
Related: see what to do when the Claude Code limit hits and running Claude Code and OpenCode together.
Frequently asked questions
Does switching accounts delete my Claude Code conversation?
No. Conversations are stored locally under ~/.claude/projects. After /login with the other account, open the same folder and run claude --continue to reopen the most recent conversation.
What is the difference between --continue and --resume?
claude --continue (-c) reopens the most recent conversation in the current folder. claude --resume (-r) lets you choose from a list or pass a session id.
Can I switch accounts in the middle of a task?
Yes. Note the current step, run /login, sign in with the other account, then run claude --continue in the same folder. The local transcript is still there.
How does Foxpit handle the 5-hour limit?
When Claude Code hits the limit, Fox parks the turn, shows the reset time and sends continue at the reset. A usage panel shows remaining quota and reset time for every agent that reports it.
Switch accounts, keep the thread.