Model or dataset
SaladDay/cc-switch-cli avatar
SaladDay/cc-switch-cli

CC-Switch CLI: a Rust fork that puts seven coding assistants behind one terminal UI

⭐️ A cross-platform CLI All-in-One assistant tool for Claude Code, Codex & Gemini CLI.

5,493 stars337 forksRustMIT

At a glance

What is it?
A downstream CLI fork of CC-Switch that manages Claude Code, Codex, Gemini, OpenCode, Hermes, OpenClaw and Pi from an interactive TUI or a scriptable command line. It promises WebDAV sync parity with upstream and lists its main commands in a Quick Start section.
Who is it for?
Take CC-Switch CLI if you already run CC-Switch and want the same WebDAV synced profiles from a terminal, or if you script assistant switching across Claude Code, Codex, Gemini, OpenCode, Hermes, OpenClaw and Pi. Pass on it if you need a parity table against upstream, since the README names only WebDAV sync as compatible.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 3 days ago.
What is it written in?
Mainly Rust, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • SaladDay/cc-switch-cli5,493 ★ · +330
Star history
Repository2026-09-232026-11-15
SaladDay/cc-switch-cli5.2k5.5k

330 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

A downstream fork, not an independent switcher

CC-Switch CLI is not an independent tool. It is described as a CLI fork of CC-Switch, the upstream project hosted at github.com/farion1231/cc-switch, so it inherits whatever that project already decided about how assistant configuration is stored and switched. The fork keeps Rust as its primary language, ships under the MIT license, and develops on the `main` branch.

What that means in practice is that you are adopting a downstream copy. `CHANGELOG.md` is linked from the top of the README, and the fork's own tags live on the releases page at github.com/saladday/cc-switch-cli/releases, linked there twice. Read those two documents rather than assuming this tool designs its storage from scratch, because the fork relationship decides the data model for you. The README makes exactly one compatibility promise in its own words, which the next section unpacks.

Seven assistants, one binary, two ways in

One tool fronts seven coding assistants: Claude Code, Codex, Gemini, OpenCode, Hermes, OpenClaw, and Pi. The same binary offers two ways in, an interactive TUI for switching by hand and a scriptable command line for automation. The project describes itself as a cross platform CLI all in one assistant tool for Claude Code, Codex and Gemini CLI. At the repository root, `scripts/` and `docs/` sit beside the Rust sources, which is where a wrapper or a usage note would live.

The README's Quick Start lists the main verbs: `cc-switch` opens the TUI, `cc-switch provider list` lists providers, `cc-switch provider switch <id>` or `cc-switch use <id>` switches the global provider, and `cc-switch start claude <id>` or `cc-switch start codex <id>` launches a session with a provider without switching globally.

WebDAV sync is the one promise the fork states out loud

The single compatibility claim the fork makes is WebDAV sync, described as fully compatible with the upstream project. That sentence carries weight for anyone already running CC-Switch, because WebDAV sync is the route through which profiles travel between machines. Inheriting that compatibility means a team can move from the upstream application to this CLI, and back, without re-entering every profile by hand.

The limit is that it is the only feature named. Parity for any specific behavior has to be verified by reading the fork's changelog next to the upstream release notes. Treat the sentence as a promise about one feature, not as a blanket claim about the whole feature set.

The install path is a release page and three files at the root

Installation runs through the release page, which the README links at the top, and the repository root carries the alternative routes: an `install.sh`, a Nix `flake.nix` with its `flake.lock`, plus `scripts/` and `docs/`.

bash
install.sh
flake.nix
flake.lock
scripts/
docs/
src-tauri/
CHANGELOG.md
AGENTS.md

None of that is a command you can paste. The binary is invoked as `cc-switch`, and the choice of artifact and platform stays with you. Two files hint at what the maintainers use themselves: `flake.nix` for a Nix based setup and `install.sh` for a shell based one. `src-tauri/` matches the Rust primary language, and `AGENTS.md`, `CLAUDE.md` and `README_ZH.md` sit in the root, so agent instructions and the Chinese translation travel with the repository rather than with a manual. Read the release assets before you script the install.

Three tags in three weeks on the 5.10 line

The release line moves fast. Three tags landed inside two weeks: v5.11.1 on 2026-10-12, v5.11.2 on 2026-10-16 and v5.11.3 on 2026-10-22, and the last push is dated 2026-10-25. That cadence suits a switching tool, where new assistant endpoints and new client releases appear constantly, and it is a warning for unattended automation.Pin a tag in anything that runs on a schedule and upgrade on your own terms. The release titles match the tags one for one, which means a script can key on either the tag or the name.

The sponsor wall is the loudest part of the front page

After the About paragraph, the README is mostly sponsor copy. Long promotional blocks advertise API relay vendors including 88API, APIMart, Cubence, OpenModel, PackyCode and DDS Hub, several quoting discount codes such as `cc-switch-cli` and `CCSCLI` alongside referral rates. The whole project description is three lines long: a CLI fork, WebDAV sync compatibility, and a link to the changelog.

For a reader this is a documentation problem, since the useful facts sit underneath relay advertising that reads like instruction text. It also says something about the audience. The people this project serves send model traffic through third party relays, which is the same crowd that juggles several assistants and cares about keeping profiles in sync. Two files carry the real weight, `CHANGELOG.md` in English and `README_ZH.md` in Chinese, so read those instead of the front page.

Editorial conclusion

Take CC-Switch CLI if you already run CC-Switch and want the same WebDAV synced profiles from a terminal, or if you script assistant switching across Claude Code, Codex, Gemini, OpenCode, Hermes, OpenClaw and Pi. Pass on it if you need a parity table against upstream, since the README names only WebDAV sync as compatible. Before adopting it in a script, do two things: pin a specific tag rather than tracking `main`, because releases land every few days, and read `CHANGELOG.md` against the upstream CC-Switch notes to see what the fork changed. Anyone pointing this tool at relay endpoints should confirm where those credentials land.

Frequently asked questions

What is a CC switch?

CC Switch is the upstream project at github.com/farion1231/cc-switch, and this repository is a CLI fork of it. The fork manages Claude Code, Codex, Gemini, OpenCode, Hermes, OpenClaw and Pi from one interactive TUI or a scriptable CLI.

How do I use CC-Switch?

Run `cc-switch` for the interactive TUI, or commands such as `cc-switch provider list` and `cc-switch use <id>`. The README describes an interactive TUI and a scriptable CLI covering seven assistants, with WebDAV sync kept compatible with upstream CC-Switch.

What does CLI stand for?

Command line interface. Here it names the mode that makes this project scriptable: the same tool that opens an interactive TUI also runs from a shell, and the project calls itself a cross platform CLI all in one assistant tool.

Is CLI still used today?

The CLI line is still shipping. Three tags arrived in under two weeks, v5.11.1, v5.11.2 and v5.11.3, and the last push is dated 2026-10-25. The project keeps an interactive TUI alongside the scriptable path.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. SaladDay/cc-switch-cli on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/saladday-cc-switch-cli.svg)](https://hysenlabs.com/projects/saladday-cc-switch-cli)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/saladday-cc-switch-cli.svg)](https://hysenlabs.com/projects/saladday-cc-switch-cli)

Was this useful?