Member-only story
Forget About CC Switch, Magpie Works Way Better in Practice
CC Switch is basically ready to be uninstalled at this point — I strongly recommend switching to Magpie, and not without reason.
Magpie is quickly becoming the new infrastructure for individuals and teams using AI.
I used CC Switch for a long time before this. It gathers the configs for tools like Claude Code, Codex, and Gemini CLI into a single window, letting you switch providers with one click instead of manually editing config files. Local routing, circuit breaking, MCP and Skills panels, session management, cloud sync — it had everything you'd expect.
For a while I didn't notice any issues, until one time after switching providers, I found that `~/.claude/settings.json` was missing several pieces. The status bar config was gone, all 13 hooks had disappeared, `enabledPlugins` and `extraKnownMarketplaces` had been wiped, the deny rules for specific commands in `permissions.deny` were deleted, and there was an extra environment variable I didn't recognize.
I later figured out the cause: at the time, the way CC Switch saved provider configs was by copying — when you added a provider, it would duplicate your entire current config and store it in its library, then write it back to your file on switch. Starting from version 3.16.5, when switching it now first re-collects the shared portions (`hooks`, `enabledPlugins`, `env`, and the like) from your live `settings.json` into its stored common config, so these changes won't get silently…
