SkillAgentSearch skills...

turno

Switch accounts in your coding agents and keep the conversation, the MCP sign-ins and the browser session.

Install / Use

claude mcp add wimo-dev -- npx -y github:wimo-dev/turno

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

81/100

Supported Platforms

Claude Code
Claude Desktop
Cursor
GitHub Copilot
OpenAI Codex

Our assessment of turno

turno scores 81/100 on our quality scale, 716th of 948 AI & Machine Learning skills we index.

Its MCP Server is 29 KB long, well organised into 47 sections with 10 code examples: a thorough specification that gives an agent plenty to work with.

It has 10 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
4/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so turno is actively maintained.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 97/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-11-22. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

turno compared with similar skills

All 4 of these similar skills score higher than turno; compare them before choosing.

SkillScoreStarsUpdatedFormat
turno (this skill)by wimo-dev8110todayMCP Server
claude-memby thedotmack100119.0ktodayCLAUDE.md
Agent-Reachby Panniantong100114.0ktodayCLAUDE.md
Understand-Anythingby Egonex-AI10093.7ktodayCLAUDE.md
hyperframesby heygen-com10088.2ktodayCLAUDE.md

Frequently asked questions

How do I install turno?
Run claude mcp add wimo-dev -- npx -y github:wimo-dev/turno. The install tabs above show the steps for each supported agent.
Which AI agents does turno work with?
It is written for Claude Code, Claude Desktop, Cursor, GitHub Copilot and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
Is turno safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is Apache-2.0-licensed and scores 97/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is turno still maintained?
The repository was last updated today, so turno is actively maintained.
<p align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="docs/assets/logo-dark.svg"> <img src="docs/assets/logo-light.svg" alt="turno" width="168" height="56"> </picture> </p> <p align="center"> <b>Switch accounts. Keep everything else.</b> </p> <p align="center"> <a href="https://www.npmjs.com/package/turno-cli"><img alt="npm" src="https://img.shields.io/npm/v/turno-cli?color=2457F5"></a> <a href="https://github.com/wimo-dev/turno/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/wimo-dev/turno/actions/workflows/ci.yml/badge.svg"></a> <a href="LICENSE"><img alt="License: Apache-2.0" src="https://img.shields.io/badge/license-Apache--2.0-blue"></a> <a href="https://scorecard.dev/viewer/?uri=github.com/wimo-dev/turno"><img alt="OpenSSF Scorecard" src="https://api.scorecard.dev/projects/github.com/wimo-dev/turno/badge"></a> </p> <p align="center"> <a href="https://turno.wimo.dev"><b>turno.wimo.dev</b></a> · <a href="https://turno.wimo.dev/docs">Docs</a> · <a href="https://turno.wimo.dev/docs/releases">Releases</a> · English · <a href="README.es.md">Español</a> </p>

Switching accounts? Keep talking. The same session continues on your other account, with its whole context, its MCP servers already signed in and a browser profile that keeps its sign-ins. turno is for people who use a work account and a personal account with their coding agents.

  • Your conversation. A Claude Code session started with one account continues under another, or forks into a second one: turno session handoff work prints the command.
  • Your MCP sign-ins. One local gateway logs in to each remote OAuth server once per account (turno mcp login <server>), and every agent session of that account reaches it through the gateway.
  • Your browser session. A real Chrome profile per identity that keeps its sign-ins (the separate turno-browser package), and claude.ai links that open with the session's account (turno open).
  • Your control. Three skills of the Claude Code plugin move work between accounts from inside a session: /switch-account, /fork-session and /copy-artifact.
  • The right account by itself. Each project folder gets its account, in Claude Code, Codex, Copilot CLI and Cursor CLI.
  • Easy to try, easy to undo. npx turno-cli demo runs in a throwaway HOME, and turno undo puts back every file a command changed.

The same gateway starts each MCP server once and shares it between sessions; the measured memory saving is in Benchmark. turno.wimo.dev tells the whole story, with a small working picture of each part.

