DEDUPED We read 1,000+ AI sources. You read one email. Subscribe free

AI USE CASES

How to point any base-URL tool at one local gateway with magpie

Aim scripts and apps that take an OpenAI, Anthropic or Gemini base URL at magpie's local address.

Who it is forBuilder with a script or editor tool that reads OPENAI_BASE_URL and wants it to use a different model

The problemTools that call one vendor's API cannot easily use other models or your pooled accounts.

The outcomeThe tool sends requests to 127.0.0.1:3425 and gets answers from whichever model magpie routes to.

What you need first

  • macOS, Windows, Linux, Docker or Termux
  • At least one coding agent already installed (for example Claude Code, Codex or Gemini CLI)
  • At least one provider: an API key, a local model server, or a signed-in subscription such as Claude, ChatGPT, Copilot, Gemini or Grok
  • Bun is downloaded automatically the first time a plugin needs it

Steps

  1. Make sure magpie is running with at least one provider added
  2. Run: export OPENAI_BASE_URL=http://127.0.0.1:3425/v1 OPENAI_API_KEY=magpie
  3. Run your tool or script as usual
  4. Check the Routing view to see the request arrive and which provider answered

Prompt for your agent

Using yetone/magpie, configure <TOOL_NAME> to use the local gateway at 127.0.0.1:3425 via its base URL environment variables. Run one request and verify it shows up in magpie's Routing view.

Caveat. A tool that hard-codes its API host or rejects custom base URLs will not work. One user also reported that some apps do not accept magpie as a provider.

About magpie

A menu bar app to pair any coding agent with any model, like Codex on DeepSeek. Part of this week's top 10 repos: ranked #9 on Repo Radar. View yetone/magpie on GitHub.

More with magpie

See all use cases for yetone/magpie

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page