# Let Claude use SaneCode (MCP) and failover (SaneCode docs)

> SaneCode is a Windows app that runs several Claude desktop accounts in one window. Each account is the official, unmodified Claude desktop app with its own data folder; SaneCode starts one per account and docks their windows beside its sidebar, so every account stays signed in. Free for 2 accounts; Pro ($29 once) for more. Not affiliated with Anthropic.

Page: https://sanecode.co/docs/let-claude-use-sanecode-mcp-failover/
Markdown: https://sanecode.co/docs/let-claude-use-sanecode-mcp-failover.md

## All SaneCode docs pages
- [Let Claude use SaneCode (MCP) and failover](https://sanecode.co/docs/let-claude-use-sanecode-mcp-failover/): SaneCode's own MCP server lets Claude see your accounts and their usage limits, carry a conversation on in another account when one runs out, schedule Continue after the reset, and report what happened while you were away. (Markdown: https://sanecode.co/docs/let-claude-use-sanecode-mcp-failover.md)
- [Use SaneCode from ChatGPT, Claude.ai and other AI apps](https://sanecode.co/docs/use-sanecode-from-chatgpt-claude-and-other-ai-apps/): Connect SaneCode's remote MCP server (mcp.sanecode.co) to ChatGPT, Claude.ai, Claude Code, Cursor, VS Code and other AI apps, so they can check your Claude accounts and move or schedule work on your PC. (Markdown: https://sanecode.co/docs/use-sanecode-from-chatgpt-claude-and-other-ai-apps.md)
- [Overview](https://sanecode.co/docs/): What SaneCode is and how it fits with Claude desktop. (Markdown: https://sanecode.co/docs/index.md)
- [How SaneCode works](https://sanecode.co/docs/how-sanecode-runs-multiple-claude-instances/): How SaneCode runs several Claude desktop accounts at once on Windows, where each account's data lives, what every account shares, what SaneCode changes on your PC, and how its settings connect. (Markdown: https://sanecode.co/docs/how-sanecode-runs-multiple-claude-instances.md)
- [Install and first run](https://sanecode.co/docs/install-sanecode-on-windows/): Install SaneCode and bring in the Claude you already use. (Markdown: https://sanecode.co/docs/install-sanecode-on-windows.md)
- [Add Claude accounts and sign in](https://sanecode.co/docs/add-claude-accounts-and-sign-in/): Add a second (or fifth) Claude account to SaneCode, sign in once with the built-in guide, and fix sign-ins that land in your other Claude. (Markdown: https://sanecode.co/docs/add-claude-accounts-and-sign-in.md)
- [Switching and windows](https://sanecode.co/docs/switch-claude-accounts-without-signing-out/): Shortcuts, popping out, chat tabs, and what happens when SaneCode closes. (Markdown: https://sanecode.co/docs/switch-claude-accounts-without-signing-out.md)
- [Layouts: Split, Grid and Canvas](https://sanecode.co/docs/claude-desktop-side-by-side-layouts/): See several Claude accounts or chats at once in SaneCode. Split and Grid are free, Canvas is Pro. Every control, what it does, and the limits. (Markdown: https://sanecode.co/docs/claude-desktop-side-by-side-layouts.md)
- [Continue a Claude conversation in another account after a usage limit](https://sanecode.co/docs/continue-claude-session-in-another-account/): When a Claude account hits its usage limit, move the Claude Code conversation to another of your accounts and keep going with the full context, no new chat, no re-explaining. (Markdown: https://sanecode.co/docs/continue-claude-session-in-another-account.md)
- [Continue after reset (Automations)](https://sanecode.co/docs/continue-claude-after-usage-limit-resets/): Send “Continue” or your own prompt to any Claude account's window, or to Codex, when its usage limit resets. Several at once, logged, without keeping the window in front. (Markdown: https://sanecode.co/docs/continue-claude-after-usage-limit-resets.md)
- [Shared MCP servers](https://sanecode.co/docs/share-mcp-servers-across-claude-accounts/): Set up an MCP server once in SaneCode and every Claude account gets it, instead of configuring it in each account. (Markdown: https://sanecode.co/docs/share-mcp-servers-across-claude-accounts.md)
- [Claude in Chrome for every account](https://sanecode.co/docs/claude-in-chrome-for-every-account/): Use Claude in Chrome from every Claude desktop account in one Chrome profile, without signing the extension out and in when you switch. (Markdown: https://sanecode.co/docs/claude-in-chrome-for-every-account.md)
- [Claude desktop and Claude Code themes](https://sanecode.co/docs/claude-desktop-and-claude-code-themes/): Change the theme of Claude desktop's Code tab in every account at once. SaneCode applies a Claude Code theme (colours and a background) with one setting, in light or dark mode, without modifying Claude. (Markdown: https://sanecode.co/docs/claude-desktop-and-claude-code-themes.md)
- [Claude Code plugins, skills, mods and MCP with several accounts](https://sanecode.co/docs/claude-code-plugins-and-skills-in-every-account/): Plugins and skills added in Claude desktop belong to one account; Claude Code's own .claude folder is one per PC. Which extensions every account shares, which stay per account, and how to set them up. (Markdown: https://sanecode.co/docs/claude-code-plugins-and-skills-in-every-account.md)
- [Settings](https://sanecode.co/docs/sanecode-settings/): Every setting and exactly what it changes. (Markdown: https://sanecode.co/docs/sanecode-settings.md)
- [Invite friends: $5 off Pro each](https://sanecode.co/docs/invite-friends-get-pro-discount/): Share your SaneCode referral link. Every friend who signs up and signs in from SaneCode takes $5 off your Pro, and gets $5 off theirs. Six friends make Pro free. (Markdown: https://sanecode.co/docs/invite-friends-get-pro-discount.md)
- [Claude updates and repair](https://sanecode.co/docs/claude-desktop-updates-and-repair/): What happens when Claude desktop updates, resets or is reinstalled. (Markdown: https://sanecode.co/docs/claude-desktop-updates-and-repair.md)
- [FAQ and troubleshooting](https://sanecode.co/docs/sanecode-faq-and-troubleshooting/): Common questions and fixes. (Markdown: https://sanecode.co/docs/sanecode-faq-and-troubleshooting.md)

## Questions people ask
- How do I add a second Claude account?
- How do I continue a Claude Code session in another account after a usage limit?
- How do I share my MCP servers with every Claude account?
- Does SaneCode change the Claude app or my sign-ins?

---

# Let Claude use SaneCode: limits, failover and moving work

*Updated November 18, 2026.*

**What is it?** SaneCode adds its own [MCP server](https://modelcontextprotocol.io/) to every
Claude account it runs. Claude can then see your accounts and their usage limits, and ask SaneCode
to move work between them. You don't learn any commands: you ask Claude in plain words, *"which
account has room left?"*, *"if you run out, continue in my work account"*, *"what happened
overnight?"*.

**Who is it for?** Anyone who runs more than one Claude account on one Windows PC:

- **Two plans, one person**: a personal and a work account, or two Max plans, used in turn as
  limits run out.
- **Long and unattended work**: migrations, big refactors, "run until the tests pass", work left
  running overnight or during a meeting.
- **Freelancers and consultants**: a Claude per client, kept apart, with work moved only when you
  say so.
- **Away from the desk**: you want to know what your Claudes did and keep them going without
  sitting at the PC.

## Why does this exist?

A usage limit stops a long task dead, and today the fix is manual. What people say:

- "sessions just stall on the limit banner" ([anthropics/claude-code#89993](https://github.com/anthropics/claude-code/issues/89993))
- "This cycle happens multiple times per day for heavy users" ([#34341](https://github.com/anthropics/claude-code/issues/34341), closed without a fix)
- "Long-running agent work still stops dead" ([Orca #20512](https://github.com/stablyai/orca/issues/20512))
- "log out, log in with the other account, restart the session" ([dev.to](https://dev.to/inulute/how-i-run-two-claude-accounts-as-one-49b1))
- What do you do when Claude hits limits? "Log into my second claude account." ([X](https://x.com/AbhiCodes15/status/2075897894893187347))

The tools that switch accounts automatically today are for the Claude Code CLI only
([claude-swap](https://github.com/realiti4/claude-swap), [lpm](https://lpm.cx/claude-code-multiple-accounts)).
SaneCode does it for the Claude desktop app, with every account left open and the same
conversation carried over.

## How do I turn it on?

It's on by default: **Settings → Tools for Claude → Let Claude use SaneCode**.

- **Chats** get the tools from each account's Claude config.
- **The Code tab** gets them as a small Claude Code plugin (`sanecode-tools`) that SaneCode names in
  Claude Code's settings, because Code sessions don't read the desktop config.
- A Claude that's already open gets them after a **Restart** (title bar); Code sessions when they
  next start. In Claude you'll see "used plugin sanecode-tools sanecode" when it calls one.
- Turn it off and SaneCode takes its server back out of every account; your own MCP servers are
  never touched.

## What can I ask Claude?

| You want to | Ask Claude | Tool | Plan |
| --- | --- | --- | --- |
| Know which account to use | "Which account has room left?" "When does my limit reset?" | `sanecode_accounts_and_limits` | Free |
| Leave a long task running safely | "I'm going to bed, don't let this stop if you run out." "If you run out, continue in work." | `sanecode_set_failover` | Pro |
| Keep going right now | "I'm out here, move this to my other account." | `sanecode_continue_in_account` | Free |
| Wait for the reset instead | "Continue this when the limit resets." "Say *run the tests* at 7 pm." | `sanecode_schedule_continue` | Pro |
| Catch up after being away | "What happened overnight?" "Did the failover kick in?" | `sanecode_activity` | Free |
| See where every session stands | "Which sessions stopped?" "Is the migration in personal still running?" | `sanecode_sessions` (titles only) | Free |
| Tell another account what to do | "Tell my work Claude to commit and open a PR." | `sanecode_send_prompt` (your words) | Pro |
| Review or stop what's set | "What's scheduled?" "Stop the failover, I'm back." | `sanecode_list_automations`, `sanecode_cancel_automation` | Free |
| See accounts together | "Put work and personal side by side." | `sanecode_open_accounts` | Free |

Claude offers the failover by itself before a long or overnight task. Each tool tells Claude when
it helps and when it doesn't, so a fast model picks the right one too (we checked ten everyday
requests with Claude Haiku: right tool every time, and no tool for an unrelated coding question).

## What does it look like in practice?

**Before bed.** *"Refactor all 60 handlers, I'll check in the morning."* Claude checks your
accounts, sees *work* has room, and sets a failover: if *personal* hits its limit, the same
conversation opens in *work* and SaneCode types "Continue refactoring the 60 handlers from where
you stopped." When *work* runs out and *personal* has reset, it moves back.

**Next morning.** *"What happened overnight?"* Claude reads the activity: "01:12 moved 'Refactor
handlers' to work (personal hit its limit) · 03:40 typed Continue in personal." Then *"Stop the
failover, I'm back."*

**Mid-day limit.** *"I'm out of usage, move this to my other account."* The conversation opens in
the other account with your project folder, and Claude there carries on. Your first account keeps
its copy.

**Dispatching.** *"Tell my client account to run the tests and open a PR."* SaneCode types exactly
that into the client account's Claude, which does the work. Claude in this account only passes the
message on.

## How does failover work?

1. You (or Claude) set a rule: *personal* runs out → continue in *work*. Also in **Automations →
   When an account runs out, continue in another**.
2. Once a minute SaneCode reads *personal*'s newest Code session for a usage-limit message
   ("5-hour limit reached ∙ resets 7pm"). It reads only while a rule exists.
3. When it finds one, it opens **the same conversation** in *work* with Claude's own resume link
   (Claude Code keeps conversations in your Windows user's `.claude` folder, which every account
   shares), then types the rule's prompt there.
4. When *work* runs out too and *personal* has reset, it moves back. If both are out, it waits for
   the first reset. Each limit moves once.

If Claude's own **Auto-continue when limits reset** is ticked in the first account, turn it off
for conversations with a failover: otherwise both accounts carry on the same conversation after
the reset.

Every move is in the Automations log ("Moved 'Migrate API' here from personal"). SaneCode has to
be open; the PC may sleep, and SaneCode acts when it wakes.

## Is it safe? What does it see?

- **Nothing leaves your PC.** The server is `sanecode.exe --mcp`, started by Claude over stdio. It
  talks to the open SaneCode through files in `%APPDATA%\SaneCode\mcp`, your own Windows folder.
  There is no network port.
- **No conversation content.** SaneCode reads session titles, folders, times and the limit line,
  never what you and Claude said. Our telemetry never includes anything from your accounts.
- **It only types what you asked.** `sanecode_send_prompt` types your words; moves and failovers
  type the prompt you (or Claude, restating your task) set. Every typed line is in the log.
- **Moving or typing uses the other account's usage**, like typing there yourself.
- **Pro is checked by SaneCode**, not by Claude: a Free install answers "needs SaneCode Pro" for
  the Pro tools.
- **From outside your Claude accounts every tool is Pro.** If something other than one of your
  Claude apps uses the tools (ChatGPT, Claude.ai, another app, a terminal), SaneCode asks the open
  app whether this PC has Pro before any tool runs; the remote server checks Pro too.

## Can I use it from ChatGPT or my phone?

Yes, with SaneCode Pro: SaneCode has a remote MCP server at `https://mcp.sanecode.co/mcp` for
ChatGPT, Claude.ai, Claude Code on another computer, Cursor and other AI apps. Turn on
**Settings → Tools for Claude → Use SaneCode from other apps**, add the URL in the app, and allow
it once with your SaneCode account. The app then reports and dispatches while Claude in each
account does the work. Step by step for each app:
[Use SaneCode from ChatGPT, Claude.ai and other AI apps](https://sanecode.co/docs/use-sanecode-from-chatgpt-claude-and-other-ai-apps/).

## What doesn't it do?

- **Only Code-tab conversations move.** Chats stay in their account (Claude keeps them on its
  servers, per account).
- **It can't see a percentage used.** It knows a limit was hit and when it resets (Claude keeps
  no meter on disk), so "room left" means "no limit hit in the last 6 hours".
- **It doesn't do the work itself.** It moves, schedules and types; Claude in each account works.
- **The weekly limit counts too**: SaneCode reads "resets Thu 9am" and "resets Nov 21, 9am" as
  well as the 5-hour "resets 7pm".

## Troubleshooting

- **Claude doesn't mention SaneCode.** Restart that account (title bar → Restart) or start a new
  Code session; check Settings → Tools for Claude is on.
- **"SaneCode isn't open."** The tools that act need the SaneCode app running.
- **"Needs SaneCode Pro."** Failover, scheduling, sending a message, and any use from outside
  your Claude accounts are Pro.
- **A move didn't type.** The target account was starting; SaneCode starts it if needed and retries for a
  few minutes, then logs why in Automations.

Related: [Continue after reset](https://sanecode.co/docs/continue-claude-after-usage-limit-resets/),
[Continue in another account](https://sanecode.co/docs/continue-claude-session-in-another-account/),
[Shared MCP servers](https://sanecode.co/docs/share-mcp-servers-across-claude-accounts/).
