mirror of
https://github.com/farion1231/cc-switch.git
synced 2026-08-01 21:26:13 +08:00
Jason
a4bba43f73
The guide used DeepSeek as its Chat-format example, which stopped being accurate once the preset moved to native Responses. It is not obsolete, though: a provider saved before 3.19.1 keeps its stored apiFormat and still carries the "needs routing" badge, and deepseek-v4-pro has no official Codex integration yet, so Chat + routing remains its only path. Rather than swap in a different provider, open with a check for which case the reader is in (badge present/absent/no-routing-support) plus a three-row table for DeepSeek specifically. The title and filename stay put — six published release notes and three sibling guides link here. Also in this pass: - Drop the screenshot of the old boolean "needs local routing mapping" toggle; that control is now Advanced Options -> Upstream Format, a three-way select. The image file stays, since the official-auth preservation guide still references it. - Document the Anthropic Messages format, previously unmentioned. - Fix the Chat-provider list: DeepSeek and MiniMax both moved to Responses, so name Kimi, Zhipu GLM, SiliconFlow and ModelScope. - Note that converting an existing provider keeps the official catalog's capabilities (freeform apply_patch, GPT-5 harness, low/high/max, web_search) but that its stored contextWindow of 1000000 overrides the official 1048576, with two ways to fix it. - Record the direct connection's prerequisites: Codex CLI 0.144.0+ and a ~75 KB catalog file. - Add a usage-attribution section: the provider dimension collapses into Codex (Session), while the model dimension still separates rows. - Reference DeepSeek's official Codex integration and Responses API docs. All UI terms are taken from the locale files so they match what the app actually renders in each language.