yoink vs claude-swap

How each one switches a Claude account

Both tools save a Claude Code login once and restore it later without a browser sign-in, and both use the macOS Keychain on a Mac and files elsewhere.

• claude-swap. Log in with an account, run cswap add, log in with the next one and run cswap add again. cswap switch rotates to the next account, and cswap switch 2 or an email or alias picks one. Its README says a switch holds Claude Code's own credential locks while writing, so it never interleaves with a token refresh.
• yoink. yoink add saves the live login and runs claude auth login --claudeai for the next account. yoink work or yoink use work switches. Before each switch, yoink re-saves the live credential into the active profile, then writes the target credential and its oauthAccount block in ~/.claude.json. How it works has the sequence.

Feature by feature

Choose claude-swap if

• You only use Claude Code and want to see each account's usage at a glance.
• You want switching to happen for you as an account nears its limit, which is what cswap auto does. yoink only switches when you ask it to.
• You run two accounts at the same time in separate terminals.
• You already use uv or pipx for Python tools.

Choose yoink if

• You also use Codex, Kimi Code, Gemini or GitHub Copilot and want one tool for every login.
• You want one API key, from OpenRouter, DeepSeek, Ollama or any compatible endpoint, written into several coding agents.
• You prefer a single binary with no runtime, from the install script or PowerShell (or npm install -g yoink-cli, if you already have Node).

Can you use both?

Yes, with one rule: pick one of them for Claude Code accounts. Both rewrite the same live Claude Code credential, and each keeps its own saved copies, so switching with one leaves the other's idea of the active account out of date. A setup that works is claude-swap for Claude accounts and usage, and yoink for providers and the other vendors' logins.

FAQ