A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 18%
Response Time: -
First Timer Success: 15%
farion1231/cc-switch has a recorded first-timer success rate of 14.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in farion1231/cc-switch respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 63.0 places farion1231/cc-switch in the A tier.
The external contributor pull request merge rate for farion1231/cc-switch is 17.5%, based on public PR activity from non-core contributors.
farion1231/cc-switch currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (71% critical review signals). Ensure PRs strictly follow guidelines before requesting review in farion1231/cc-switch.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/farion1231/cc-switch?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (22% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
例如启用了Claude Code, Codex和OpenCode，聚焦在Codex，关闭CC Switch应用，再次启动默认显示Claude Code，而非Codex。 同样的步骤在WSL的Linux版CC Switch以及Win10测试也没有问题。在我的Win 11启动时会闪一下，然后软件打开后显示第一顺位的应用。 CC Switch v3.20.1，Win 11 OS Originally posted by @ramonmi in #6921
Summary The built-in minimax-m3 pricing row currently uses these USD rates per million tokens: Input: $0.60 Output: $2.40 Cache read: $0.12 Cache write: $0 MiniMax's current pay-as-you-go page marks the 50% discount as permanent. For requests with up to 512K input tokens, the effective rates are $0.30, $1.20, and $0.06. The current row therefore makes usage cost estimates twice the billed amount for the standard context tier. Official pricing: https://platform.minimax.io/subscribe/token-plan?tab=api-enterprise Current row: cc-switch/src-tauri/src/database/schema.rs Line 2168 in ff3bc24 ("minimax-m3", "MiniMax M3", "0.60", "2.40", "0.12", "0"), The 512K–1M tier uses $0.60, $2.40, and $0.12, but the current pricing table stores only one rate per model. Using the standard ≤512K tier here is consistent with how the catalog handles other models without context-tiered prici
Self Checks / 自检 I have read the FAQ section in README. 我已阅读 README 中的常见问题。 I have searched for existing issues, including closed ones. 我已搜索过已有的 Issue，包括已关闭的。 Related App / 涉及应用 General / 通用 Problem or Motivation / 问题或动机 感谢作者开发了这么好用的 CC Switch 工具！在日常管理大量 Skills 的过程中，它极大地提升了效率。随着管理规模的扩大，目前遇到了几个关于“组织管理”和“Hermes 整合”的痛点，希望能提供以下几点功能支持： 1. 支持在 Skill 列表中使用文件夹进行分类管理 现状 (Problem)：目前 CC Switch 中的 Skill 是完全平铺显示的。当 Skill 数量变多（比如达到几十个）时，查找和管理会变得非常混乱。 建议 (Solution)：希望可以在软件中引入“文件夹/分类 (Categories/Folders)”的概念，允许用户创建文件夹，将不同的 Skill 分门别类地归纳
Problem The ~/.cc-switch/ directory and database files (cc-switch.db) are created without explicit permissions, inheriting the system default umask (typically 0o755 for directories and 0o644 for files). This allows other users on the same machine to read these files. Current State Some sensitive files already have strict permissions set: settings.json → 0o600 (settings.rs:504) copilot_auth.json → 0o600 (copilot_auth.rs:1282,1288) codex_oauth_auth.json → 0o600 (codex_oauth_auth.rs:817,823) Gemini .env file → 0o600, parent dir → 0o700 (gemini_config.rs:170,185) However, the following locations lack permission protection: ~/.cc-switch/ directory itself — created via multiple create_dir_all() calls with no explicit permissions (config.rs:184,198,206, database/mod.rs:101, database/backup.rs:63,309, etc.) cc-switch.db database — created via rusqlite::Connection::open() with no explicit permissions (database/mod.rs:104) Backup database files — same issue (database/backup.rs
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to farion1231/cc-switch, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of farion1231/cc-switch acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 17.5% were successfully merged into the primary branch.
farion1231/cc-switch has a recorded first-timer success rate of 14.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 63.0 places farion1231/cc-switch in the Welcoming tier.
The external pull request merge rate is 17.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, farion1231/cc-switch currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for farion1231/cc-switch are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.