cc-switch: The Hottest Rust Repo on GitHub Right Now #Shorts
In this video, we break down farion1231/cc-switch - one of the hottest open-source projects on GitHub right now.
A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io. It has already earned 147,675 stars on GitHub and is written primarily in Rust. We look at what it does, why developers are paying attention to it right now, and who should try it.
📂 Repo: farion1231/cc-switch
🌐 Stars: 147,675 | Language: Rust | Forks: 9,726
🔔 Subscribe for daily picks of the hottest GitHub repos: / @reporadar
#github #opensource #programming
keywords: coding, developer tools, github, opensource, programming, software, tech
#Shorts
11 views
cc-switch: The Hottest Rust Repo on GitHub Right Now
In this video, we break down farion1231/cc-switch - one of the hottest open-source projects on GitHub right now.
A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io. It has already earned 147,675 stars on GitHub and is written primarily in Rust. We look at what it does, why developers are paying attention to it right now, and who should try it.
📂 Repo: farion1231/cc-switch
🌐 Stars: 147,675 | Language: Rust | Forks: 9,726
🔔 Subscribe for daily picks of the hottest GitHub repos: / @reporadar
#github #opensource #programming
keywords: coding, developer tools, github, opensource, programming, software, tech
9 views
How to switch Claude Code between API providers in one click with CC Switch (and run GPT in it)
If you use Claude Code with more than one API provider, you know the routine: open ~/.claude/settings.json, swap the base URL, swap the key, swap the model, hope you did not break the JSON, and do it again tomorrow when you hit a limit. Multiply that by Codex and Gemini CLI, which each keep their own config in their own format, and switching becomes a chore you avoid.
CC Switch is a desktop app for Windows, macOS and Linux that does this in one click. Pick a preset, paste a key, press Enable. It manages Claude Code, Claude Desktop, Codex, Gemini CLI, Grok Build, OpenCode, OpenClaw, Hermes Agent, Pi, MiniMax Code, Kimi Code and Oh My Pi, and the README lists 90+ provider presets, including AWS Bedrock and NVIDIA NIM.
This guide covers install, your first switch, running GPT or local models inside Claude Code through its routing mode, and the details that trip people up.
Install
macOS (Homebrew is the recommended route):
brew install --cask cc-switch
Update later with:
brew upgrade --cask cc-switch
The macOS build is universal (Apple Silicon and Intel) and is signed and notarized. On Arch Linux:
paru -S cc-switch-bin
Windows and other Linux users download the .msi, .deb, .rpm or .AppImage from the repo's Releases page. Requirements per the README: Windows 10+, macOS 12+, or Linux with glibc 2.35+ and WebKitGTK 4.1 (Ubuntu 22.04+, Debian 12+).
Working on a server over SSH with no desktop? The README points to the community CC Switch CLI, which shares the same ~/.cc-switch data folder:
brew install cc-switch-cli
Nothing you already have gets lost
On first launch, CC Switch imports your existing Claude Code, Codex, Gemini CLI and Grok Build config as a provider called default, and adds an official provider for each tool. Before it rewrites any config file for the first time, it backs up the original to ~/.cc-switch/backups/live-first-write/.
It also only touches the key fields when you switch: endpoint, key, model and API protocol. Your plugins, hooks, permissions, MCP servers, your own environment variables and even comments in the file stay as they are. That is the main reason to use it over a shell script that overwrites the whole file.
Your first switch
1. Pick the tool in the sidebar (say, Claude Code).
2. Click "+" in the top right and choose a preset, or create a custom config.
3. Paste your API key and save.
4. Select the provider and click "Enable".
Claude Code picks up the change without a restart. Codex, Gemini CLI and Grok Build need you to restart the terminal or the CLI. Claude Desktop needs a full quit and reopen.
You can also switch from the system tray, which shows one row per tool with its current mode, provider and quota.
To go back to your subscription, switch to the built-in "Claude Official" provider and run /login in Claude Code. For Codex, use "OpenAI Official" and codex login.
Use GPT, Gemini or a local model inside Claude Code
Claude Code speaks the Anthropic Messages format. Many providers, and most local model servers, only offer an OpenAI-style Chat Completions endpoint. CC Switch handles this with Routing mode: it runs a local router on your machine that converts between Anthropic Messages, OpenAI Chat Completions, OpenAI Responses and Gemini's native format.
To set it up:
1. Edit the provider and open "Advanced Options".
2. Set "Upstream Format" to match the provider: "OpenAI Chat Completions" for Chat Completions only services (many local servers), "OpenAI Responses API" for Responses endpoints, or "Gemini Native generateContent" for Gemini.
3. On the Claude Code page, open the "Routing" tab and click "Start routing".
The README is direct about the failure mode: choosing the wrong format or forgetting to start routing usually gives you a 404 or 405.
While routing is on, your Claude Code config points at http://127.0.0.1:15721 with a placeholder key PROXY_MANAGED. That is expected. The real address and key live in CC Switch, and "Usage" in the sidebar shows "requested model to actual model" for each request. Quitting CC Switch writes your direct config back first, so Claude Code keeps working without it.
Routing also gives you auto-failover: set a queue of providers per tool, and when a request fails CC Switch moves to the next one. Note that official providers like Claude Official cannot go through routing.
Aggregation: several providers in one model picker
On the Claude Code and Codex pages there is also an "Aggregation" mode. Add a few providers and their models all appear in the tool's own model list, and each request goes to whichever provider owns the model you picked. Two caveats from the docs: aggregation does not do failover, and Claude Code needs version 2.1.243 or later. Switching models mid-session also rebuilds the prompt cache, so the first turn after a switch costs a bit more.
Gotchas
- The model resets after a switch. The model is a key field that belongs to the provider. If you change it with /model inside Claude Code, it lasts until your next switch. To keep it, edit the provider in CC Switch.
- "Connectivity check" passing does not mean your key works. It only checks the address is reachable. If requests fail, check the key, model name and upstream format, and read the request log under "Usage".
- WSL on Windows. Point the tool's config folder at the WSL path (for example \\wsl.localhost\Ubuntu\home\<user>\.claude) in "Settings, App config". For routing, switch WSL2 to mirrored networking, because 127.0.0.1 inside WSL cannot reach the router on Windows in the default NAT mode.
Bonus: one place for MCP, skills and prompts
CC Switch also has panels to add an MCP server or skill once and sync it to each tool, and a prompt library that writes to CLAUDE.md, AGENTS.md or GEMINI.md. Its usage dashboard tracks tokens, cache hit rate and spending per provider and model from each tool's local session logs, even with routing off.
CC Switch or a gateway?
CC Switch is for one developer on one machine who wants to flip providers without editing files. If you need a shared, server-side gateway for a team or an app, look at something like LiteLLM, which lets you call 100+ LLMs with one OpenAI-format API. We compare both kinds in the best AI repos for LLM gateways and routers.
The short version of this guide, with the exact steps and a prompt, lives on the Deduped page for switching Claude Code providers in one click.
---
Get one email every Monday with the week's hottest AI repos and exactly how to use them: subscribe free at dedupedai.com
Mentions
还在手动切换 Claude Code、Codex 和其他编码代理？ 现在，一款桌面应用可以统一管理它们的账户与设置，让切换工具变得像切换标签一样简单 cc-switch 已获得 146k 颗星，背后原因很简单：开发者们早就厌倦了反复登录和手动配置 了解更多 farion1231/cc-switch
@lidangzzz 用简洁的 GUI 管理多个 Agent 应用的供应商、用量、会话历史、MCP、Skills，稳定、原生、低侵入 farion1231/cc-switch
5 popular Claude Code repos, ranked by GitHub stars #shorts Five popular Claude Code related repos by GitHub stars (checked 2026-10-22): anthropics/claude-code 152.9k, farion1231/cc-switch 147.6k, garrytan/gstack 137.3k, stablyai/orca 102.5k, thedotmack/claude-mem 102.3k. This is a hand-picked list, not a complete ranking of GitHub. anthropics/claude-code farion1231/cc-switch garrytan/gstack stablyai/orca thedotmack/claude-mem Independent tutorial channel. Not affiliated with or endorsed by Anthropic.
cc-switch: The Hottest Rust Repo on GitHub Right Now #Shorts In this video, we break down farion1231/cc-switch - one of the hottest open-source projects on GitHub right now. A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io. It has already earned 147,675 stars on GitHub and is written primarily in Rust. We look at what it does, why developers are paying attention to it right now, and who should try it. 📂 Repo: farion1231/cc-switch 🌐 Stars: 147,675 | Language: Rust | Forks: 9,726 🔔 Subscribe for daily picks of the hottest GitHub repos: / @reporadar #github #opensource #programming keywords: coding, developer tools, github, opensource, programming, software, tech #Shorts
cc-switch: The Hottest Rust Repo on GitHub Right Now In this video, we break down farion1231/cc-switch - one of the hottest open-source projects on GitHub right now. A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io. It has already earned 147,675 stars on GitHub and is written primarily in Rust. We look at what it does, why developers are paying attention to it right now, and who should try it. 📂 Repo: farion1231/cc-switch 🌐 Stars: 147,675 | Language: Rust | Forks: 9,726 🔔 Subscribe for daily picks of the hottest GitHub repos: / @reporadar #github #opensource #programming keywords: coding, developer tools, github, opensource, programming, software, tech
How to switch Claude Code between API providers in one click with CC Switch (and run GPT in it) If you use Claude Code with more than one API provider, you know the routine: open ~/.claude/settings.json, swap the base URL, swap the key, swap the model, hope you did not break the JSON, and do it again tomorrow when you hit a limit. Multiply that by Codex and Gemini CLI, which each keep their own config in their own format, and switching becomes a chore you avoid. CC Switch is a desktop app for Windows, macOS and Linux that does this in one click. Pick a preset, paste a key, press Enable. It manages Claude Code, Claude Desktop, Codex, Gemini CLI, Grok Build, OpenCode, OpenClaw, Hermes Agent, Pi, MiniMax Code, Kimi Code and Oh My Pi, and the README lists 90+ provider presets, including AWS Bedrock and NVIDIA NIM. This guide covers install, your first switch, running GPT or local models inside Claude Code through its routing mode, and the details that trip people up. Install macOS (Homebrew is the recommended route): brew install --cask cc-switch Update later with: brew upgrade --cask cc-switch The macOS build is universal (Apple Silicon and Intel) and is signed and notarized. On Arch Linux: paru -S cc-switch-bin Windows and other Linux users download the .msi, .deb, .rpm or .AppImage from the repo's Releases page. Requirements per the README: Windows 10+, macOS 12+, or Linux with glibc 2.35+ and WebKitGTK 4.1 (Ubuntu 22.04+, Debian 12+). Working on a server over SSH with no desktop? The README points to the community CC Switch CLI, which shares the same ~/.cc-switch data folder: brew install cc-switch-cli Nothing you already have gets lost On first launch, CC Switch imports your existing Claude Code, Codex, Gemini CLI and Grok Build config as a provider called default, and adds an official provider for each tool. Before it rewrites any config file for the first time, it backs up the original to ~/.cc-switch/backups/live-first-write/. It also only touches the key fields when you switch: endpoint, key, model and API protocol. Your plugins, hooks, permissions, MCP servers, your own environment variables and even comments in the file stay as they are. That is the main reason to use it over a shell script that overwrites the whole file. Your first switch 1. Pick the tool in the sidebar (say, Claude Code). 2. Click "+" in the top right and choose a preset, or create a custom config. 3. Paste your API key and save. 4. Select the provider and click "Enable". Claude Code picks up the change without a restart. Codex, Gemini CLI and Grok Build need you to restart the terminal or the CLI. Claude Desktop needs a full quit and reopen. You can also switch from the system tray, which shows one row per tool with its current mode, provider and quota. To go back to your subscription, switch to the built-in "Claude Official" provider and run /login in Claude Code. For Codex, use "OpenAI Official" and codex login. Use GPT, Gemini or a local model inside Claude Code Claude Code speaks the Anthropic Messages format. Many providers, and most local model servers, only offer an OpenAI-style Chat Completions endpoint. CC Switch handles this with Routing mode: it runs a local router on your machine that converts between Anthropic Messages, OpenAI Chat Completions, OpenAI Responses and Gemini's native format. To set it up: 1. Edit the provider and open "Advanced Options". 2. Set "Upstream Format" to match the provider: "OpenAI Chat Completions" for Chat Completions only services (many local servers), "OpenAI Responses API" for Responses endpoints, or "Gemini Native generateContent" for Gemini. 3. On the Claude Code page, open the "Routing" tab and click "Start routing". The README is direct about the failure mode: choosing the wrong format or forgetting to start routing usually gives you a 404 or 405. While routing is on, your Claude Code config points at http://127.0.0.1:15721 with a placeholder key PROXY_MANAGED. That is expected. The real address and key live in CC Switch, and "Usage" in the sidebar shows "requested model to actual model" for each request. Quitting CC Switch writes your direct config back first, so Claude Code keeps working without it. Routing also gives you auto-failover: set a queue of providers per tool, and when a request fails CC Switch moves to the next one. Note that official providers like Claude Official cannot go through routing. Aggregation: several providers in one model picker On the Claude Code and Codex pages there is also an "Aggregation" mode. Add a few providers and their models all appear in the tool's own model list, and each request goes to whichever provider owns the model you picked. Two caveats from the docs: aggregation does not do failover, and Claude Code needs version 2.1.243 or later. Switching models mid-session also rebuilds the prompt cache, so the first turn after a switch costs a bit more. Gotchas - The model resets after a switch. The model is a key field that belongs to the provider. If you change it with /model inside Claude Code, it lasts until your next switch. To keep it, edit the provider in CC Switch. - "Connectivity check" passing does not mean your key works. It only checks the address is reachable. If requests fail, check the key, model name and upstream format, and read the request log under "Usage". - WSL on Windows. Point the tool's config folder at the WSL path (for example \\wsl.localhost\Ubuntu\home\<user>\.claude) in "Settings, App config". For routing, switch WSL2 to mirrored networking, because 127.0.0.1 inside WSL cannot reach the router on Windows in the default NAT mode. Bonus: one place for MCP, skills and prompts CC Switch also has panels to add an MCP server or skill once and sync it to each tool, and a prompt library that writes to CLAUDE.md, AGENTS.md or GEMINI.md. Its usage dashboard tracks tokens, cache hit rate and spending per provider and model from each tool's local session logs, even with routing off. CC Switch or a gateway? CC Switch is for one developer on one machine who wants to flip providers without editing files. If you need a shared, server-side gateway for a team or an app, look at something like LiteLLM, which lets you call 100+ LLMs with one OpenAI-format API. We compare both kinds in the best AI repos for LLM gateways and routers. The short version of this guide, with the exact steps and a prompt, lives on the Deduped page for switching Claude Code providers in one click. --- Get one email every Monday with the week's hottest AI repos and exactly how to use them: subscribe free at dedupedai.com
现在一个桌面应用就能管理 Claude Code、Codex 和你跑的其他所有编程智能体的账号和设置 cc-switch 拿了 14.6 万颗星，就是因为大家不想再手动切来切去了 farion1231/cc-switch
3 Trending GitHub Repos: CC Switch, New API & LocalAI – Where Your AI Calls Go Three repositories trending on GitHub today, explained in plain language: what each one does, how it works, who should try it, how to get started, and where the caveats are. This edition is all about the plumbing between AI tools and AI models: a desktop app that switches providers for your coding agents in one click, a self-hosted gateway that puts one API in front of every model provider for a whole team, and an engine that runs models on your own hardware. ⏱ Chapters 0:00 Intro & this week in dev tools 1:39 CC Switch: one app for your coding agents 4:43 New API: a self-hosted AI gateway 8:03 LocalAI: run any model on your own hardware 11:11 Summary 📦 Repos 1. farion1231/cc-switch – CC Switch, by Jason Young (Rust · MIT)farion1231/cc-switch 2. QuantumNous/new-api – New API, by QuantumNous (Go · AGPL-3.0)QuantumNous/new-api Docs: docs.newapi.ai 3. mudler/LocalAI – LocalAI, by Ettore Di Giacinto and the LocalAI team (Go · MIT)mudler/LocalAI Docs: localai.io 📰 News mentioned • OpenCode Console breach exposes stored API keys (Oct 17): techcrunch.com • VS Code 1.142 adds agent Canvases (Oct 14): code.visualstudio.com • GitHub open source license compliance generally available (Oct 16): github.blog Star counts are as of 21 October 2026. Features and claims are as described in each project's README and release notes; try them in your own setup before relying on them. If you found this useful, like and subscribe for the next round of trending repos. #GitHub #OpenSource #AI #DeveloperTools #LLM
Runner 0.17.0 发布：支持 Claude Code 多账号切换 之前在 V 站介绍过 Runner ，是一个管理 CLI agent 的原生桌面工具，本质是一个类似 terminal multiplexer 的工具，可以在同一个 app 中管理不同平台的 agent cli ，也可以把几个 agent 组成 crew 一起协作沟通。 之前的帖子：[我的第一个 300 stars 开源项目 Runner]( v2ex.com) 这次做 claude 多账号切换的初衷主要是我自己用了两年的 Claude 账号最近被封了，用的是 Max 订阅。并且想要再搞出一个新的 max 账号现在太难了，有 [KYC]( support.claude.com)，加上越来越严格的检查，感觉普通国内用户想稳定用一个 Max 账号的成本已经显著增加了。 从我自己最近的使用情况来看，Pro 账号的检查相对没那么严格，用多个 Pro 的重度用户也多了起来。这样就需要管理几个账号、看各自的用量，也希望换个账号以后还能接着之前的工作继续做。 所以这次 0.17.0 给 Runner 加了 Claude Code 多账号支持，可以在里面分别登录、查看用量，切换账号以后继续之前的对话。这里单独开一帖，配几张图介绍一下。  添加另一个账号  在 Settings → Agents → Claude Code 的 Accounts 里面，可以看到自己原来用的账号，默认叫 Personal 。点 Add account ，给新账号起个名字，再跟着 Claude Code 的浏览器登录流程走一遍就可以了。如果之前已经用独立目录登录过，也可以直接选择那个目录。 添加以后，两个账号的登录会分别保留，平时切换不用再来回退出和登录。  原来的配置可以继续用 我自己用 Claude Code 会配一些 skills 、MCP 和插件，换个账号以后如果这些都要重新弄一遍，还是挺麻烦的。所以添加账号时，可以勾选 Use Personal’s settings ，继续用主账号的全局 CLAUDE.md 、skills 、MCP 和已启用的插件。 这里主账号和当前使用的账号是分开的：主账号提供共享配置，Active 决定接下来用哪个账号启动会话。比如配置一直用 Personal 的，干活时可以切到 Work 。 新账号已有的本地配置和同名 skill 会保留，登录信息也是各自独立的。 换个账号，继续之前的对话 在用量下拉框里选好账号以后，新开的 chat 和新启动的 Claude Code crew 成员就会使用它。已经在跑的会话会继续使用原来的账号。 已有的 chat 如果也想换账号，可以先 Stop ，选好另一个账号，再点 Resume 。Runner 会接着原来的对话继续，不用重新开一个 chat ，再把项目和做到哪一步介绍一遍。 这一版先做了手动切换，不会在额度用完时自动轮换账号。多账号功能目前也只针对 Claude Code 。 账号切换实现对比 做这个功能的时候，也看了社区里一些工具的实现。大致可以分成两类： 1. 通过反代或者 agent gateway 。 客户端先把请求交给一个中间服务，由它选择账号、转发请求，有的还会做协议转换。具体实现也有区别，比如 [Magpie 的 Claude gateway]( github.com/yetone/magpie/blob/main/docs/subsystem…)，是由 gateway 调用真实的 Claude Code ，再由 Claude Code 向 Anthropic 发起请求。 2. 原生 CLI 直连，在本机切换账号。 不额外加模型请求代理，还是由 Claude Code 自己发请求。这里又可以分成替换登录凭据和切换账号目录两种做法，所以 direct mode 不一定就是切目录。 [Anthropic 官方文档里的多账号用法]( code.claude.com)是给每个账号一个独立的配置目录，用 CLAUDE_CONFIG_DIR 来选择。例如个人账号继续直接运行 claude，工作账号用 CLAUDE_CONFIG_DIR=~/.claude-work claude，各自在自己的目录下登录。 对 Runner 来说，我觉得沿用这个官方提供的机制是最稳妥的选择。Runner 本来就在管理本机的 CLI 进程，经常会有几个 agent 同时跑。每个账号保留自己的登录状态和凭据存储，登录、保存凭据和 token 刷新都交给 Claude Code ，Runner 负责启动时选好目录。从登录状态的稳定性和账号凭据管理上，这样我会更放心一些。 Runner 具体怎么做 - 登录和凭据： 添加账号时，在对应目录下运行 claude auth login，走 Claude Code 自己的浏览器登录流程。macOS 上凭据由 Claude Code 放进对应的 Keychain 项，Windows 上放在对应目录的凭据文件里。Runner 保存账号名字、目录等信息，不另外保存一份供切换用的凭据；查看用量时会读取本机凭据，查询对应账号的用量。 - 启动和切换： 原来的账号保持原来的启动方式，额外账号通过 CLAUDE_CONFIG_DIR 指定目录。切换 Active 账号，只影响接下来新开或恢复的会话，已经在跑的 agent 继续用自己的账号。在 Runner 外面直接打开的 Claude Code 也继续使用原来的默认登录。 - 共享配置： 目录分开以后，skills 、MCP 和插件这些也需要处理。Runner 按需链接主账号的 CLAUDE.md 、skills 等内容，settings 、MCP 和插件通过启动参数带入，保留各账号已有的本地文件和插件状态。所以账号可以分别登录，常用配置仍然可以共用。 - 继续原来的对话： Runner 会记住对话文件最初在哪个目录。换账号恢复时，用 claude --resume <原对话文件路径> 接着原来的记录继续，不需要把历史复制到新账号目录，也不用从头开一个 chat 。 和 Magpie direct mode 的区别 [Magpie 的 direct mode]( github.com/yetone/magpie/blob/main/internal/provi…) 会记住多个账号的凭据，切换时先保存当前账号的最新凭据，再把选中账号的凭据写回 Claude Code 原来使用的位置。这样配置和历史可以一直留在同一个目录，切换工具需要处理凭据的保存、替换和刷新后的同步。 Runner 这里切的是启动时使用的目录，每个账号的凭据留在各自的存储里。相应地，Runner 要多处理共享配置和跨目录恢复对话。这是两种实现各自需要处理的事情，也和 Runner 本身就管理会话的功能有关。 另外，Magpie 的 [gateway 内部也会给 Claude 账号使用独立目录]( github.com/yetone/magpie/blob/main/internal/provi…)。所以这个区别具体说的是它切换原生 Claude Code 登录的 direct mode ，独立目录也不是 Runner 特有的做法。 和 CC Switch 的区别 [CC Switch]( github.com/farion1231/cc-switch/blob/main/README.…) 在 Claude Code 这一侧主要是切换 provider 配置。Direct 模式会修改配置里的 endpoint 、key 、模型等字段； Routing 模式则让请求经过它的本地路由，可以做协议转换和故障切换。Claude Official 使用 Claude Code 自己的登录，不经过本地 Routing 。 按它目前的文档，Accounts 里的多订阅账号管理列出的是 ChatGPT 、GitHub Copilot 和 Grok 。它的 Claude provider 切换，和 Runner 这次做的几个 Claude 订阅账号各自登录、切换后继续同一个会话，处理的需求有所不同。 下载和反馈 Repo： yicheng47/runner 官网： runnersh.dev 下载： runnersh.dev 版本说明：[Runner 0.17.0]( github.com/yicheng47/runner/releases/tag/v0.17.0) 支持 macOS （ Apple Silicon ）和 Windows x64 （ Windows 10 1809 及以上）。 有多个 Claude 账号的朋友可以试试看，有问题在楼里反馈，或者到 GitHub 提 issue 都可以。也欢迎分享自己平时是怎么切换账号的，看看还有哪些地方可以做得方便一点。
CC Switch حسابهای Coding Agent رو مدیریت میکنه برای جابهجایی بین Claude Code و Codex، تنظیمات و حسابها رو یکجا نگه میداره. اوپنسورس و دسکتاپیه. farion1231/cc-switch