yetone/magpie

Quick start

Mac builds are signed and notarised, and every build updates itself. Behind a firewall, use --proxy or --mirror. Or go install github.com/yetone/magpie@latest, or the Docker image.

2 · Add a provider. Open magpie and go to Providers → Add provider. Pick a preset and paste a key, or sign in with a subscription.

3 · Pick a model for each agent on the Agents page. Start a new session and it's on the new model.

magpie finds the subscriptions your agents are signed in to by reading their sign-ins (Claude Code's and Codex's files, the Keychain). To keep it from reading them, turn off Settings → Privacy → Subscription accounts, or run magpie accounts discovery off (on turns it back on). MAGPIENOACCOUNTS=1 turns it off for one run without changing the saved setting. API-key providers work either way.

curl -fsSL https://usemagpie.ai/install.sh | sh

Usage and cost

• Tokens and cost — Tokens, cache reads and writes, reasoning and calls, with cost at list price in dollars or yuan; set your own price for any model
• Quota — Balances and quota windows for every key, plan and account (magpie quota), and a reminder before a window renews with much of it unused
• Sessions — Every agent conversation with its cost and title, reopened in your terminal with one click
• Context — How full each request's context window is, how much came from the cache, and what fills it
• Bills — By account and by upstream key, and OTLP export to your own observability stack

Is magpie for you?

Each agent keeps its model in its own file, in its own format, with its own keys and base URLs. A subscription you pay for works in one agent and nowhere else. magpie puts all of that behind one app and one local gateway:

It's for you if you use more than one agent, more than one provider, or more than one account. If you use one agent on its vendor's own plan and that's enough, you don't need it.

Runs on macOS, Windows and Linux (menu bar app, window, TUI, web UI and CLI), in Docker, and on Termux.

• Pick any model for any agent from one list. magpie edits the one key that matters in the agent's own config.
• Use one provider everywhere: an API key, a local model, or the Claude, ChatGPT, Copilot, Gemini or Grok plan you're signed in to.
• Keep going when a quota runs out: a routing group moves to the next account or model, and the agent never sees the error.

Subscriptions

An agent you're signed in to is a subscription with models behind it, so magpie offers it as a provider to every other agent. Add several accounts per subscription and magpie fails over between them.

Daily warm-up starts each Claude and ChatGPT account's 5-hour window at the times you choose, or the moment the last one resets.

• Claude: drives the real local claude binary and bridges your agent's tools over MCP
• Codex / ChatGPT: your ChatGPT plan's models, in every other agent
• GitHub Copilot, Gemini (Code Assist), Antigravity, Grok (SuperGrok) and more
• Any OpenCode auth plugin or pi package from npm

Every agent's model. One place.

Claude Code on Kimi. Codex on DeepSeek. Gemini CLI on GLM. OpenCode on your ChatGPT plan. Switch any of them from the menu bar. One local gateway serves them all, and when a quota runs out, it quietly moves on to the next account.