Connect subscriptions in magpie, then set context separately for each agent

Connect subscriptions in magpie, then set context separately for each agent

If several coding agents share your subscriptions through magpie, they can now have separate context-window settings. The project's November 12 release notes for v0.1.3920 add individual agent context windows and a separate compact-at setting for routing groups. That gives users another configuration control; it is not an announcement that the underlying models can hold more context. The release notes do not specify where to change these settings, their units or their defaults, so they are not yet a basis for setup instructions.

Connect the account before choosing the agent's model

For the existing subscription connection, the subscription guide describes a short setup: add a provider in Providers, select the subscription and finish signing in on the vendor's browser page. Then choose a model on the relevant row in Agents.

magpie does not put one coding agent inside another. It runs a gateway on your computer, translates between interfaces and writes the gateway address and key into each supported agent's configuration. The gateway key is distinct from an upstream API key. The guide lists Claude Pro, Max and Team, and ChatGPT Plus, Pro and Business as supported plans. These subscription routes do not require buying a separate API key. The magpie website lists the software as free; upstream subscriptions remain a separate expense.

Some dependencies remain. Requests using a Claude subscription pass through the locally installed Claude Code, which must stay installed. For Gemini, the guide specifies Code Assist Standard or Enterprise with its own Google Cloud project. A successful sign-in elsewhere is not enough to establish that this route will work.

A new connection does not create more allowance

Run magpie accounts to check each account's allowance usage. magpie also documents selection of multiple accounts and fallback models for exhausted quotas, rate limits or outages. Check whether a fallback model suits the task, not merely whether it returns a response. Moving a subscription behind a gateway should not be treated as acquiring additional usage.

There is also a simpler alternative for a narrower need. If the goal is only to use a ChatGPT Plus or Pro subscription in OpenCode, OpenCode documents direct sign-in. It explicitly says usage counts against the plan even though the models show no cost. That display does not mean the subscription itself is free.

Our recommendation is to keep the direct route when one agent already provides what you need. magpie becomes more useful when several agents need shared account management. Its practical benefit is avoiding repeated configuration work, not removing upstream restrictions.

Before switching broadly, retain the original configuration and check model selection, tool calls and allowance changes with one agent. To restore an agent's previous configuration, run magpie <agent> default, replacing <agent> with the target agent's name, such as claude or codex.

Share this article