CC Switch / CC Switch CLI
This is a configuration manager, not a model. Use official desktop releases. On the main site's API Keys page, use Import to CC Switch if available, or add a custom provider in the corresponding application. Set NekoCloud, your key and the exact group-accessible model ID. Claude Code uses the domain root; Codex uses /v1 and Responses. Save, switch and relaunch as required. Preserve official login settings; do not delete auth.json indiscriminately.
For headless systems see the separately maintained community CC Switch CLI. ccman is another option, but avoid multiple managers writing the same agent config. Consider CCR only when protocol conversion is needed; ordinary direct access needs no additional local proxy.
Verification and safety
Back up existing settings and merge only relevant fields; preserve other providers, plugins, MCP and permissions. Protect keys and backups, never commit them. Variables must reach the actual agent process; Remote SSH, containers and desktop processes have separate environments.
Relaunch, select the NekoCloud model, send a short message and match time, model and charge in Usage. Then read a non-sensitive file in an isolated project and verify the tool call, returned result and final answer. Tests can incur charges. Keep approval controls enabled.
This is adapted from official provider configuration guidance, not proof that every model or the complete NekoCloud tool chain has been tested. Check Model Plaza, key groups and troubleshooting.
Official reference
https://github.com/farion1231/cc-switch