Native, not an orchestrator.
SaneCode doesn’t put its own chat window in front of Claude, doesn’t drive the Claude Code CLI or the SDK, and doesn’t sit between you and the model. Each account runs the official Claude desktop app, exactly as Anthropic ships it, and you talk to Claude directly. SaneCode keeps those apps in one window and handles what’s around them: sign-ins, switching, continuing a conversation in another account, shared MCP servers and updates.
The people who build Claude know its harness best
What instructions, tools, permissions and context go into Claude is tuned by Anthropic for the desktop app. Orchestrators replace or re-wrap that harness, and the native behavior is the first thing to break.
Every feature, the day it ships
Cowork, the Code tab, connectors, Remote Control, computer and browser use: whatever Claude desktop gets, you have inside SaneCode at once, because it is Claude desktop.
Your plan, used the normal way
Nothing goes through the SDK or the API on your behalf. Each account uses its plan exactly as the official app does.
Everything around Claude, nothing in front of it.
| SaneCode does | SaneCode doesn’t |
|---|---|
| Starts one official Claude desktop per account and docks it in one window | Show you a copy of Claude’s interface |
| Keeps every account signed in; guides each sign-in | Handle or read your passwords or tokens |
| Moves a Code session to another account when one hits its limit | Send your conversations anywhere |
| Shares local MCP servers with every account | Route your prompts through its own agent |
Want many different agents behind one UI instead? That’s what orchestrators are for: see SaneCode vs T3 Code.