Magpie vs CC Switch: choose who owns your agent's upstream

The engineering result to aim for is an explainable request path: which model answered, which credentials it used, what happens on failure, and how to restore direct access.

Start with Magpie for shared cross-agent routing, CC Switch for a desktop configuration workspace, Claude Code Router for explicit request policies, or CLIProxyAPI for an account-backed compatible proxy. These are editorial shortlists based on documented emphasis, not measured performance or security rankings. Their capabilities overlap.

AIHubMix prepared this comparison from official documentation checked on November 3, 2026. No hands-on benchmark, reliability test or security audit was performed. Claude Code Router's README lists AIHubMix among its sponsors; that relationship is disclosed, not used as technical evidence.

Define the boundary before choosing the manager

Claude Code, Codex and Gemini CLI own the agent environment: tools, approvals and the conversation loop. A model generates responses; a provider supplies model access. Replacing the upstream does not replace the agent or its permissions.

Separate five operations:

• Configuration switching: change an endpoint, key or model.
• Routing: put a gateway between agent and upstream, possibly translating formats.
• Aggregation: combine model choices; this does not inherently add fallback.
• Account pooling: distribute requests among credentials. Round robin is not guaranteed recovery.
• Fallback: try another configured destination after a qualifying failure.

Protocol names are another boundary. OpenAI Chat Completions and Responses are different APIs; Anthropic Messages and Gemini have their own structures. Documented conversion does not establish lossless tool, reasoning, image or streaming behavior.

Likewise, accepting a compatible base URL is not the same as native configuration integration. Feature coverage differs by client, provider and release. Choose the ownership you need, then validate that exact combination.

Choose a starting point

Use the shortlist to decide what to validate, not to infer exclusive capabilities.

CCR means Claude Code Router. Magpie needs another usable destination for fallback; CC Switch's aggregation has no failover; CCR rules need validation; CLIProxyAPI's desktop companion and statistics are separate components. This is not a measured ranking, and coverage differs by agent and provider.

Magpie: own a shared gateway across agents

Magpie combines native configuration management with a local gateway. Documented integrations include Claude Code, Codex, Gemini CLI, OpenCode, Cline and Cursor CLI. Other compatible clients can use its endpoint without necessarily having a native integration.

The gateway translates OpenAI Chat, OpenAI Responses, Anthropic Messages and Gemini formats. Providers include API-key services, compatible custom endpoints, local servers and supported subscription accounts. Profiles group several agents' configurations.

Routing groups expose multiple models or providers as one selection. Documented policies include order for ordered recovery, rotate for changing members each turn, usage for the least-used member, smart for eligible subscriptions resetting soonest, and pace for remaining weekly capacity relative to reset time. Groups can nest.

Conversation stickiness aims to preserve a useful prompt cache; it does not prove cache continuity across arbitrary provider changes. Optional intent routing asks a selected model to read new turns, without an established guarantee of savings. Fallback also needs somewhere to go: one account without a routing group leaves errors to reach the agent.

Magpie's Library manages instructions, MCP servers, skills and subagents, alongside documented usage, quota, cost and session views. It is not only a router.

Decide privacy settings separately

Masking is off by default. When enabled, it substitutes detected sensitive values locally and restores them in replies, including tool arguments. Detection can miss or misclassify values; the model cannot inspect a masked original. If enabled masking cannot run, the README describes withholding the request with HTTP 503.

The privacy documentation also covers account discovery: Magpie can read existing agent sign-ins, and discovery can be disabled. Release builds describe daily telemetry with a random identifier, version, system and product-use identifiers. Privacy settings or DO_NOT_TRACK=1 disable that telemetry, but partner-link clicks and partner-list fetches are counted independently. The README says those counts retain no identifier or address. A local gateway does not mean no other network activity.

CC Switch: own the desktop workspace, with routing available

CC Switch combines provider management with MCP, skills, prompts, projects, sessions, usage tracking, backups and synchronization. Listed clients include Claude Code, Claude Desktop, Codex, Gemini CLI and OpenCode; features differ by client.

Its three modes have different contracts:

• Direct: connect the agent to the chosen provider. The project says switching preserves unrelated hooks, plugins, MCP settings and comments.
• Routing: forward locally, convert Anthropic Messages, OpenAI Chat Completions, OpenAI Responses and Gemini Native, and use per-tool failover queues, circuit breaking and provider-health monitoring.
• Aggregation: expose multiple providers' models in Claude Code or Codex. Requests follow the chosen model's provider. Aggregation does not provide failover.

Aggregation excludes Claude official subscriptions. Official-login providers generally cannot enter Routing, except for the documented Codex OpenAI Official case. Consult the user manual for the exact client/mode matrix.

