Migrate from CC Switch to magpie: import scope and old Codex sessions (November 2026)

It can import your provider configuration. magpie's README says Import brings in providers from CC Switch, Claude Code, Codex and Alma, and in Providers, under Add provider → Import…, nothing is added until you tick entries and confirm. Imported providers are copies, so later changes in the source app are not copied again. The author also said on X on 2026-11-09 that CC Switch's config can be imported in one click.

Open Sessions → Codex in magpie, press "Move to magpie…" in the notice at the top of the list and confirm in the preview (available from v0.1.999). In issue #887 the reporter explained that they had used Codex through CC Switch, so old sessions carry model_provider custom; once Codex is connected to magpie its current provider is magpie, and Codex's default history list filters out sessions from the old provider, so the history looks gone while the session files are still there. The author replied on 2026-10-05: after you confirm, only the provider marker in the session files and in the threads table of state_*.sqlite changes, the originals are first backed up to magpie's trash folder, the notice has an Undo, sessions written to in the last minute are skipped, and nothing migrates automatically.

Yes. magpie's author wrote on X on 2026-11-09 (in Chinese) that using both also works and to try it before deciding. The two projects describe their own roles this way: CC Switch's README says switching replaces only the connection details (endpoint, key and model) in each tool's config; magpie's README and docs say clients connect to the local gateway at 127.0.0.1:3425, and magpie writes the model you pick into the client's own config file.

First run magpie claude default and magpie codex default: magpie removes what it wrote and restores the values it replaced, such as an ANTHROPIC_BASE_URL you had before. Then pick your provider in CC Switch again and switch. To uninstall magpie, run curl -fsSL https://usemagpie.ai/install.sh | sh -s -- --uninstall; it disconnects every client and puts back what each had first, your settings stay in ~/.config/magpie, and --purge deletes them. magpie's reference says the [model_providers.magpie] table stays in Codex's config.toml so that a thread started on magpie can still be opened.

First check whether the imported QCode entry has a key. magpie keeps keys in ~/.config/magpie/providers.json, readable by you alone, and its docs do not itemize what a CC Switch import carries over. If there is no key, run magpie provider key qcode followed by your cr_ key, or press "Import to magpie" in the QCode dashboard. When magpie already has QCode, importing again from the dashboard does not replace the old key, so change the key with the command above. Also check the three addresses: anthropic https://api.qcode.cc/api, chat https://api.qcode.cc/openai/v1, responses https://api.qcode.cc/openai.

Not necessarily. magpie's own comparison page says CC Switch fits when you mostly switch each tool between providers by hand and want its config left close to how you wrote it, and that magpie fits when you use several agents and want each on a different model. The author also says using both works, and to try it before deciding. For the trade-offs between the two tools, see our page “magpie vs CC Switch: how to choose”.