DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to keep an agent working when one quota runs out with Magpie

Group two models from different subscriptions so the agent moves to the other one when a quota runs out.

Account pooling. Spreading requests across several accounts may conflict with the terms of the subscriptions involved, so check each vendor's rules before pooling accounts.

Who it is forA developer with two or more subscriptions, such as Claude and GitHub Copilot, who hits quota limits in the middle of work.

The problemWhen one account's quota runs out, the agent stops, and the user has to change models by hand and restart.

The outcomeClaude Code uses one routing group name, and the gateway moves between accounts without the agent seeing an error.

What you need first

  • A computer running macOS, Windows or Linux (or Docker or Termux)
  • An API key for a provider such as DeepSeek, or a signed-in subscription such as Claude or ChatGPT
  • The agent you want to route, such as Claude Code or Codex, already installed

Steps

  1. Install Magpie and sign in to each subscription you want in the group from the Providers page.
  2. Create the group with magpie group add "Opus anywhere" models=claude/claude-opus-5-5,copilot/claude-opus-5.5 routing=smart.
  3. Point Claude Code at the group with magpie claude group/opus-anywhere.
  4. Open the Routing view to see which member each request went to.

Prompt for your agent

Using the yetone/magpie repository, create a routing group named <group-name> with models=<provider/model>,<provider/model> and routing=smart, then run `magpie claude group/<group-slug>`. Report the group definition and confirm the Routing view shows a decision for one test request.

Caveat. The README describes failover between subscriptions you sign in to, and the exact member names depend on which providers you have added.

Share: X LinkedIn Hacker News Email Copy link

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