On this page
  1. Key takeaways
  2. What actually happens when you hit the limit?
  3. Can you move a conversation to another Claude account?
  4. Method 1: Terminal, same config folder: /login then --continue
  5. Method 2: Terminal, separate accounts: resume by path
  6. Method 3: Let a tool switch for you
  7. Method 4: The desktop app’s Code tab
  8. Session Relay: continue in another account with SaneCode
  9. Is it against the terms to switch accounts when you hit the limit?
  10. How did we research this?
  11. FAQ
  12. The bottom line

Hit your Claude usage limit? Continue the same conversation in another account

Short answer: You can’t raise the limit, but you can carry the same Claude Code conversation into another of your Claude accounts with its full history. In the terminal, resume it from the other account with claude --resume. In the Claude desktop app, SaneCode’s Session Relay moves it to the account you pick. Or wait, and have it continue by itself when the limit resets.

You’re two hours into a refactor. Claude knows the codebase, the plan, the three things you already tried. Then: “You’ve reached your usage limit.” The reset is hours away.

You have a second account. But a new chat there knows nothing, and explaining everything again eats the very limit you just got back. A GitHub issue describes it exactly: hitting the limit “completely disrupts the workflow… forcing users to either wait for the limit to reset or abandon the session entirely” (#64376).

Plenty of people live with this. One user on X:

“i currently have 7 claude max plans because i use claude really heavily and when one account hits the quota i just switch to another one” (@thevibecodr)

Here’s how to make that switch without losing the conversation.

Key takeaways

What actually happens when you hit the limit?

“Pro and Max plans have a five-hour session limit and a weekly limit”, and “these limits are shared across Claude and Claude Code” (Using Claude Code with your Pro or Max plan). So a busy chat day can stop your coding session too. When you hit one, you have three choices:

  1. Wait. The desktop app’s Code tab can retry for you: it has an Auto-continue when limits reset option (what’s new, week 33).
  2. Start fresh in another account. Fast, but you lose all the context.
  3. Carry the conversation over to another account. That’s what this guide is about.

Can you move a conversation to another Claude account?

It depends where the conversation lives.

Chats on claude.ai, the desktop app’s Chat tab and mobile: no. Anthropic’s support assistant, quoted on Reddit, says “Chats, projects, and conversations can’t be transferred or continued between the accounts” (r/Anthropic). The best you can do is ask Claude for a handoff summary before the limit hits and paste it into the other account.

Claude Code: yes. Claude Code saves each conversation as a .jsonl transcript in your user folder, under ~/.claude/projects (Windows: %USERPROFILE%\.claude\projects), one folder per project. The transcript isn’t locked to an account. Anthropic’s docs list claude --resume <transcript-path>, which “resumes the session stored in the .jsonl transcript file at that absolute path” (sessions).

Method 1: Terminal, same config folder: /login then --continue

If you use plain claude with one config folder:

  1. In the session that hit the limit, run /login and sign in with your other account. (Or exit, run claude, and /login there.)
  2. Run claude --continue in the same project folder. It “reopens the most recent session in the current directory” (sessions).

A Reddit user confirms: “you can also just exit out and ‘claude –resume’, and it’ll show all prior sessions that started from that folder. None of your session data is lost” (r/ClaudeCode). Theo found the CLI routes running sessions to the new login on its own: “you can just /login in a different tab and all traffic gets routed correctly on existing runs” (@theo).

Method 2: Terminal, separate accounts: resume by path

If you keep each account in its own folder with CLAUDE_CONFIG_DIR (see our Claude Code multiple accounts guide), each account has its own projects folder, so --continue in the other account won’t find the session. Point it at the file instead.

  1. Find the transcript. In PowerShell, the newest conversations for all projects:

    Get-ChildItem "$HOME\.claude\projects" -Recurse -Filter *.jsonl |
      Sort-Object LastWriteTime -Descending |
      Select-Object -First 5 FullName, LastWriteTime

    (Using a custom folder for the first account? Replace $HOME\.claude with it.)

  2. Resume it in the other account, using the full path:

    claude-work --resume "C:\Users\you\.claude\projects\C--code-myapp\0b3f…e1.jsonl"

    On macOS/Linux: CLAUDE_CONFIG_DIR=~/.claude-work claude --resume /Users/you/.claude/projects/…/….jsonl.

The session continues “on the model it was using”, with its messages, tool calls and results (sessions). Run it from the same project folder so file paths still line up.

Method 3: Let a tool switch for you

Several open-source tools watch your usage and switch accounts for you:

These are terminal tools. Most of them swap your saved login file, so read what they do with it.

Method 4: The desktop app’s Code tab

This is where it gets awkward. The transcripts are the same files on disk, but each account keeps its own list of Code sessions. Sign out of the account that hit the limit, sign in to the other one, and the sidebar is empty. Users notice:

“If you use the Claude desktop app, you know how frustrating it is when you switch accounts and your previous chats disappear. How do you continue your work?” (@sanaullahrais)

The conversations aren’t gone; the other account just doesn’t list them (r/ClaudeAI). Your options:

Session Relay: continue in another account with SaneCode

SaneCode Sessions: a Claude Code conversation ready to continue in another account after a usage limit
Session Relay: pick the conversation, pick the account, keep going.

SaneCode runs the official Claude desktop for each of your accounts at the same time, in one window. Session Relay is its name for moving a Claude Code conversation from one account to another (docs):

  1. Open the Sessions tab in SaneCode’s sidebar. It lists every account’s Claude Code conversations, newest first.
  2. Click the conversation that hit the limit. Continue in lists your other accounts.
  3. Pick one with room left. SaneCode switches to it, and the conversation is in its Code tab, ready to go.

What comes along: every message so far, Claude’s earlier answers and tool results, the project folder and the session’s settings (model, permission mode). Nothing is uploaded; SaneCode adds the conversation to the other account’s list on your PC. Session Relay is free. (The account you continue in must have opened its Code tab once.)

Free for 2 accounts; Pro is $29 once for unlimited accounts. Not affiliated with Anthropic.

Is it against the terms to switch accounts when you hit the limit?

People ask this a lot (r/Anthropic: “Using multiple Pro accounts to bypass Claude Code rate limits— is it against the ToS?”). What the sources say:

Anthropic hasn’t published a rule about one person switching between their own paid accounts. Keep it to accounts you own and pay for, sign in through Anthropic’s own flow, and don’t share.

How did we research this?

We read Anthropic’s own pages first: the Claude Help Center, the Claude Code docs and the legal and compliance page. Then we went through the open GitHub issues, about 35 posts on X, Reddit threads, Hacker News and around 50 GitHub tools, in November 2026. Every quote links to where it was said. The Claude desktop details (the claude-desktop.exe launcher, --user-data-dir, the Claude-Data folder) are the same mechanism SaneCode is built on, so we checked them against a current Claude desktop (version 5.11492) on Windows. We make SaneCode, so we’ve kept its section separate and compared it in the same table as everything else.

FAQ

Can I continue a claude.ai chat in another account?

No. Chats belong to the account. Ask Claude for a summary of where you are and start the other account with it.

Will the other account remember my project?

In Claude Code, yes: the resumed session has the full conversation. Project files like CLAUDE.md live in your repo, so every account reads them.

Does resuming in another account cost more?

The first message is read without the old account’s prompt cache, so it costs more of the new account’s limit than a normal turn (Reddit). After that it’s normal.

Is two Pro accounts better than one Max?

It depends on your usage; people weigh it on r/ClaudeAI. Two Pro plans means two separate limits and switching between them; Max is one bigger limit with no switching.

Can Claude continue by itself when the limit resets?

Yes, in the desktop Code tab with Auto-continue when limits reset. SaneCode’s Automations do it for any account’s window, chats included, and for Codex (every way to continue after a reset).

The bottom line

A usage limit doesn’t have to end the session. Claude Code keeps your conversation on your own disk, so another account can continue it: claude --continue after a /login, or claude --resume <path> across config folders. In the desktop app, where each account hides the other’s sessions, SaneCode’s Session Relay moves the conversation in three clicks.

Related: How to switch between Claude accounts without logging out · Claude Code with multiple accounts

Every Claude account, signed in, in one window

SaneCode runs the official Claude desktop once per account. Free for 2 accounts.