Restart requirements matter. Claude Code supports documented hot switching; Direct changes for Codex, Gemini CLI and Grok Build generally require restarting. Routing may still need a restart when the model changes. Codex aggregation-list changes require restarting the relevant daemon, application or editor environment.

The provider-card connectivity check tests reachability, not API-key or model validity. Also, WebDAV/S3-compatible sync is not a complete recovery copy: some device settings, state and original-configuration backups remain local. Data defaults to ~/.cc-switch, with SQLite and associated files.

Claude Code Router: own conditions, credential pools and route inspection

Claude Code Router, or CCR, describes a multi-agent gateway and control plane, not just a Claude Code wrapper. Its README also lists Codex, OpenCode, Pi, Kimi CLI and Grok CLI.

Its emphasis is explicit policy: header/body conditions, prefixes, request rewriting, retries and ordered fallback models. Credential pools and key rotation sit beside agent profiles, model overrides and environment settings.

CCR documents request/response details, resolved provider/model/credential, status, latency, tokens, estimated cost, tool calls and traces. This makes routes inspectable; it does not establish improved task quality, and estimated cost is not an invoice.

Deployment options include desktop applications, an npm CLI with browser management UI, and Docker. The npm CLI requires Node.js 22 or newer. The provider guide covers protocols, custom endpoints and credential pools, and warns that connectivity tests send upstream requests: they can consume paid usage or request limits.

Shortlist CCR when a route must be explainable from rules and logs. More policy branches also mean more combinations to validate.

CLIProxyAPI: own the account-backed endpoint

CLIProxyAPI exposes OpenAI-compatible interfaces including Responses, Gemini-compatible interfaces including Interactions, and Claude-compatible interfaces for clients and SDKs.

Its README documents Codex and Claude Code OAuth, Gemini account access, round-robin multi-account balancing for several providers, configured OpenAI-compatible upstreams and a reusable Go SDK. Endpoint compatibility does not establish that the core project natively rewrites every agent's profiles.

Count the surrounding components separately. The README recommends EasyCLIProxyAPI for graphical configuration, updates, tray controls and service start/stop. Since v6.10.0, CLIProxyAPI and CPAMC no longer ship built-in usage statistics; separate statistics and management projects are referenced instead.

Do not conclude that CLIProxyAPI has no retries, fallback or recovery controls: inspect the selected release's configuration. Conversely, round-robin distribution alone is not a guaranteed cross-model fallback policy.

Proposed acceptance workflow, not a reported test

Use the following before connecting a real project. This is a reader exercise, not a test performed for this article.

1. Capture the baseline. Use a disposable repository and low-privilege test credentials. Back up the original agent configuration and choose one manager to own it.
2. Validate one route. Connect one agent to one provider. Check a plain response and the actual resolved provider/model, not just a connectivity indicator.
3. Validate agent behavior. Ask it to read a harmless file and propose a small change. Verify a complete tool-call/result cycle and streaming completion before permitting writes.
4. Exercise recovery only if needed. Add another route, then use a safe local mock or authorized test setup to check the intended failure condition and alternate destination. Do not deliberately exhaust paid quotas.
5. Check side effects. Confirm retries or recovery do not repeat side-effectful tool actions in your workflow. This is an acceptance criterion, not an observed product defect.
6. Rehearse removal. Stop the manager and verify the documented restore or return-to-direct procedure. Apply restart requirements and reconcile usage estimates with provider records.

Pitfalls outside the model picker

A working login is not permission. OAuth support does not establish provider approval for every cross-client use. CC Switch explicitly warns about subscriptions outside official clients. Check provider terms and organizational rules; a manager adds no entitlement and removes no limits.

Local is still a trust boundary. Review credential permissions, account discovery, backup/sync scope and request-log contents before importing production credentials. Encryption at rest was not verified here. Remote access needs its own authentication and exposure review.

Several configuration owners complicate rollback. Avoid several managers automatically rewriting the same settings. This is an operational precaution, not a demonstrated product bug.

Choose the simplest arrangement that passes acceptance. One agent on its official provider may need no gateway at all. The useful outcome is an explainable, reversible setup—not a winner inferred from feature counts.

Sources

Official sources checked on November 3, 2026:

1. Magpie README — integrations, routing groups, Library and privacy behavior.
2. CC Switch README — modes, client coverage, restarts and storage.
3. Claude Code Router README — agents, rules, credentials and deployment.
4. CLIProxyAPI README — interfaces, accounts, companion software and statistics boundary.
5. CCR provider guide — protocols, pools and test-request costs.