turno demo: two profiles, one gateway, the status line, the picker and turno doctor, in a throwaway HOME

Install

# try it first, in a throwaway HOME; your own setup is not touched
npx turno-cli demo

Then install it with the package manager you already use (macOS or Linux, Node 22.11+):

npm install --global turno-cli
pnpm add --global turno-cli
bun add --global turno-cli
# yarn 1 (classic); yarn 2 and later have no global installs
yarn global add turno-cli
brew tap wimo-dev/turno && brew trust wimo-dev/turno && brew install turno

The npm package is turno-cli; the command it installs is turno, and turno upgrade later updates it with the same tool. npx turno-cli, pnpm dlx turno-cli and bunx turno-cli run it once without installing. It runs no install scripts, and npm and Homebrew install exactly the dependency versions that were tested, from its npm-shrinkwrap.json (pnpm, bun and yarn resolve the dependencies of its dependencies themselves). CI installs it each of these ways on macOS and Linux. Nothing leaves your machine: no account, no telemetry, no proxy for model traffic.

What it does

  • A conversation that continues on another account. Your Claude Code profiles share conversations, skills, commands, hooks, plugins and settings, and keep only their own login. turno work --resume <id> continues a session that another account started, and turno session handoff work prints the exact command (--fork keeps this session open and starts a copy). What profiles share.

  • MCP sign-ins, once per account. The gateway logs in to each OAuth remote server once per account (turno mcp login <server>) and every agent session of that account uses it; a variant per profile lets work and personal reach two accounts of the same service. Secrets live in the macOS Keychain or the Linux Secret Service, not in agent configs. The gateway.

  • A browser per identity (separate package turno-browser): an MCP server that drives your installed Chrome with one persistent profile per identity, so an agent works in the sessions you signed into by hand, and turno open <profile> <url> opens a claude.ai link with the account that owns it. See Browser with real profiles.

  • Skills that move work between accounts. The Claude Code plugin adds /switch-account, /fork-session and /copy-artifact, and the accounts bridge lets a session delegate a task to a service only another profile is signed into, asking before it writes. Skills.

  • The folder picks the account. turno profile assign ~/code/acme work and every agent you open in that repository uses your work login; turno auto picks it and says which account and why, and turno status shows who is logged in where. The same folder rule can choose which MCP servers sessions there see. Folder rules.

  • One MCP gateway for every session. mcpd listens on 127.0.0.1, answers initialize and the tool lists from a cache, starts a server the first time one of its tools is called, shares that process between sessions where it is safe (shared, project or session scope) and stops it when idle, sooner when memory is low. It speaks MCP 2025-11-25 and 2026-07-28 on the same endpoint, and turno mcp log, top and savings show its calls, memory and saving. See docs/mcp.md.

  • Four agents, one setup. The same profiles, folder rules and gateway for:

    | Agent | Profile | Gateway entries | Example | |---|---|---|---| | Claude Code | ~/.claude-<p>, claude-<p> | .claude.json | turno work | | Codex CLI | ~/.codex-<p>, codex-<p> | config.toml, token from the environment | turno auto --agent codex | | GitHub Copilot CLI | ~/.copilot-<p>, copilot-<p> | mcp-config.json | copilot-work | | Cursor CLI | ~/.cursor-<p>, cursor-agent-<p> | ~/.cursor/mcp.json, routed by environment | cursor-agent-work |

    A profile is one account of one agent. opencode, Gemini CLI, Goose, Crush, Droid and Kiro can use the gateway too: turno mcp config --agent <name> prints their entries. See docs/agents.md.

  • A status line for Claude Code with the account, its 5 h and weekly usage, context, branch and cost, with Nerd Font icons it installs for you (or Unicode where there is none).

  • Easy to check, easy to undo. turno doctor names each problem and its fix (--fix repairs what is safe, --report prints a block for an issue with no secrets), turno mcp call tries a tool the way a session would, --no-gateway opens the agent without turno's gateway to tell whose problem it is, and turno undo puts back every file a command changed. Troubleshooting.

