Pool Your AI Subscriptions: Routing WorkBuddy and Qoder Quotas Through a Single Local Gateway
A local gateway that pools multiple AI subscription quotas into one endpoint is a concrete answer to tool sprawl, though it relies on community plugins and browser/OAuth sessions rather than official multi-platform support. Anyone running several AI coding tools on limited disk space gets a working reference for consolidating both storage and model access.
A developer with a 256 GB Mac running eleven AI coding tools realized the tools were consuming gigabytes of disk space and fragmenting their workflow across chat histories, indexes, and workspace states. The solution they settled on was Magpie, a free, open-source desktop-and-CLI AI gateway that sits between coding agents and model sources, aggregating models from accounts with paid subscriptions, check-in points, and gift quotas into a single local pool.
Magpie supports community plugins for WorkBuddy, WorkBuddy AI, Qoder, Qoder CN, and ZCode, letting the developer log in via browser or device authorization and expose only a curated subset of models to each tool. The article documents the full configuration flow: adding sources, restricting per-tool source visibility, filtering models at the source level, and syncing the catalog so that MiniMax Code, WorkBuddy, and other tools can select from the aggregate list.
The setup works for MiniMax Code and WorkBuddy, with real UI chat verification through ZCode's GLM-5.3-Flash. The Qoder CN IDE native chat does not expose a way to add a custom baseUrl, so that route remains unconfirmed. The article also covers check-in automation for supported sources, time-limited gift quotas that require client-side CAPTCHA, the extra hidden token overhead of app-side requests, and which desktop apps can be uninstalled without breaking gateway login states.
Treating multiple AI coding tools as interchangeable apps misses the point: the thing worth consolidating is model access, not the tool UI. The author's persistence in keeping the gateway despite setup friction shows that quota access matters more than the app itself.
A local gateway's model catalog can go stale between CLI and desktop processes because each keeps its own in-memory snapshot. The observed mismatch between the UI and the running API is a realistic reminder that gateway updates require process awareness, not just file writes.
The heaviest cost of AI coding may not be the inference itself but the per-app context: a two-request verification message consumed 31K input tokens, while a terminal request with a similar purpose used a dozen. The user, not the model, is responsible for understanding this app overhead.
Free event quotas have a materially higher operational cost than paid subscriptions: they require learning vendor rules, catching validity windows, and handling client-side CAPTCHAs. The difference between 'program supports claiming' and 'the account has claimed it' is a distinction most developers can afford to ignore only when paying for usage.
Auto-check-in and gifting systems that work sum to a non-zero amount of maintenance. The author repeatedly notes whether things are verified, which is the practical stance: the plane is repaired, but the flight log is not yet approved.