cc-switch Releases

Feature release focused on provider compatibility, OpenClaw editing, Common Config usability, and sync/data reliability. Restores Stream Check UI, adds OpenAI Responses API support, overhauls OpenClaw with JSON5 editing, and upgrades WebDAV sync with dual-layer versioning.

Mar 9, 2026

Adds comprehensive VibeVoice LoRA training and inference support, introduces streaming voice presets, and updates LLM support to include Qwen3.5.

Mar 5, 2026

Significantly improves performance through Faster-Qwen3-TTS integration and introduces Multi-GPU support for TTS, ASR, and LLM subsystems.

Mar 1, 2026

Hotfix release that reverts the Partial Key-Field Merging architecture from v3.11.0 due to critical data loss issues, restoring the proven full config overwrite + Common Config Snippet mechanism.

Feb 28, 2026

Major release adding OpenClaw as the fifth managed CLI application with full provider management, config editors, and workspace support. Introduces Session Manager for browsing conversation history and Backup Management with configurable policies. Includes significant architecture improvements with partial key-field merging for provider switching.

Feb 26, 2026

Introduces Prompt Hub for direct prompt loading, Ollama as an alternative LLM backend, and batch audio generation by paragraph.

Feb 22, 2026

This release focuses on API documentation alignment, refactoring async file handling, and migrating packaging to flit-core, alongside bug fixes for various integrations.

Feb 22, 2026

Enhances output flexibility with multiple formats, embeds metadata directly into audio files, and improves persistent settings management.

Feb 14, 2026

Feature release adding API Format Selector for Claude providers, pricing enhancements with per-provider cost multipliers, Skills ZIP installation support, and Linux ARM64 architecture support. Also adds preferred terminal selection and silent startup options.

Jan 31, 2026

Patch release adding skill sync method configuration and including important bug fixes for prompts, OpenCode serialization, and provider form model fields.

Jan 24, 2026

Patch release focusing on Windows platform bug fixes, UI improvements, and code quality enhancements. Addresses terminal window issues, config path resolution, and visual rendering problems.

Jan 23, 2026

Major release introducing OpenCode as the fourth managed CLI application with full provider, MCP, and Skills management. Adds global proxy settings, Claude Rectifier for thinking signature fixing, enhanced health checks, and per-provider configuration support.

Jan 22, 2026

This release adds socks proxy support and LeakIX API integration, while removing the deprecated Core.bing_key() method and switching CI to Ruff.

Jan 18, 2026

This release focuses on stability and compatibility, including backward compatibility fixes for deprecated models, Gradio 6 support, and a robust timeout mechanism for Python execution.

Jan 16, 2026

Bug fix release addressing critical panic/crash issues including proxy port conflicts, UTF-8 boundary panics with multi-byte characters, and SOCKS proxy support.

Jan 9, 2026

Major release introducing Local API Proxy with per-app takeover, Auto Failover with circuit breaker, Universal Provider for shared config across apps, and comprehensive multi-app workflow improvements across Claude Code, Codex, and Gemini CLI.

Jan 8, 2026

A minor release focused on expanding discovery capabilities with a new module for THC subdomain enumeration.

Dec 31, 2025

A minor release adding macOS tray template icon support, new partner integrations (AiGoCode, DMXAPI), provider icons, and various UI/UX fixes including dark mode visibility and header layout.

Dec 24, 2025

This release mirrors the hotfix found in v5.2.1, correcting the extended query parser behavior in the 4.x branch and clarifying that there is no actual security risk associated with CVE-2024-51999.

Dec 1, 2025

This release serves as a hotfix to revert an erroneous breaking change introduced in version 5.2.0, specifically regarding the extended query parser, and confirms that the associated CVE-2024-51999 is not a valid security vulnerability.

Dec 1, 2025