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:
- 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) - “This cycle happens multiple times per day for heavy users” (
#34341, closed without a fix) - “Long-running agent work still stops dead” (
Orca #20512) - “log out, log in with the other account, restart the session” (
dev.to) - What do you do when Claude hits limits? “Log into my second claude account.” (
X)
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.
- 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?
- You (or Claude) set a rule: personal runs out → continue in work. Also in Automations → When an account runs out, continue in another.
- 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.
- 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
.claudefolder, which every account shares), then types the rule’s prompt there. - 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_prompttypes 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.
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, Continue in another account, Shared MCP servers.
Every Claude account in one Claude desktop, on Windows. Free for 2 accounts.
Written by the founder,
@inxanity06 · Updated 2026-11-18