Switch accounts. Keep everything else.
Switching accounts? Keep talking.
The same session continues on your other account, with all its context, its MCP servers already signed in and its browser still logged in.
Try the demo
Runs in a throwaway HOME. Your own setup is not touched.
Open source · Apache-2.0 · macOS and Linux
Start from your problem
01 · the conversation keeps going
Change account. The conversation comes along.
Your Claude Code profiles share conversations, skills and settings. A session started with one account continues with another, or forks so both keep going.
Continue a session that another account started.
- add rate limiting to the api
- edited src/limits.ts +24 −3
one conversation, kept by every profile
02 · MCP logins, once per account
One login per account. Every agent uses it.
The gateway signs in to each remote MCP server once per account and keeps the token in your keychain. No agent logs in on its own, and each profile reaches its own account of the same service.
One OAuth login, shared by every session of every agent on that account.
no agent has signed in yet
03 · a browser per identity
A browser that is already the right you.
Each identity gets its own real Chrome profile. You sign in by hand once and the cookies stay. Links open with the account that owns them, and an agent works inside sessions you already have.
The link opens in that profile's Chrome profile.
A separate package, turno-browser. For your own accounts, at a human pace.
Browser identitiesthree identities, three Chrome profiles
04 · skills between accounts
Move work between accounts from inside the session.
A Claude Code plugin adds the moves you repeat every day. Each skill hands you the exact command or does the copy for you. Nothing switches behind your back.
Continue this session under another profile, with the conversation intact.
Install it with /plugin marketplace add wimo-dev/turno and /plugin install turno@turno.
The skills, one by one- add rate limiting to the api
- edited src/limits.ts +24 −3
three skills and a bridge
05 · how it knows which account
Every project folder has its own account.
This is how turno knows which account to use. Assign a folder once and every agent you open there signs in with that account. Folders without a rule use your default.
This folder and everything under it.
pick a folder
06 · one shared gateway
Eight sessions. One set of servers.
Every agent session starts its own copy of every MCP server. turno starts each server once, only when a tool is called, shares it between sessions and stops it when idle.
Memory per server, as it runs.
Measured on an Apple M3 with 16 GB, 2026-11-16, six common servers. Reproduce it with node bench/mcp-ram.mjs before you quote a number.
Method and caveats8 sessions, 6 servers each
07 · works with your agents
Four agents. One setup.
The same profiles, folder rules and gateway work for every agent you use. In Claude Code, a status line shows which account you are on and how much of it is left.
A profile for another agent, with the same rules.
four agents, the same rules
08 · safe to try
Try it without touching your setup.
The demo runs in a throwaway HOME. When you install for real, turno asks before it adopts anything and writes it all as one change you can undo.
The whole tour in a throwaway HOME.
turno runs each vendor's own CLI, unmodified. It is for separate work and personal accounts, not for getting around limits.
Try it- .claude/
- code/acme/
- .zshrc
nothing leaves your machine