magpie

One place to pick every agent's model: Codex on DeepSeek, Claude Code on Kimi, Gemini CLI on GLM, from the menu bar. usemagpie.ai

magpie is a single screen that lists each AI agent on your machine and the model it is set to. Click a value, pick a model. That is the whole app.

It lives in the menu bar: click the icon and a panel drops down; the same screen also opens as a normal window (magpie, or Open magpie in the tray menu), and there is a terminal version (magpie tui) and a plain CLI.

  ◉ magpie

  ▸ Claude Code   claude-fable-5-1[1m]                        ~/.claude/settings.json
    Codex         gpt-6-astra   effort medium
    Gemini CLI    gemini-3.1-pro
    OpenCode      anthropic/claude-sonnet-5   small anthropic/claude-haiku-4-5
    MiMo Code     anthropic/claude-sonnet-5
    Pi            openrouter/z-ai/glm-5.2:batch
    Goose         anthropic/claude-sonnet-5
    Cursor        auto
    Copilot CLI   claude-fable-5

  ↑↓ agent  ·  ←→ field  ·  ↵ change  ·  s save profile  ·  p profiles  ·  q quit

• One small binary. Under 15 MB with the desktop app (it uses the system webview through Wails, nothing bundled), 7 MB for the terminal-only build. macOS, Linux and Windows.
• Edits config files surgically. Only the one key you change is touched; comments, ordering and indentation in your settings.json, config.toml, opencode.jsonc or config.yaml survive intact. Writes are atomic.
• One endpoint for every agent. magpie runs a local gateway that speaks OpenAI chat completions, OpenAI Responses and the Anthropic Messages API, and forwards to whichever vendor serves the model. Codex, Claude Code, OpenCode and the rest all point at http://127.0.0.1:3425/v1 and pick from one catalog; the translation between APIs happens in magpie, streaming and tool calls included.
• Your subscriptions, shared. Sign in to Claude Code, Codex (ChatGPT) or Copilot and that login shows up as a provider: every other agent can use its models through the gateway, with nothing copied and no key to paste.
• Providers with one field. Pick a preset (Anthropic, OpenAI, Gemini, DeepSeek, Kimi, GLM, MiniMax, StepFun, Qwen, Baidu Qianfan, Tencent Cloud Token Plan, Huawei Cloud MaaS, Volcengine Ark, Mistral, Groq, xAI, OpenRouter, Together, Fireworks, SiliconFlow, NVIDIA NIM, ModelScope, AiHubMix, 302.AI, Ollama, LM Studio…), paste a key, done. Custom vendors need a name and a base URL. magpie never reads keys from your shell environment.
• Real model lists, nothing compiled in. With a key in hand magpie asks the vendor which models it serves and offers exactly those; the models.dev catalog fills in names, reasoning efforts and the list for vendors that have none, and refreshes itself in the background once it goes stale. Choose which models each provider exposes, or expose them all — a model released this morning is in the picker on the next refresh.
• Each agent's own model list. Under an agent's name on the Agents page, "Showing 5 / 32 models" opens its list: click a model to take it out of that agent's picker (Codex's /model included, its ChatGPT models too) or put it back; other agents still use it, and a new model is shown.
• Profiles. Snapshot every agent's settings under a name and switch all of them back in one move.
• Real logos, no framework. Plain HTML over the system webview; brand icons from lobehub/icons.

Agents

| Agent | File | Fields | | ------------ | --------------------------------- | --------------- | | Claude Code | ~/.claude/settings.json | provider, model, opus/sonnet/haiku/fable (through magpie) | | Claude Desktop | Claude/ + Claude-3p/configLibrary/ in ~/Library/Application Support (%LOCALAPPDATA% on Windows, ~/.config on Linux) | provider (its third-party gateway mode: Code and Cowork on magpie, no Anthropic sign-in; restart Desktop) | | Codex | ~/.codex/config.toml | provider, model, effort | | Gemini CLI | ~/.gemini/settings.json, ~/.gemini/.env | auth, model | | OpenCode | ~/.config/opencode/opencode.json(c) ($OPENCODE_CONFIG_DIR) | model, small | | OpenChamber | ~/.config/openchamber/preferences.json ($OPENCHAMBER_DATA_DIR; magpie's provider in OpenCode's config) | model, small (its own defaults, over OpenCode's) | | MiMo Code | ~/.config/mimocode/mimocode.json(c) | model, small | | Pi | ~/.pi/agent/settings.json | model | | OmO (omo-ai) | ~/.omo/agent/settings.json (+ models.json; $OMO_CODING_AGENT_DIR, $SENPI_CODING_AGENT_DIR) | model | | Goose | ~/.config/goose/config.yaml | model | | Cursor CLI | ~/.cursor/cli-config.json | model | | Copilot CLI | ~/.copilot/settings.json | model | | Crush | ~/.config/crush/crush.json | large, small | | DeepSeek Harness (dsh) | ~/.dsh/profiles/*/cordis.patch.yml ($DSH_HOME; a custom provider, Magpie), or ~/.dsh/config.yaml before dsh 0.1.5 | model, effort | | Command Code | ~/.commandcode/settings.json (+ providers.json) | model | | fx | ~/.fx/settings.json | model (a keyless magpie provider) | | omp (oh-my-pi) | ~/.omp/agent/config.yml (+ models.yml) | model | | Devin | ~/.config/devin/config.json (%APPDATA%\devin\config.json on Windows) | model | | Hermes Agent | ~/.hermes/config.yaml ($HERMES_HOME) | model | | Kimi Code | ~/.kimi/config.toml ($KIMI_SHARE_DIR) | model (a magpie provider; magpie's models in Kimi's /model) | | Muse Code | ~/.config/muse/settings.json ($XDG_CONFIG_HOME) | model (endpoint_transport to the gateway, auth none; magpie's models in Muse's list) | | MiniMax Code (mcode) | ~/.minimax/config.yaml ($MINIMAX_DATA_DIR) | model (a magpie custom provider; magpie's models in its /model) | | Droid (Factory) | ~/.factory/settings.json ($FACTORY_HOME_OVERRIDE) | model (magpie's models as BYOK customModels, in Droid's /model) | | Cline (CLI) | ~/.cline/data/settings/providers.json ($CLINE_DIR) | model, effort (magpie takes its openai-compatible provider) | | Qoder (CLI) | ~/.qoder/settings.json ($QODER_CONFIG_DIR) | model, effort (a magpie custom provider; needs a Qoder plan with BYOK) | | Qoder CN (CLI) | ~/.qoder-cn/settings.json ($QODERCN_CONFIG_DIR) | model, effort (as Qoder; its own accounts, a Qoder CN plan with BYOK) | | Grok Build | ~/.grok/config.toml ($GROK_HOME) | model, effort | | ZCode | ~/.zcode/v2/config.json | provider (magpie's models in ZCode's picker) | | WorkBuddy | ~/.workbuddy/models.json ($WORKBUDDY_CONFIG_DIR) | provider (magpie's models in WorkBuddy's picker) | | OpenHanako | ~/.hanako/provider-catalog.json + agents/<id>/config.yaml ($HANA_HOME; its local API while it runs) | model (the primary agent's; magpie's models as a provider) | | Alma | Alma's local API (localhost:23001, while Alma runs) | model (Alma's default; magpie's models as a provider) |

