Yoink

Every AI coding login and provider, in one place.

Yoink for AI coding is an open source (MIT) CLI for macOS, Linux and Windows, plus a macOS menu bar app, that switches AI coding logins and connects API-key providers to 13 coding harnesses.

_{Not the Yoink drag-and-drop app for Mac, and not the PyPI yoink-cli media downloader.}

Switch Claude Code, ChatGPT (Codex), Kimi Code, Gemini and GitHub Copilot logins without signing out. Add an API key once (OpenAI, Kimi, OpenRouter, Ollama, or any compatible API) and yoink connects it to the coding harnesses that speak its API, up to 13: pi, omp, opencode, codex, Claude Code, Qwen Code, Kilo Code, Droid, Crush, Goose, Zed, Continue and Claude Desktop. Drive it from the terminal on macOS, Linux and Windows, or from the macOS menu bar.

Website  ·  Download for Mac  ·  Read the docs  ·  npm

Download the notarized Yoink app for Apple Silicon or Intel from the download page, then drag it to Applications. It lives in the menu bar and handles Claude Code accounts and API-key providers: switch accounts, save the current login, add a provider and tick the harnesses it connects to. Subscription logins for Codex, Kimi, Gemini and Copilot switch from the CLI.

macOS / Linux:

curl -fsSL https://yoink.codes/install.sh | bash

Windows (PowerShell):

powershell -c "irm https://yoink.codes/install.ps1 | iex"

Or on any OS with Node:

npm install -g yoink-cli

Each drops a single self-contained binary onto your PATH. Confirm it answers:

yoink version

Register your Claude accounts once, then switch between them by name:

yoink add        # sign in as account A, name it "work"
                 # "Add another?" > yes > sign in as account B, name it "personal"

yoink personal   # switch to personal
yoink work       # switch back

Restart Claude Code after a switch so it picks up the new login.

Save the logins of your other coding tools the same way. Each one switches inside its own tool only:

yoink save codex-work --tool codex   # snapshot the ChatGPT login Codex holds right now
yoink add                            # pick ChatGPT (Codex), Kimi Code, Gemini or GitHub Copilot to add another
yoink use codex-work                 # switch Codex, leave Claude Code and the rest alone
yoink current                        # the active profile in every tool

Connect an API-key provider to your harnesses:

yoink add        # pick "Provider (API key)", a preset or Custom, paste the key, pick models, tick harnesses
yoink harnesses  # see which harness has which provider

Run yoink with no arguments for a keyboard-driven list of your profiles, grouped by tool once you have more than one kind:

┌  yoink switch accounts
│
│  Claude Code
│  ● work (work@company.com)
│  ○ personal
│  Providers
│  ○ openrouter
│  ChatGPT (Codex)
│  ○ codex-work
│
└  ↑↓/jk move   ↵ switch   n new   e edit   s save   d delete   q quit

Actions loop back to the list, so you can switch, add, and prune in one sitting, then leave with q. See interactive menu.

• Instant Claude Code switching. Each profile stores the credential blob (macOS Keychain on macOS, ~/.claude/.credentials.json on Linux/Windows) plus the oauthAccount identity, so a swap is a keystroke, not a browser round-trip.
• Never loses a token. Every switch re-snapshots the active profile from the live credential store first, so a background token refresh is never dropped.
• Subscription logins beyond Claude. Save and switch ChatGPT (Codex), Kimi Code, Gemini and GitHub Copilot logins too. Each tool switches inside itself only, so a subscription token never leaks into another tool, and yoink asks before switching a tool that is running. See subscriptions.
• One provider, up to 13 harnesses. Add a provider once and connect it to every harness its endpoints support (pi, omp, opencode, codex, Claude Code, Qwen Code, Kilo Code, Droid, Crush, Goose, Zed, Continue and Claude Desktop). Rotate the key or change the model list and yoink re-syncs every harness it is connected to.
• Presets and custom providers. OpenAI, Kimi Code, Moonshot, OpenRouter, DeepSeek, Z.ai and Ollama are built in. For anything else, yoink probes the base URL to find which of OpenAI Chat, OpenAI Responses and Anthropic Messages it speaks.
• Real model metadata. Pick as many models as you like from the provider's live list; context windows, output limits, reasoning and image support come from models.dev.
• Import what you already have. yoink import finds providers you set up by hand in your harness configs and brings them under management.
• Per-project overrides. Apply a provider to Claude Code globally, or scope it to one repo via ./.claude/settings.local.json, which yoink offers to add to your .gitignore before writing.
• Careful writes. Harness configs are written atomically with owner-only permissions and backed up once to <file>.yoink.bak (except the per-provider Goose and Claude Desktop files, which yoink owns and deletes on disconnect). In Claude Code, yoink only ever touches seven managed ANTHROPIC_* / CLAUDE_CODE_SUBAGENT_MODEL keys and warns before writing a key into a git-tracked file.
• Scriptable. Every provider flow has a non-interactive form with the key read from stdin, and list, current, harnesses, presets, status and probe print JSON for scripts.
• Terminal or menu bar. The CLI runs on macOS, Linux and Windows; the macOS menu bar app covers Claude accounts and providers with no terminal.
• One binary. bun build --compile bakes the CLI, its deps and the runtime into a single file. No Node, no runtime to install.