Quick start

# finds your agents, profiles, folders and MCP servers, shows the diff,
# then starts the gateway and points every profile at it
turno init
# sign in once per profile (/login)
claude-work
# Claude Code, with this folder's account
cd ~/code/acme && turno auto
# where you stand: this folder, accounts, gateway, what to do next
turno

turno init asks before it adopts anything and writes everything as one change, so one turno undo <stamp> reverts it. The gateway runs as a login service (launchd on macOS, systemd --user on Linux); turno init --no-start leaves it for later (turno mcp daemon start, then turno mcp sync). Step by step instead:

# ~/.claude-work and the claude-work command
turno profile add work --color violet
turno profile add personal
# sign in once per profile (/login)
claude-work
# this folder and everything under it
turno profile assign ~/code/acme work
# folders without a rule
turno config set default personal
# mcp.toml from the servers you already have
turno mcp import --move-secrets --write
# the gateway, and every profile pointed at it
turno mcp daemon start && turno mcp sync
# Claude Code, signed in as work
cd ~/code/acme && turno auto

Codex, Copilot and Cursor profiles are the same with --agent codex|copilot|cursor. Point your terminal or editor at turno auto (or the turno-auto launcher) and every folder opens with its account. Launchers go in ~/.local/bin; when it is not on your PATH, turno profile add prints the line to add, and turno work works meanwhile. turno auto never switches accounts in silence: a missing profile or a broken config.toml stops it with the command that fixes it (docs/accounts.md).

Benchmark

Six popular local MCP servers (Playwright, Chrome DevTools, filesystem, memory, sequential thinking, Context7), each session running initialize and tools/list on all of them. Resident memory of every process involved, Apple M3 with 16 GB, Node 26, 2026-11-16:

| Sessions | Each session starts its own servers | turno, all six servers running | turno, idle (tool lists cached) | |---|---|---|---| | 4 | 1,410 MiB, 28 processes | 692 MiB, 8 processes | 101 MiB, 1 process | | 8 | 3,163 MiB, 56 processes | 847 MiB, 8 processes | 103 MiB, 1 process |

Started the way most server READMEs suggest (npx -y <package>), 4 sessions take 3,123 MiB in 52 processes. Reproduce it with node bench/mcp-ram.mjs --sessions 8; method and caveats in BENCHMARKS.md.

How it compares

| | Accounts per folder | Several agents | Shared MCP processes | Status line | Notes | |---|---|---|---|---|---| | turno | yes | Claude Code, Codex, Copilot CLI, Cursor CLI | yes, lazy | yes | CLI, local only | | claude-swap | switch, not per folder | Claude Code | no | no | usage dashboard, parallel sessions | | clauth | switch | Claude Code | no | no | TUI, cross-account delegation | | cc-switch | no | many | no (manages MCP config) | no | desktop app, provider switching | | ccstatusline | no | Claude Code | no | yes | the most customizable status line | | MetaMCP, mcp-proxy | no | any MCP client | aggregates or bridges | no | Docker / transport bridge | | Plain CLAUDE_CONFIG_DIR | by hand | one | no | no | what turno automates |

If you only need one of these pieces, those tools are good at it. turno is for the case where you run many sessions of several agents with more than one account.

FAQ

Is using several accounts allowed? That depends on your plan, not on turno. turno runs each vendor's own, unmodified CLI, and each account signs in with the vendor's own login in its own folder. The intended use is separate work and personal accounts. Do not use it to get around usage limits or safeguards; see Vendor terms.

Where are my credentials? Where each agent keeps them, inside that profile's folder (or the Keychain where the agent uses it). turno never reads, copies or forwards login tokens. MCP secrets you

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars10
CategoryAI
Updated49m ago
Forks0

Languages

TypeScript

Trust signals

97/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info