Provider-scoped agents (OpenCode, MiMo Code, Pi, OmO, Goose, Crush, omp, Hermes Agent) take provider/model. Only agents that are installed or configured are shown.

Providers and the gateway

Every model an agent can pick is spelled provider/model and served by magpie's gateway, so agents never hold vendor keys or vendor URLs. Add a provider, and its models appear in every agent's picker:

magpie presets                          # the vendors magpie knows, grouped: vendors, relays, local
magpie provider add deepseek sk-…       # a preset needs only the key
magpie provider add ollama              # local servers need none
magpie provider add "My Relay" url=https://relay.example.com/v1 key=sk-… models=gpt-5.5,claude-sonnet-5
magpie providers                        # host, key, exposed models, who uses what
magpie provider deepseek                # one provider in detail
magpie provider models deepseek         # re-fetch the vendor's list (add ids to choose which to expose)
magpie provider test deepseek           # one tiny request per API, with latency
magpie provider key deepseek sk-…       # replace the key
magpie provider rm deepseek
magpie models                           # the catalog agents see
magpie claude deepseek/deepseek-chat    # use it

Custom providers take url= (an OpenAI-compatible base), anthropic= (an Anthropic-compatible base), or both, plus responses= when the vendor has a separate Responses endpoint, catalog= to borrow a models.dev list, and models= to name the models to expose. Anything a preset does not know can be overridden the same way.

magpie usage also lists upstream provider keys to help check upstream bills. Each request records the fingerprint and saved name of the key that actually served it, including image calls and account/key failover. The CSV adds provider_key_id and provider_key_name. JSON uses providerKeyId and providerKeyName, distinct from gateway caller keys. System One calls use the same attribution. No raw credential is stored in usage records. Rotating the provider's first key does not move old usage to its replacement; deleted keys keep their historical identity. Older records appear as key not recorded, never inferred from today's configured key. These are upstream credentials, not keys clients use to call Magpie.

One magpie can serve several computers (an office one, a personal one): share it on the network (Settings → Share on local network), and on each other computer add it as a Remote magpie — in the app's Add sheet, or magpie provider add remote-magpie sk-magpie-… url=http://192.168.1.20:3425 id=office. Each computer's own magpie still wires its agents, while the providers, routing groups (office/group/…) and usage are the shared one's. A request goes on in the API the agent spoke — Anthropic Messages, Responses, Chat Completions, token counting — and a model the shared magpie's provider serves on another API only is turned into that API once, never on both computers. Its list is the models the shared magpie's agents are shown, each named with its provider there (Claude Sonnet 5 · Relay A · office), and its image models are listed under Settings → Images and draw through it.

The gateway issues gateway keys for clients, separate from a provider's upstream API keys. Turn on Settings → Share on local network, then open Gateway → Gateway keys → Add gateway key. This block appears only while sharing is on. Create a named key for each client and copy it from its row. Rename, disable, rotate or remove keys independently; rotation and removal ask for confirmation. Rotation keeps the name, enabled state and usage history; other keys are unchanged. While sharing is on, Gateway → Connect offers loopback and shared addresses, plus enabled gateway keys, for all connection examples. With sharing off, Connect keeps the original API key field and local magpie token, without a gateway-key picker. Its arbitrary local option is This computer, distinct from the named Magpie key.

For a headless gateway, use the CLI before exposing the port:

magpie gateway-key add "Remote laptop" # prints the new credential once
magpie gateway-key list                # ids, names, enabled state and masked keys
magpie gateway-key rotate <id>         # prints the replacement; identity stays the same
magpie gateway-key remove <id>         # revokes remote access

While LAN sharing is enabled, remote requests require an enabled gateway key sent as Bearer, x-api-key, x-goog-api-key or ?key=.