Full flags in usage and the CLI reference.

Run yoink add, pick Provider (API key), choose a preset or Custom, paste the key, pick models, and tick the harnesses to connect. Or do it in one line from a script, with the key on stdin:

echo "$FUSE_API_KEY" | yoink add --external --name fuse --provider Fuse \
  --base-url https://api.fuse.example/v1 --models claude-sonnet-4-5,gpt-5.2 \
  --connect pi,opencode,omp --default claude-sonnet-4-5 --token-stdin

yoink harnesses

● Claude Code  no providers  /Users/you/.claude/settings.json
● pi           fuse  /Users/you/.pi/agent/models.json
● omp          fuse  /Users/you/.omp/agent/models.yml
● opencode     fuse  /Users/you/.config/opencode/opencode.json
○ codex        not installed  /Users/you/.codex/config.toml

yoink probed the URL, found which protocols Fuse speaks, looked the two models up on models.dev, and wrote a provider entry into each harness with claude-sonnet-4-5 as the default. Later changes follow everywhere:

yoink models fuse --set claude-sonnet-4-5,gpt-5.2,kimi-k2   # re-syncs pi, omp, opencode
yoink connect fuse --to claude-code                         # makes Fuse Claude Code's backend
yoink disconnect fuse --from opencode

codex only connects to providers with an OpenAI Responses endpoint, and Claude Code holds one backend at a time, so connecting a provider there switches the active profile. Goose, Zed, and Claude Desktop are experimental: yoink writes their config, then prints a short notice when one more step is needed, such as exporting the key or selecting the config inside the app. See providers and harnesses for the full flow.

Chat is OpenAI Chat Completions, Responses is the OpenAI Responses API, and Messages is Anthropic Messages, each listed in the harness's order of preference.

Claude Code keeps your login in the macOS Keychain under the service Claude Code-credentials on macOS, and in ~/.claude/.credentials.json on Linux and Windows. A profile pairs that credential blob with the oauthAccount identity from ~/.claude.json. A switch:

1. Re-snapshots the currently active profile from the live credential store.
2. Writes the target profile's credential blob back (Keychain entry on macOS, .credentials.json elsewhere).
3. Restores the target profile's account identity into ~/.claude.json.

Profiles live in ~/.config/yoink/profiles.json on every OS (chmod 600 on POSIX). Full details in how it works.

macOS (Apple Silicon and Intel), Linux (x64 and arm64, both glibc and musl/Alpine), and Windows (x64 and arm64). On macOS, credentials are swapped through the login Keychain via the security CLI; on Linux and Windows, through ~/.claude/.credentials.json, written atomically with the same protections Claude Code itself applies. The installers and npm package ship prebuilt binaries for every platform, so nothing else is needed. On bare Alpine, run apk add libstdc++ libgcc once (the same runtime libraries Node needs there).

Full guides live at yoink.codes and in docs/:

• Getting started
• Usage
• Interactive menu
• Providers
• Harnesses
• Subscriptions
• How it works
• Development · Contributing

bun install
bun run dev        # web dev server + CLI test watcher (mprocs)
bun run build      # build every app (turbo)
bun run test       # run every app's tests

Build the CLI from source and link it:

cd apps/cli && bun run build
ln -sf "$PWD/dist/yoink" ~/.local/bin/yoink

See docs/development.md for the monorepo layout, release flow, and architecture.

MIT © Majid Raimi