Skip to Content

Docs

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.

View source

This page is the way in: start from the problem you have, or read what stays with you when you switch accounts.

Start from your problem

Something does not work? turno doctor names the problem, and Troubleshooting has a page for each finding.

What stays when you switch

  1. The conversation. Your Claude Code profiles share conversations, skills and settings, so a session started with one account continues with another (turno work --resume <id>), or forks so both keep going. turno session handoff work prints the exact command. See What profiles share.
  2. Your MCP logins. The gateway signs in to each remote MCP server once per account (turno mcp login linear) and keeps the token in the macOS Keychain or the Linux Secret Service. No agent logs in on its own, and each profile can reach its own account of the same service. See The gateway.
  3. Your browser. Each profile opens claude.ai links in its own Chrome profile, so a link from a session opens with that session's account (turno open work <url> does it by hand). With the separate package turno-browser, each identity gets a persistent Chrome profile that you sign in to once by hand, and an agent works inside the sessions you already have. See Browser identities.
  4. The moves, from inside the session. The turno plugin for Claude Code adds /switch-account, /fork-session and /copy-artifact. See Skills.

How turno knows which account to use: each project folder has its own. turno profile assign ~/code/acme work once, and every agent you open there signs in with that account; folders without a rule use your default. turno auto never switches accounts in silence. See Folder rules.

One gateway, less memory

Every agent session starts its own copy of every MCP server. Eight sessions with six common servers is 3,163 MiB in 56 processes. turno starts each server once, only when a tool is called, behind one local gateway that every session of every agent shares: 847 MiB while all six run, 103 MiB while they sit idle. The benchmark has the method and the caveats.

Works with your agents

The same profiles, folder rules and gateway work for Claude Code, Codex CLI, GitHub Copilot CLI and Cursor CLI. In Claude Code, a status line shows the account, its 5 h and weekly usage, the context, the branch and the cost. See I use Claude Code and Codex.

Safe to try

turno demo builds a throwaway HOME with two profiles, a gateway and two MCP servers, opens a shell there and removes everything when you leave. Your own setup is not touched.

npx turno-cli demo

When you install for real, every write can be put back with turno undo, and turno uninstall --dry-run lists everything turno set up before anything is removed. Once turno is set up, a bare turno shows where you stand:

turno 0.2.0  ~ →  personal

Here ───────────────────────────────────────────────────────────────────────────
  claude   personal   folder without a rule

Profiles ───────────────────────────────────────────────────────────────────────
              5 hours    week    account
   personal   -          -       you@personal.example · pro  default
   work       -          -       you@work.example · max

Machine ────────────────────────────────────────────────────────────────────────
  gateway   ● running on port 52222
  sessions  0 live sessions

Is it for you?

turno is for the case where you run many sessions of several agents with more than one account. If you only need one of those pieces, other tools do it well: see the comparison.

It runs on macOS and Linux with Node 22.11 or newer. Windows is not supported. Nothing leaves your machine: no account, no telemetry, no proxy for model traffic.

Next

On this page