Docs · Sharing

Remote magpie

One magpie can serve several computers. Sign in and set up providers and routing groups once, on the computer that keeps them (your desktop, a server, a NAS in Docker), and on every other computer add that magpie as a provider of its own: a Remote magpie.

The computer you sit at still runs magpie: it wires that computer’s agents, picks their models and keeps their sessions. Only the models come from the other one.

1. Share the main magpie

1. Turn on sharingOn the computer that keeps your providers: Settings → Share on local network → On. magpie then listens on the local network and makes a gateway key named Magpie. The Address row below the switch shows where other computers reach it, such as http://192.168.1.20:3425.
2. Make a key for each computerGateway → Gateway keys, or magpie gateway-key add "Laptop", which prints its sk-magpie-key-…. Each key can have its own daily, weekly or monthly limit and its own models, and its calls are counted under its name.

While sharing is off, a desktop magpie listens on its own computer only, and other computers can’t reach it. A magpie in Docker is reached through its published port instead, and asks every caller outside its container for a gateway key, shared or not; see Docker.

2. Add it on the other computer

You need the address and a key from step 1. Any of these does it:

• The app: on the Providers tab press ＋ Add provider, pick Remote magpie, then give its address and the key.
• The TUI (magpie tui): on the Providers page press a, pick Remote magpie, then type its address and key. On its row, w changes the address and m fetches its list again.
• The CLI:

magpie provider add remote-magpie sk-magpie-key-… url=http://192.168.1.20:3425 id=office
magpie models            # office/… are the shared magpie's
magpie provider refresh office   # fetch its list again

id= names the provider here, and so begins its models’ ids (office/…). The address can be typed as 192.168.1.20:3425 (plain http:// is assumed), with /v1 after it, or as the root: magpie puts every API on it either way. Add one Remote magpie for each computer you share from, with a different id.

What you get

• Its models, as its own agents are shown them: office/relay-a/claude-sonnet-5, labelled Claude Sonnet 5 · Relay A · office. The ids stay ids; only the labels carry the names. Pick them for an agent here like any other model.
• Its routing groups, as office/group/…. The group decides on the shared magpie, with its accounts.
• Every API. A request goes on in the API the agent spoke (Anthropic Messages and token counting, Responses, Chat Completions). A model that the shared magpie’s provider serves on another API only is turned into that API once, never on both computers. Responses go over HTTP, SSE included, not WebSocket.
• Images and video. Its image and video models are found by themselves and served through its image generation and edit, and video, APIs.
• System One. Its decision models (Jev, Clef, and models with names of your own) are set up at its /v1/systemone and appear as decision models, not chat models. Refresh the provider’s list to find new ones. A bare office asks the first decision model listed.
• Embeddings and rerank go to its matching APIs. They stay in agents’ lists as they are on the remote; being listed doesn’t make them able to hold a conversation.
• Prices. Each model costs here what the shared magpie counts it at (a price set there by hand, else its provider’s list price), so the two computers count the same. A price you set here comes first.

Quotas and usage

The Usage page, the menu bar and magpie quota show the shared magpie’s subscription cards, named with it (Codex · office, id office/codex), as that magpie last read them: only the computer with the sign-ins asks the vendors. A card’s refresh here has it read that card once more, at most once every 30 seconds. A Codex reset or a WorkBuddy check-in is pressed on that computer, from its own app, TUI or CLI.

The shared magpie counts this computer’s requests under the name of the gateway key it sends, with the account that answered.

When it doesn’t work

Questions or a setup worth sharing? Ask on Discord. The reference has the details.