Skip to main content

CC Switch

CC Switch can import Claude, Codex, or Gemini setup with the correct service address.

Before configuring​

  • This page uses placeholders only. Copy the real Key from PopGo API keys and the model from models and pricing.
  • One-click setup is for software that is already installed and has registered its protocol handler. Allow the browser to open the external app when prompted.
  • For manual setup, save one minimal Provider first. Enable streaming, tools, or multi-model routing only after the first request succeeds.

Official source and verification​

This page was verified on 2026-07-15 against the official source for CC Switch v3.17.0. Official source. Verification covers all three one-click targets and their endpoint levels.

One-click setup​

Sign in to the PopGo API keys page and open the action menu on the target Key row. Public documentation never creates or displays a link containing a Key. Choose CC Switch, then select Claude, Codex, or Gemini for the target. Inside CC Switch, select Claude, Codex, or Gemini for the intended target and verify the endpoint level.

Manual setup​

Review the Endpoint for each target in CC Switch. Replace only the Key and model placeholders with your own values.

FieldEndpoint
Claudehttps://api.popgo.site
Codexhttps://api.popgo.site/v1
Geminihttps://api.popgo.site
  • The Claude target uses the root address, while Codex uses the /v1 address. Do not mix them in one target.
  • If fields are empty after import, confirm the selected Key-row menu target, then fill the table manually.

Success check​

Save and activate the target setup, then start a new session in the corresponding tool. The first successful request completes verification.

Common errors and recovery​

  • Not installed: install v3.17.0 from the official source, then retry from the Key row action menu.
  • Browser blocked: allow the site to open an external application, then run one-click setup again.
  • Protocol not registered: launch CC Switch once to register its system protocol, then return to the browser.
  • Import failed: confirm the selected target; if it still fails, compare the Endpoint with the table below.
  • For a 401, paste YOUR_API_KEY again and remove surrounding whitespace.
  • For a 404, verify the Base URL level and make sure the client is not appending /v1 twice.