Let Claude use SaneCode: limits, failover and moving work

Updated November 18, 2026.

What is it? SaneCode adds its own MCP server 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:

Why does this exist?

A usage limit stops a long task dead, and today the fix is manual. What people say:

The tools that switch accounts automatically today are for the Claude Code CLI only (claude-swap, lpm). 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.

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?

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.

What doesn’t it do?

Troubleshooting

Related: Continue after reset, Continue in another account, Shared MCP servers.

Try SaneCode

Every Claude account in one Claude desktop, on Windows. Free for 2 accounts.

Written by the founder, · Updated 2026-11-18