Home/Compare/cc-switch vs zcf

Comparison

cc-switch vs zcf

Verdict

Pick cc-switch when cc-switch is primarily Rust; zcf is TypeScript; pick zcf when zcf is primarily TypeScript; cc-switch is Rust.

Markdown twin · cc-switch alternatives · zcf alternatives

GraphCanon updated today

cc-switch logo

cc-switch

farion1231/cc-switch

116kpushed Jul 11, 2026
vs
zcf logo

zcf

UfoMiao/zcf

6.1kpushed Jul 13, 2026

Trust & integrity

Signalcc-switchzcf
Maintenance
Very active (0d since push)
As of 4d · github_public_v1
Very active (1d since push)
As of today · github_public_v1
Provenance
Not a fork · Personal account
As of 4d · github_public_v1
Not a fork · Organization account
As of today · github_public_v1
OSV dependency advisories
No lockfile (source not queried)
As of 4d · osv@v1
No lockfile (source not queried)
As of today · osv@v1
deps.dev advisories
Not queried
deps.dev@v1
Not queried
deps.dev@v1
OpenSSF Scorecard
Not queried
openssf-scorecard@v1
Not queried
openssf-scorecard@v1

Tagline

cc-switch
A cross-platform desktop All-in-One assistant for multiple AI agents
zcf
Zero-Config Code Flow for Claude code & Codex

Stars

cc-switch
116k
zcf
6.1k

Forks

cc-switch
7.8k
zcf
425

Open issues

cc-switch
1.9k
zcf
49

Language

cc-switch
Rust
zcf
TypeScript

Adopt for

cc-switch
cc-switch is a cross-platform desktop tool for managing AI agents written in Rust and TypeScript.
zcf
-

Persona

cc-switch
-
zcf
-

Runtime

cc-switch
-
zcf
-

License

cc-switch
cc-switch is distributed under the MIT License, allowing free modification and distribution as long as copyright notices are retained and changed licenses do not restrict usage.
zcf
MIT

Last pushed

cc-switch
Jul 11, 2026
zcf
Jul 13, 2026

Categories

cc-switch
AI Agents, Developer Tools
zcf
AI Agents, Developer Tools, LLM Frameworks

Trust and health

Days since push

cc-switch
0d
zcf
1d

Open issues (now)

cc-switch
1.9k
zcf
49

Owner type

cc-switch
User
zcf
Organization

Full report

cc-switch
Trust report

Choose cc-switch if…

  • cc-switch is primarily Rust; zcf is TypeScript.
  • Tags unique to cc-switch: claude code, codex, desktop-app, hermes-agent.
  • If you require seamless interaction with multiple AI agents such as Claude Code, Codex, or Gemini CLI in a single interface.

When NOT to use cc-switch

  • If you are looking for a web-based or mobile app; cc-switch is strictly desktop-focused.
  • Requires manual curation of supported agents, limiting its utility if your primary agent is not included by default.
  • You prioritize the use of proprietary tools over open-source solutions.

Choose zcf if…

  • zcf is primarily TypeScript; cc-switch is Rust.
  • Tags unique to zcf: agent, ai, ai-agent, bmad-method.
  • Also covers LLM Frameworks.

When NOT to use zcf

  • AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism.
  • Developer Tools: A gateway is overkill when you're pinned to a single provider and model.
  • LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.

Explore

Sources

Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.

GitHub stars on cards: cc-switch 116k · zcf 6.1k (synced Jul 11, 2026).

Common questions

What is the difference between cc-switch and zcf?
cc-switch: A cross-platform desktop All-in-One assistant for multiple AI agents. zcf: Zero-Config Code Flow for Claude code & Codex. See the comparison table for live GitHub stats and shared categories.
When should I choose cc-switch over zcf?
Choose cc-switch over zcf when cc-switch is primarily Rust; zcf is TypeScript; Tags unique to cc-switch: claude code, codex, desktop-app, hermes-agent; If you require seamless interaction with multiple AI agents such as Claude Code, Codex, or Gemini CLI in a single interface.
When should I choose zcf over cc-switch?
Choose zcf over cc-switch when zcf is primarily TypeScript; cc-switch is Rust; Tags unique to zcf: agent, ai, ai-agent, bmad-method; Also covers LLM Frameworks.
When should I avoid cc-switch?
If you are looking for a web-based or mobile app; cc-switch is strictly desktop-focused. Requires manual curation of supported agents, limiting its utility if your primary agent is not included by default. You prioritize the use of proprietary tools over open-source solutions.
When should I avoid zcf?
AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism. Developer Tools: A gateway is overkill when you're pinned to a single provider and model. LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.
Is cc-switch or zcf more popular on GitHub?
cc-switch has more GitHub stars (115,863 vs 6,076). Stars measure visibility, not whether either tool fits your constraints.
Are cc-switch and zcf open source?
Yes - both are open-source projects on GitHub (cc-switch: MIT, zcf: MIT).
Where can I find alternatives to cc-switch or zcf?
GraphCanon lists graph-backed alternatives at cc-switch alternatives and zcf alternatives (cc-switch markdown twin, zcf markdown twin), ranked by typed relationship edges rather than popularity votes.
Is there a machine-readable version of this comparison?
Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
Which is better maintained, cc-switch or zcf?
cc-switch: Very active. zcf: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
Where are the full trust reports for cc-switch and zcf?
GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: cc-switch trust report; zcf trust report.

Was this helpful?

Anonymous feedback helps us improve pages and translations.