@cc-x/cc-x 0.4.4 → 0.4.6

package/README.en.md

@@ -1,33 +1,25 @@
 # ccx
 
+> `xx` — one command to switch Claude Code between APIs. **Zero config risk.**
+>
 > [简体中文](README.md) | English
 
-**A Claude Code API switcher** (terminal command `xx`). One command to switch Claude Code
-between the official account and third-party Anthropic-compatible APIs (DeepSeek, Zhipu GLM,
-Xiaomi MiMo…).
-
-What sets it apart from other switchers — **it never writes any Claude Code config file**;
-switching works purely through environment variables. So:
-
-- 🛡️ **Zero config risk**: it never touches `~/.claude/settings.json`, never opens
-  `~/.claude.json` (where MCP lives) — **physically incapable** of losing your MCP / plugins / hooks.
-- 🔀 **Parallel terminals**: each terminal can run a different API without interference (process-level isolation).
-- ⚡ **One command**: pick in `xx`, then use it for this terminal only or set it as the future default.
+Switching Claude Code between the official account and third-party APIs means juggling
+environment variables — or trusting a tool that rewrites your Claude config. ccx takes a
+different path: **switching happens purely at the environment-variable layer.** It never
+reads or writes any Claude Code config file. Your MCP, plugins, hooks — it won't touch them.
 
 ```text
-  cc-x v0.4.4 · Claude Code API switcher     (default = used by bare `claude` in new terminals)
+  cc-x v0.4.6 · Claude Code API switcher     (default = used by bare `claude` in new terminals)
 
    ▶ Official          (default)[Logged in]
      DeepSeek                   [Key set] — work
      智谱GLM                    [No key]
      小米MiMo                   [No key]
 
-     New profile
-     切换到中文
-     Update check: off
-     Exit
+     New profile  ·  切换到中文  ·  Update check: off  ·  Exit
 
-  ↑↓ move · Enter open · Shift+↑↓ (or PgUp/PgDn) reorder · q quit
+  ↑↓ move · Enter open · Shift+↑↓ reorder · q quit
 ```
 
 > **Two builds**: the **native Go build** is recommended — GitHub Releases provide a lightweight
@@ -36,301 +28,217 @@ switching works purely through environment variables. So:
 
 ---
 
-## ccx vs cc-switch
-
-cc-switch is an excellent all-in-one **GUI**; ccx takes the opposite, **minimal** approach:
-
-| | ccx (command `xx`) | cc-switch |
-|---|---|---|
-| Form | Terminal command (lightweight) | Desktop GUI (full-featured) |
-| Scope | Only switches the API | API + MCP + multiple CLIs + prompts… |
-| Touches config files? | **No** (env vars only) | Rewrites config files from its own DB |
-| Can lose MCP / plugins? | **Impossible by design** | Users have reported it overwriting them |
-| Different API per terminal | **Native** (process-level isolation) | Global switch; sessions can interfere |
-
-- **ccx fits you if you** live in the terminal, often run several terminals with different APIs
-  in parallel, have been burned by a switcher corrupting your config/MCP, or just want that one job done.
-- **cc-switch fits you if you** want a GUI, need to manage MCP and several AI CLIs in one place,
-  or prefer an all-in-one tool.
-
 ## Install
 
-> Install **Claude Code** first (`claude` on PATH) — "Use this session" launches it. **Open a new terminal** after installing.
+> Install [Claude Code](https://claude.ai/code) first (`claude` on PATH). **Open a new terminal** after installing.
 
-**Windows native (recommended)**
+**Windows (native, recommended)**
 
 ```powershell
 irm https://github.com/becomeless/cc-x/releases/latest/download/install.ps1 | iex
 ```
 
-Installs to `%LOCALAPPDATA%\Programs\ccx` and adds it to your user PATH.
+The installer chooses a per-user directory and adds it to your user PATH automatically, so no administrator rights or manual PATH edits are needed.
 
-**macOS / Linux native (recommended)**
+**macOS / Linux (native, recommended)**
 
 ```bash
 curl -fsSL https://github.com/becomeless/cc-x/releases/latest/download/install.sh | sh
 ```
 
-Installs to `~/.local/bin` (override with `CCX_INSTALL_DIR`) and verifies `checksums.txt`. If that dir
-isn't on PATH, follow the printed hint.
+The installer places `xx` in a user-level command directory. If that directory isn't on PATH,
+it prints a hint (the Unix installer deliberately doesn't edit your shell config).
 
-**npm, any platform** (needs Node.js ≥ 18)
+**npm (any platform, Node.js ≥ 18)**
 
 ```bash
 npm install -g @cc-x/cc-x
 ```
 
-Open a new terminal and run `xx --version` to verify.
+---
+
+## 60-second quick start
 
-## Quick start (60 seconds)
+The first run of `xx` seeds 4 profiles in `~/.cc-mini/providers.json` (Official + DeepSeek +
+Zhipu GLM + Xiaomi MiMo), **with empty keys**.
+
+1. `xx` → ↑↓ to a profile → Enter → **Edit** → **API key** → paste your key
+2. Then either:
+   - **Use this session** — launch Claude now in this terminal (temporary, parallel-friendly)
+   - **Set default** — bare `claude` in new terminals uses it from now on
+
+```bash
+xx                 # open the menu
+xx DeepSeek        # set as default
+xx DeepSeek -s     # use this session, launch Claude now (--session)
+xx -l              # list all profiles and state (--list)
+xx --help          # all options
+```
 
-1. Open a new terminal and run `xx`. The first run creates 4 default profiles in
-   `~/.cc-mini/providers.json` (Official + DeepSeek + Zhipu GLM + Xiaomi MiMo), **with empty keys**.
-2. ↑↓ to the one you want → Enter → **Edit** → pick **API key** and paste your key (done locally).
-3. Then either:
-   - **Set default**: future **new** terminals running bare `claude` use it.
-   - **Use this session**: launch Claude right now in this terminal (temporary, parallel-friendly).
+---
 
-## Two activation modes (core concept)
+## Two modes (the key concept)
 
-This is the key to ccx. Which API Claude uses is decided by **environment variables**; ccx offers two scopes:
+Which API Claude uses is decided by **environment variables**. ccx offers two scopes:
 
-| | Use this session | Set default |
+| | Use this session (`-s`) | Set default |
 |---|---|---|
-| Mechanism | Sets env vars for **this one process** and launches `claude` | Writes the API as **user environment variables** |
-| Scope | This terminal only, **ephemeral** (gone when you close it) | **New** terminals running bare `claude` use it |
-| Effect on running sessions | **None** | **None** (env vars freeze at process start) |
-| Typical use | Several terminals in parallel, each on its own API | Set your everyday "main API" |
+| Mechanism | Sets env vars on this process + launches `claude` | Writes **user environment variables** |
+| Scope | This terminal only; **gone when you close it** | **New** terminals going forward |
+| Running sessions | Unaffected | Unaffected (env freezes at process start) |
+| Best for | Parallel terminals on different APIs | Set your daily-driver API once |
 
 **Parallel example**: open 4 terminals and run `xx Official -s`, `xx DeepSeek -s`, `xx 智谱GLM -s`,
-`xx 小米MiMo -s` — four Claudes running at once, each on its own API, never interfering.
+`xx 小米MiMo -s` — four Claudes running at once, each on its own API, zero interference.
 
-**Why not switch via a global config file?** Because `settings.json` is shared globally; editing it hits
-**running** sessions (a classic symptom: another terminal suddenly reports `... cannot be parsed as a URL`).
-Environment variables are process-isolated, sidestepping that trap.
+**Why not a global config file?** `settings.json` is shared globally; editing it hits running
+sessions (classic symptom: another terminal suddenly says `cannot be parsed as a URL`).
+Environment variables are naturally process-isolated.
 
-## Command-line usage
+---
 
-```bash
-xx                       # open the interactive menu
-xx DeepSeek              # "Set default" to the profile named DeepSeek
-xx DeepSeek -s           # "Use this session" for DeepSeek and launch Claude (--session)
-xx -l                    # list all profiles and their state (--list)
-xx --lang en             # UI language for this run (zh / en)
-xx --help                # all options
-```
+## ccx vs cc-switch
 
-`xx <name>` defaults to "Set default"; add `-s` / `--session` for "Use this session".
+cc-switch is an excellent full-featured GUI; ccx takes the opposite, minimal approach.
 
-## Menus & editing
+| | ccx (`xx`) | cc-switch |
+|---|---|---|
+| Form | Terminal command (lightweight) | Desktop GUI (full-featured) |
+| Scope | Just API switching | API + MCP + multiple CLIs + prompts… |
+| Touches config? | **Never** (env vars only) | Rewrites config from its own DB |
+| Can lose MCP? | **Physically impossible** | Users have reported it |
+| Parallel terminals | **Native** (process isolation) | Global switch; sessions can clash |
 
-Run `xx` for the main menu: `↑↓` move, `Enter` select, `q` / `Esc` quit. With a profile selected,
-**`Shift+↑↓` (or `PgUp`/`PgDn`) reorders** it, saved instantly.
+- → **ccx**: terminal natives, parallel-session runners, anyone burned by a config-wrecking switcher, "just switch the API" people
+- → **cc-switch**: GUI preference, all-in-one MCP + multi-CLI management
 
-- **Select a profile → Enter** for the action menu: **Use this session** / **Set default** / **Edit** /
-  **Delete** (with confirm; keep "Official") / **Back**.
-- **New profile** — create an empty profile and open the edit form.
-- **Switch to 中文 / English** — instant language toggle, remembered in `lang` in `~/.cc-mini/providers.json`.
-- **Update check: off / notify** — see [Checking for updates](#checking-for-updates).
-- **Exit**.
+---
 
-```text
-  Profile: DeepSeek — work    [Key set]
+## Design philosophy
 
-   ▶ Session    — this terminal only, launches Claude now (great for parallel terminals)
-     Set default — used by bare claude in new terminals (running sessions unaffected)
-     Edit
-     Delete
-     Back
+> ccx cares more about boundaries than features.
 
-  ↑↓ move · Enter select · q back
-```
+Claude Code already has its own config system, MCP ecosystem, and session state. ccx is not trying to become a control panel above it, or to copy user config into another database. It stands at one narrow point before Claude Code starts: prepare the 7 managed environment variables, then let Claude Code run.
 
-**Edit form**: `↑↓` pick a field, `Enter` to change; "Save & back" / "Discard" at the bottom. Inside a
-field, **Enter = keep**, `-` = clear, `Esc` = cancel that field. The first field, **Provider**, is the key
-one: picking a provider (from the preset catalog) **auto-fills** the API URL, the three model mappings, and
-the auth field (providers with multiple URLs let you choose one first); "Note" is free text.
+That constraint is deliberate: no writes to Claude Code config files, no MCP management, no automatic migration, no resident background controller. If process environment variables can solve it, ccx avoids global files; if a choice matters, the user makes it explicitly. Doing less keeps the failure surface small.
 
-```text
-  Edit profile (↑↓ pick a field, Enter to edit; save/discard at bottom)
-
-   ▶ Provider      : DeepSeek
-     Note          : work
-     API URL       : https://api.deepseek.com/anthropic
-     Auth field    : AUTH_TOKEN
-     API key       : ********
-     opus  → model : deepseek-v4-pro
-     sonnet→ model : deepseek-v4-pro
-     haiku → model : deepseek-v4-flash
-     effort level  : max
-
-     Show key in plaintext (now hidden)
-
-     Save & back
-     Discard
-```
+Issues / PRs are welcome, but the direction is clear: **make switching steadier, clearer, and less intrusive** before adding broader management power. Anything that writes a Claude Code config file will not be accepted.
 
-## Configuration reference
+---
+
+## Configuration
 
 ### Fields
 
 | Field | Environment variable | Notes |
 |---|---|---|
-| Provider | — | Picked from the preset catalog; auto-fills URL/models/auth. Also the unique key; duplicates get " 2/3…" |
-| Note | — | Free text to tell apart multiple profiles of the same provider |
-| API URL | `ANTHROPIC_BASE_URL` | Third-party endpoint; empty for Official = use the logged-in session |
-| Auth field | — | Put the key in `AUTH_TOKEN` or `API_KEY` (see below) |
+| API URL | `ANTHROPIC_BASE_URL` | Third-party endpoint; empty for Official = logged-in session |
+| Auth field | — | `AUTH_TOKEN` (default) or `API_KEY`; **wrong one = 401** |
 | API key | `ANTHROPIC_AUTH_TOKEN` or `ANTHROPIC_API_KEY` | Value for the chosen auth field |
-| opus → model | `ANTHROPIC_DEFAULT_OPUS_MODEL` | Model the `opus` tier maps to |
-| sonnet → model | `ANTHROPIC_DEFAULT_SONNET_MODEL` | Model the `sonnet` tier maps to |
-| haiku → model | `ANTHROPIC_DEFAULT_HAIKU_MODEL` | Model the `haiku` tier maps to; **background tasks use it too** |
-| effort level | `CLAUDE_CODE_EFFORT_LEVEL` | Thinking depth, see below |
-
-> ccx **deliberately does not set** `ANTHROPIC_MODEL` or touch `model` in `settings.json`. You pick the tier
-> live with `/model opus\|sonnet\|haiku`, and the mapping translates it to the provider's real model.
-
-### Model mapping & effort
-
-**Why third parties need model mapping:** their endpoints only know their own model names (e.g.
-`deepseek-v4-pro`), while Claude Code calls `claude-*` by default — without mapping it errors out. Background
-tasks use the `haiku` tier, so `haiku → model` **must be set too** (otherwise: "main chat works but errors
-now and then").
-
-**effort (thinking depth):** `low < medium < high < xhigh < max` — higher is smarter but slower and burns
-more tokens; `auto` = model default; empty = unset. Note **effort is a Claude-model feature; whether a third
-party honors it depends on their implementation**.
-
-Reference config per provider (defaults are pre-seeded):
-
-| Profile | BASE_URL | OPUS / SONNET | HAIKU (incl. background) | effort |
-|---|---|---|---|---|
-| Official | (empty = logged-in) | — | — | empty / `auto` |
-| DeepSeek | `https://api.deepseek.com/anthropic` | `deepseek-v4-pro` | `deepseek-v4-flash` | `max` (recommended) |
-| Zhipu GLM | `https://open.bigmodel.cn/api/anthropic` | `GLM-4.7` | `glm-4.5-air` | empty |
-| Xiaomi MiMo | `https://api.xiaomimimo.com/anthropic` (pay-as-you-go)<br>`https://token-plan-cn.xiaomimimo.com/anthropic` (TokenPlan) | `mimo-v2.5-pro` | `mimo-v2.5-pro` | empty |
+| opus → model | `ANTHROPIC_DEFAULT_OPUS_MODEL` | Three-tier model mapping; haiku also covers background tasks — **must be set** |
+| sonnet → model | `ANTHROPIC_DEFAULT_SONNET_MODEL` | |
+| haiku → model | `ANTHROPIC_DEFAULT_HAIKU_MODEL` | |
+| effort level | `CLAUDE_CODE_EFFORT_LEVEL` | `low`–`max`; `auto` = model default; empty = unset. Third parties may not honor it |
 
-> Model names change as providers update; follow each provider's official docs.
+> ccx **deliberately does not set** `ANTHROPIC_MODEL`. Use `/model opus|sonnet|haiku` in-session;
+> the mapping table translates to the provider's real model name.
 
 ### Auth field: AUTH_TOKEN vs API_KEY
 
 | Option | Request header | Used by |
 |---|---|---|
-| `ANTHROPIC_AUTH_TOKEN` (default) | `Authorization: Bearer <key>` | Most third-party relays |
-| `ANTHROPIC_API_KEY` | `x-api-key: <key>` | The official API, and a few relays that only accept this |
-
-The wrong one yields 401. Switch it under "Auth field"; on switch ccx clears the other to avoid a leftover conflict.
-
-## Multiple accounts & maintaining presets
-
-**Multiple accounts**: several keys for the same provider (personal / work)? Just create multiple profiles —
-the second one off the same provider auto-names to `DeepSeek 2`; use **Note** to label them, shown as
-"Provider — Note".
-
-**Maintaining the provider catalog**: `presets.json` (shipped with the tool) is the catalog the "Provider"
-picker reads. Add a provider to offer a new one — no code change:
-
-```json
-[
-  {
-    "name": "DeepSeek",
-    "auth": "AUTH_TOKEN",
-    "effort": "max",
-    "urls": [ { "label": "Anthropic-compatible", "url": "https://api.deepseek.com/anthropic" } ],
-    "models": { "opus": "deepseek-v4-pro", "sonnet": "deepseek-v4-pro", "haiku": "deepseek-v4-flash" }
-  }
-]
-```
+| `AUTH_TOKEN` (default) | `Authorization: Bearer <key>` | Most third-party relays |
+| `API_KEY` | `x-api-key: <key>` | The official API, and a few relays |
 
-- `urls` can hold **several** (e.g. API vs TokenPlan endpoints); you choose one when picking the provider.
-- `models` are the recommended three-tier mapping, auto-filled and still editable. `auth` / `effort` are optional.
-- You can also drop a custom catalog at `~/.cc-mini/presets.json` to override the shipped one (highest priority).
+### Pre-seeded profiles
 
-## Checking for updates
-
-The **Update check** toggle in the main menu is **off by default**. Switch it to **notify** and ccx shows a
-one-line yellow notice atop the menu when a newer release exists, with the upgrade command (it never
-auto-downloads — you decide when to upgrade).
-
-- No GitHub API; checks at most once a day, cached in `~/.cc-mini/update-check.json`; offline/failure is silent.
-- The check runs in the background and won't slow startup — a new version usually shows up on your **next** launch.
-- To upgrade, just re-run the install command (native: the one-liner under [Install](#install); npm:
-  `npm i -g @cc-x/cc-x@latest`).
+| Profile | BASE_URL | OPUS / SONNET | HAIKU (incl. background) | effort |
+|---|---|---|---|---|
+| Official | empty (logged-in) | — | — | — |
+| DeepSeek | `https://api.deepseek.com/anthropic` | `deepseek-v4-pro` | `deepseek-v4-flash` | `max` (recommended) |
+| Zhipu GLM | `https://open.bigmodel.cn/api/anthropic` | `GLM-4.7` | `glm-4.5-air` | — |
+| Xiaomi MiMo | `https://api.xiaomimimo.com/anthropic` | `mimo-v2.5-pro` | `mimo-v2.5-pro` | — |
 
-## First run: skip login / onboarding
+> Model names change as providers update. Xiaomi MiMo has both pay-as-you-go and TokenPlan
+> endpoints; you pick one when selecting the provider.
 
-With a third-party API (token auth), Claude Code **may still show a login / onboarding screen on first
-launch** — because it hasn't recorded "onboarding done". One-time fix: in `~/.claude.json` (Windows:
-`C:\Users\<you>\.claude.json`), **add a single key** to the top-level `{ }` (keep everything else):
+### Advanced
 
-```json
-{
-  "hasCompletedOnboarding": true
-}
-```
+- **Multiple accounts**: create multiple profiles from the same provider — names auto-suffix
+  with ` 2`, ` 3`… Use **Note** to tell them apart, shown as "Provider — Note".
+- **Custom providers**: `presets.json` is the provider catalog; add a JSON entry to offer a new
+  one, no code change. Drop `~/.cc-mini/presets.json` to override the shipped catalog.
+- **First-launch login prompt**: third-party APIs may still show onboarding. Add
+  `"hasCompletedOnboarding": true` to `~/.claude.json` (**only this key** — don't overwrite
+  the file; it also holds your MCP config).
+- **Update check**: toggle to "notify" in the menu — a yellow one-liner appears atop the menu
+  when a new release is out. At most one check per day; never auto-upgrades.
 
-> ⚠️ This file also holds your MCP config — **only add the key, never overwrite the whole file**. ccx
-> deliberately won't edit it for you; it's exactly the file a tool shouldn't touch.
+---
 
-## Data & file locations
+## Data & files
 
-- **Profiles (plaintext keys, keep local)**: `~/.cc-mini/providers.json` (also holds `lang` and `update`).
-- **Provider catalog**: the shipped `presets.json`, or `~/.cc-mini/presets.json` to override.
-- **Update-check cache**: `~/.cc-mini/update-check.json`.
+- **Profiles (plaintext keys, keep local)**: `~/.cc-mini/providers.json` (also holds `lang` and `update`)
+- **Provider catalog**: shipped `presets.json`; override at `~/.cc-mini/presets.json`
 - **"Set default" writes user environment variables** (not Claude config files):
-  - **Windows** → registry `HKCU\Environment` + one change broadcast;
-  - **macOS / Linux** → a `# >>> xx >>>` … `# <<< xx <<<` marker block in the shell startup file
-    (idempotent rewrite, chosen by `$SHELL`).
-  - Same semantics either way: **only affects new terminals**; switching to "Official" clears all managed vars.
-- **It modifies no Claude config file.**
+  - Windows → registry `HKCU\Environment` + one change broadcast
+  - Unix → `# >>> xx >>>` … `# <<< xx <<<` marker block in shell startup file (idempotent rewrite, chosen by `$SHELL`)
+  - Same semantics either way: **only affects new terminals**; switching to "Official" clears all managed vars
+- **No Claude Code config file is ever modified.**
 
-ccx only ever touches these 7 "managed" variables (and clears the ones a target profile doesn't use):
+ccx only touches these 7 "managed" variables (and clears the ones a target profile doesn't use):
 `ANTHROPIC_BASE_URL`, `ANTHROPIC_AUTH_TOKEN`, `ANTHROPIC_API_KEY`, `ANTHROPIC_DEFAULT_OPUS_MODEL`,
 `ANTHROPIC_DEFAULT_SONNET_MODEL`, `ANTHROPIC_DEFAULT_HAIKU_MODEL`, `CLAUDE_CODE_EFFORT_LEVEL`.
 
-> 💡 To change `settings.json`, use Claude Code's own `/update-config` and describe what you want in natural
-> language (e.g. "allow npm commands") — safer than letting an external tool rewrite it.
+> 💡 To change `settings.json`, use Claude Code's own `/update-config` and describe what you want
+> in natural language (e.g. "allow npm commands") — safer than letting an external tool rewrite it.
+
+---
 
 ## FAQ
 
-**Does switching in one terminal affect another running one?** No. "Use this session" is process-level; "Set
-default" only affects **new** processes — running sessions froze their env at start.
+**Does switching in one terminal affect another?** No. "Use this session" is process-scoped;
+"Set default" only affects new terminals.
 
-**I "Set default" but bare `claude` here is still the old one?** Expected — this terminal has the old env.
-**Open a new terminal.**
+**I set default but bare `claude` here is still the old one?** Expected — this terminal has
+the old env. Open a new one.
 
-**Seeing `... cannot be parsed as a URL`?** A profile's API URL is an invalid value; Edit to fix or delete it.
+**Seeing `cannot be parsed as a URL`?** A profile's API URL is invalid. Edit to fix or delete it.
 
-**Set effort on a third party but nothing happens?** effort is a Claude-model feature; third parties may not
-support it. DeepSeek recommends `max`; otherwise leave it empty.
+**Set effort on a third party but nothing happens?** effort is a Claude-model feature; third
+parties may not support it. DeepSeek recommends `max`; leave empty otherwise.
 
-**Are keys safe?** Stored in plaintext under your home dir, protected by your account. Don't commit
+**Are keys safe?** Plaintext in your home dir, protected by your OS account. Don't commit
 `providers.json` to a repo.
 
+**Can I choose the install directory?** Yes. The Windows installer supports `-InstallDir`;
+macOS / Linux supports `CCX_INSTALL_DIR` or `--install-dir`. Most users should keep the default;
+if you change it, pass the same directory when uninstalling.
+
+**Can I download the binary manually?** Yes. Go to [GitHub Releases](https://github.com/becomeless/cc-x/releases/latest),
+download the zip / tar.gz for your platform, extract it, and put `xx` / `xx.exe` somewhere on PATH.
+For most users, the install command above is better: it picks the platform, verifies checksums, and handles PATH / uninstall.
+
+---
+
 ## Uninstall
 
-1. **Clear env vars first**: run "Set default → Official" once in `xx` to clear all managed variables.
-2. **Remove the binary**:
+1. Clear env vars: `xx` → Official → Set default
+2. Remove the binary:
    - Windows native:
      ```powershell
-     powershell -NoProfile -ExecutionPolicy Bypass -Command "$s = irm https://github.com/becomeless/cc-x/releases/latest/download/install.ps1; & ([scriptblock]::Create($s)) -Uninstall"
+     $s = irm https://github.com/becomeless/cc-x/releases/latest/download/install.ps1
+     & ([scriptblock]::Create($s)) -Uninstall
      ```
+     This removes the installed files and automatically removes the matching user PATH entry.
    - macOS / Linux native:
      ```bash
      curl -fsSL https://github.com/becomeless/cc-x/releases/latest/download/install.sh | sh -s -- --uninstall
      ```
-   - npm: `npm uninstall -g @cc-x/cc-x`.
-   - macOS / Linux, if you used "Set default", also delete the `# >>> xx >>>` marker block in your shell startup file.
-3. Delete the data dir `~/.cc-mini/`.
+   - npm: `npm uninstall -g @cc-x/cc-x`
+3. Delete data: `rm -rf ~/.cc-mini`
 
-## Design principles
-
-ccx was born from friction I kept hitting with cc-switch — not a criticism; it's powerful, I just wanted a
-lighter path. So ccx holds one principle: **simpler is better.** Do one job (switch the API); touch as little
-as possible (above all, **never write a Claude Code config file**); before adding a feature, ask whether it
-can be left out.
-
-Issues / PRs welcome — but **changes that make it simpler are more welcome than ones that make it more
-powerful**, and anything that writes a Claude Code config file will not be accepted.
+---
 
 ## License
 

package/README.md

@@ -1,319 +1,221 @@
 # ccx
 
+> `xx` — Claude Code 多 API 切换，一个命令搞定。**不碰配置，不怕翻车。**
+>
 > 简体中文 | [English](README.en.md)
 
-**Claude Code API 切换器**（终端命令 `xx`）。一个命令，在 Claude Code 官方账号与各家第三方
-Anthropic 兼容 API（DeepSeek、智谱 GLM、小米 MiMo…）之间来回切。
-
-它和别的切换工具最大的不同——**绝不写任何 Claude Code 配置文件**，切换纯靠环境变量。所以：
-
-- 🛡️ **配置零风险**：不碰 `~/.claude/settings.json`，更不打开存放 MCP 的 `~/.claude.json`，
-  从设计上**不可能**弄丢你的 MCP / 插件 / hooks。
-- 🔀 **多终端并行**：每个终端可以各用各的 API，互不干扰（进程级隔离）。
-- ⚡ **一个命令**：`xx` 选一下，要么仅当前终端临时用，要么设为以后默认。
+用 Claude Code 连第三方 API？每次手打环境变量太烦，换工具切又怕弄丢 MCP。
+ccx 把这事儿做到了最简——切换只在环境变量层，**不读写任何 Claude Code 配置文件**。
+你的 MCP、插件、hooks，它碰都不会碰。
 
 ```text
-  cc-x v0.4.4 · Claude Code API 切换器     （默认 = 新终端裸敲 claude 用的）
+  cc-x v0.4.6 · Claude Code API 切换器     （默认 = 新终端裸敲 claude 用的）
 
    ▶ 官方            （默认）[登录态]
      DeepSeek                [密钥已设] — 公司
      智谱GLM                 [密钥未填]
      小米MiMo                [密钥未填]
 
-     新增配置
-     切换到 English
-     更新检查：关闭
-     退出
+     新增配置  ·  切换到 English  ·  更新检查：关闭  ·  退出
 
-  ↑↓ 选择 · Enter 进入 · Shift+↑↓（或 PgUp/PgDn）排序 · q 退出
+  ↑↓ 选择 · Enter 进入 · Shift+↑↓ 排序 · q 退出
 ```
 
 > **两个版本**：推荐 **Go 原生版**——GitHub Release 提供轻量 `xx` / `xx.exe`，无需 Node.js，
-> 覆盖 Windows x64、macOS Intel / Apple Silicon、Linux x64 / arm64。偏好 npm 的用户可装
+> 覆盖 Windows x64、macOS Intel / Apple Silicon、Linux x64 / arm64。npm 用户可装
 > `@cc-x/cc-x`（命令仍是 `xx`）。两版功能一致。
 
 ---
 
-## 和 cc-switch 怎么选
-
-cc-switch 是优秀的**全能型 GUI**；ccx 走相反的**极简路线**，两者定位不同：
-
-| | ccx（命令 `xx`） | cc-switch |
-|---|---|---|
-| 形态 | 终端命令（轻量） | 桌面 GUI（全能） |
-| 职责 | 只切 API，一件事做到位 | API + MCP + 多 CLI + 提示词… |
-| 改不改配置文件 | **完全不碰**（纯环境变量） | 以自有数据库为准，重写配置文件 |
-| 会不会弄丢 MCP / 插件 | **设计上不可能** | 有用户反馈被覆盖丢失 |
-| 多终端并行不同 API | **原生支持**（进程级隔离） | 全局切换，易相互影响 |
-
-- **更适合用 ccx**：命令行党、爱敲一下就切；常同时开多个终端各跑不同 API；被“切换把配置 / MCP
-  弄坏”坑过想要零风险；只想要“切 API”这一件事。
-- **更适合用 cc-switch**：想要图形界面、要在一个工具里统管 MCP 和多个 AI CLI、喜欢一站式。
-
 ## 安装
 
-> 需要先装好 **Claude Code**（`claude` 在 PATH 中）——「本次启用」会直接调用它。安装后请**新开一个终端**。
+> 先装好 [Claude Code](https://claude.ai/code)（`claude` 在 PATH 中）。装完**新开一个终端**。
 
-**Windows 原生版（推荐）**
+**Windows（推荐原生版）**
 
 ```powershell
 irm https://github.com/becomeless/cc-x/releases/latest/download/install.ps1 | iex
 ```
 
-装到 `%LOCALAPPDATA%\Programs\ccx` 并加入用户 PATH。
+安装器会自动选择用户级目录并写入用户 PATH，无需管理员权限，也无需手动配置。
 
-**macOS / Linux 原生版（推荐）**
+**macOS / Linux（推荐原生版）**
 
 ```bash
 curl -fsSL https://github.com/becomeless/cc-x/releases/latest/download/install.sh | sh
 ```
 
-装到 `~/.local/bin`（可用 `CCX_INSTALL_DIR` 改目录），并校验 `checksums.txt`。若该目录不在 PATH，按提示加入。
+安装器会放到用户级命令目录；若该目录不在 PATH 中，会打印一行提示（Unix 版刻意不自动改 shell 配置）。
 
-**npm 全平台版**（需 Node.js ≥ 18）
+**npm（全平台，需 Node.js ≥ 18）**
 
 ```bash
 npm install -g @cc-x/cc-x
 ```
 
-新开终端运行 `xx --version` 验证安装。
-
-## 快速上手（60 秒）
-
-1. 新开终端运行 `xx`。首次会在 `~/.cc-mini/providers.json` 生成 4 个默认配置
-   （官方 + DeepSeek + 智谱GLM + 小米MiMo），**密钥为空**。
-2. ↑↓ 选中要用的那家 → Enter → 「编辑」→ 选「API 密钥」填入你的 key（在本机操作）。
-3. 配好后二选一：
-   - **设为默认**：以后**新开**终端裸敲 `claude` 就用它。
-   - **本次启用**：立刻在当前终端启动 Claude（临时、可多终端并行）。
-
-## 两种启用方式（核心概念）
-
-这是理解 ccx 的关键。Claude 用哪个 API 本质由**环境变量**决定，ccx 提供两种作用范围：
-
-| | 本次启用 | 设为默认 |
-|---|---|---|
-| 机制 | 只给**当前终端这一个进程**设环境变量并启动 `claude` | 把该 API 写成**用户环境变量** |
-| 作用范围 | 仅当前终端，**阅后即焚**（关掉就没了） | 之后**新开**的终端裸敲 `claude` 默认用它 |
-| 对运行中会话 | **零影响** | **零影响**（环境变量在进程启动时定型） |
-| 典型场景 | 多终端并行，各用各 API | 设定最常用的“主力 API” |
+---
 
-**并行示例**：同时开 4 个终端分别 `xx 官方 -s`、`xx DeepSeek -s`、`xx 智谱GLM -s`、`xx 小米MiMo -s`，
-得到 4 个同时运行、各用各 API、互不干扰的 Claude。
+## 60 秒上手
 
-**为什么不用全局配置文件来切？** 因为 `settings.json` 全局共享，改它会波及**正在运行**的其它会话
-（典型表现：另一终端突然报 `... cannot be parsed as a URL`）。环境变量天然进程隔离，避开了这个坑。
+首次运行 `xx` 会在 `~/.cc-mini/providers.json` 生成 4 个预设配置（官方 + DeepSeek + 智谱GLM + 小米MiMo），**密钥为空**。
 
-## 命令行用法
+1. `xx` → ↑↓ 选中要用的配置 → Enter → 「编辑」→「API 密钥」→ 填入你的 key
+2. 配好后二选一：
+   - **本次启用** — 即刻在当前终端启动 Claude（临时，多开互不干扰）
+   - **设为默认** — 以后新终端裸敲 `claude` 就用它
 
 ```bash
-xx                       # 打开交互菜单
-xx DeepSeek              # 「设为默认」到名为 DeepSeek 的配置
-xx DeepSeek -s           # 「本次启用」DeepSeek 并立即启动 Claude（--session 同义）
-xx -l                    # 列出所有配置及状态（--list 同义）
-xx --lang en             # 本次界面用英文（zh / en）
-xx --help                # 全部参数
+xx                 # 打开菜单
+xx DeepSeek        # 设为默认
+xx DeepSeek -s     # 本次启用，立即启动 Claude（--session 同义）
+xx -l              # 列出所有配置及状态（--list 同义）
+xx --help          # 全部参数
 ```
 
-`xx <名称>` 默认是「设为默认」；加 `-s` / `--session` 改为「本次启用」。
+---
 
-## 菜单与编辑
+## 两种模式（核心概念）
 
-运行 `xx` 进入主菜单：`↑↓` 移动、`Enter` 选择、`q` / `Esc` 退出。选中某个配置时按
-**`Shift+↑↓`（或 `PgUp`/`PgDn`）可上下移动排序**，即时保存。
+Claude 用哪个 API 由**环境变量**决定。ccx 提供两种作用范围：
 
-- **选中配置 → Enter** 进入动作菜单：**本次启用** / **设为默认** / **编辑** / **删除**（二次确认，建议保留「官方」）/ **返回**。
-- **新增配置** — 新建空配置并进入编辑表单。
-- **切换到 English / 中文** — 界面语言即时切换，记忆在 `~/.cc-mini/providers.json` 的 `lang`。
-- **更新检查：关闭 / 提醒** — 见[检查新版本](#检查新版本)。
-- **退出**。
+| | 本次启用 (`-s`) | 设为默认 |
+|---|---|---|
+| 机制 | 给当前进程设环境变量，启动 `claude` | 写入**用户环境变量** |
+| 作用范围 | 仅当前终端，**关了就没** | 之后**新开**的终端默认用它 |
+| 对正在跑的会话 | 零影响 | 零影响（进程启动时已定型） |
+| 适合 | 多终端并行，各跑各的 API | 定好主力 API，不用老切 |
 
-```text
-  配置：DeepSeek — 公司    [密钥已设]
+**并行示例**：开 4 个终端分别 `xx 官方 -s`、`xx DeepSeek -s`、`xx 智谱GLM -s`、`xx 小米MiMo -s`——四个 Claude 同时干活、各用各的 API、互不打架。
 
-   ▶ 本次启用    — 仅当前终端，立即启动 Claude（并行多终端推荐）
-     设为默认    — 新终端裸敲 claude 默认用它（不影响运行中会话）
-     编辑
-     删除
-     返回
+**为什么不用配置文件？** `settings.json` 全局共享，改它会波及正在跑的会话（典型症状：另一终端突然报 `cannot be parsed as a URL`）。环境变量天然进程隔离，避开了这个坑。
 
-  ↑↓ 选择 · Enter 确认 · q 返回
-```
+---
 
-**编辑表单**：`↑↓` 选字段、`Enter` 改，最下方可「保存并返回」/「放弃修改」。进入某项后**回车 = 不改**、
-输入 `-` = 清空、`Esc` = 取消该项。第一项**「供应商」**最关键：选一个供应商（来自预设目录）后会
-**自动填入** API 地址、三档模型映射、认证字段（多地址的供应商会先让你选一个）；「备注」随你写。
+## 和 cc-switch 怎么选
 
-```text
-  编辑配置 （↑↓ 选要改的项，Enter 进入；↓到底可选保存/放弃）
-
-   ▶ 供应商        : DeepSeek
-     备注          : 公司
-     API 地址      : https://api.deepseek.com/anthropic
-     认证字段      : AUTH_TOKEN
-     API 密钥      : ********
-     opus  → 模型  : deepseek-v4-pro
-     sonnet→ 模型  : deepseek-v4-pro
-     haiku → 模型  : deepseek-v4-flash
-     effort 思考档 : max
-
-     显示密钥明文（当前隐藏）
-
-     保存并返回
-     放弃修改
-```
+cc-switch 是优秀的全能 GUI；ccx 走相反的极简路线。
 
-## 配置详解
+| | ccx (`xx`) | cc-switch |
+|---|---|---|
+| 形态 | 终端命令（轻量） | 桌面 GUI（全能） |
+| 职责 | 只切 API | API + MCP + 多 CLI + 提示词… |
+| 改配置文件？ | **不碰**（纯环境变量） | 会重写 |
+| 能弄丢 MCP？ | **不可能** | 有用户反馈被覆盖 |
+| 多终端并行 | **原生支持**（进程隔离） | 全局切换，容易互扰 |
 
-### 字段
+- → **ccx**：命令行党、常多开终端、被切配置坑过、只想要「切 API」一件事
+- → **cc-switch**：要 GUI、要一站式管 MCP 和多 CLI
 
-| 字段 | 对应环境变量 | 说明 |
-|---|---|---|
-| 供应商 | — | 从预设目录选；选后自动带出地址/模型/认证字段。也是配置唯一标识，同名自动追加「 2/3…」 |
-| 备注 | — | 自己写，用于区分同供应商的多份配置 |
-| API 地址 | `ANTHROPIC_BASE_URL` | 第三方接入点；官方留空＝走登录态 |
-| 认证字段 | — | 密钥放进 `AUTH_TOKEN` 还是 `API_KEY`（见下） |
-| API 密钥 | `ANTHROPIC_AUTH_TOKEN` 或 `ANTHROPIC_API_KEY` | 对应认证字段的值 |
-| opus → 模型 | `ANTHROPIC_DEFAULT_OPUS_MODEL` | `opus` 档映射到的模型 |
-| sonnet → 模型 | `ANTHROPIC_DEFAULT_SONNET_MODEL` | `sonnet` 档映射到的模型 |
-| haiku → 模型 | `ANTHROPIC_DEFAULT_HAIKU_MODEL` | `haiku` 档映射到的模型；**后台任务也用它** |
-| effort 思考档 | `CLAUDE_CODE_EFFORT_LEVEL` | 思考深度，见下 |
+---
 
-> ccx **刻意不设** `ANTHROPIC_MODEL`、也不碰 `settings.json` 的 `model`。你在会话里用
-> `/model opus\|sonnet\|haiku` 现场选档，映射表负责把它翻译成对应供应商的模型。
+## 设计哲学
 
-### 模型映射与 effort
+> ccx 的边界比功能更重要。
 
-**为什么第三方必须配模型映射？** 第三方端点只认自己的模型名（如 `deepseek-v4-pro`），而 Claude Code
-默认会叫 `claude-*`，不映射就报错。后台任务走 `haiku` 档，所以 `haiku → 模型` **也必须填**
-（否则表现为“主对话能用但时不时报错”）。
+Claude Code 已经有自己的配置系统、MCP 生态和会话状态。ccx 不想再造一个“上层控制台”，也不想把用户的配置收编进自己的数据库。它只站在 Claude Code 进程启动前的那一小步：把 7 个受管环境变量准备好，然后让 Claude Code 自己工作。
 
-**effort（思考深度）**：`low < medium < high < xhigh < max`，越高越聪明但越慢越费 token；`auto` = 模型
-默认；留空 = 不设。注意 **effort 是 Claude 模型特性，第三方是否生效取决于各家实现**。
+所以它的取舍是有意的：不写 Claude Code 配置文件，不接管 MCP，不做自动迁移，不做后台常驻管理。能用进程环境变量解决，就不碰全局文件；能让用户显式选择，就不替用户自动决定。少做一点，是为了把风险面压到足够小。
 
-各家参考配置（默认已预置）：
+欢迎 Issue / PR，但方向很明确：**让切换更稳、更清楚、更不打扰用户**，比堆更多管理能力更重要。任何会写 Claude Code 配置文件的改动都不会被接受。
 
-| 配置 | BASE_URL | OPUS / SONNET | HAIKU（含后台） | effort |
-|---|---|---|---|---|
-| 官方 | （留空＝登录态） | — | — | 留空 / `auto` |
-| DeepSeek | `https://api.deepseek.com/anthropic` | `deepseek-v4-pro` | `deepseek-v4-flash` | `max`（官方推荐） |
-| 智谱GLM | `https://open.bigmodel.cn/api/anthropic` | `GLM-4.7` | `glm-4.5-air` | 留空 |
-| 小米MiMo | `https://api.xiaomimimo.com/anthropic`（按量付费）<br>`https://token-plan-cn.xiaomimimo.com/anthropic`（TokenPlan） | `mimo-v2.5-pro` | `mimo-v2.5-pro` | 留空 |
+---
 
-> 模型名会随各家更新而变，请以各供应商官方接入文档为准。
+## 配置说明
 
-### 认证字段：AUTH_TOKEN vs API_KEY
+### 字段一览
 
-| 选项 | 实际请求头 | 谁用 |
+| 字段 | 对应环境变量 | 说明 |
 |---|---|---|
-| `ANTHROPIC_AUTH_TOKEN`（默认） | `Authorization: Bearer <key>` | 绝大多数第三方中转 |
-| `ANTHROPIC_API_KEY` | `x-api-key: <key>` | 官方 API，及少数只认这种头的中转 |
+| API 地址 | `ANTHROPIC_BASE_URL` | 第三方接入点；官方留空=登录态 |
+| 认证字段 | — | 密钥放 `AUTH_TOKEN`（默认）还是 `API_KEY`；**放错会 401** |
+| API 密钥 | `ANTHROPIC_AUTH_TOKEN` 或 `ANTHROPIC_API_KEY` | 对应认证字段的值 |
+| opus → 模型 | `ANTHROPIC_DEFAULT_OPUS_MODEL` | 三档模型映射；后台任务走 haiku 档，**必须填** |
+| sonnet → 模型 | `ANTHROPIC_DEFAULT_SONNET_MODEL` | |
+| haiku → 模型 | `ANTHROPIC_DEFAULT_HAIKU_MODEL` | |
+| effort 思考档 | `CLAUDE_CODE_EFFORT_LEVEL` | `low` ~ `max`；`auto`=模型默认；留空=不设。第三方不一定生效 |
 
-放错会 401。编辑时可在「认证字段」切换；切换配置时 ccx 会自动清掉另一个，避免残留冲突。
+> ccx **刻意不设** `ANTHROPIC_MODEL`。在会话里用 `/model opus|sonnet|haiku` 选档，映射表负责翻译成对应供应商的模型名。
 
-## 多账号与维护预设
+### 认证字段：AUTH_TOKEN vs API_KEY
 
-**多账号**：同一家有多个 key（个人 / 公司），直接建多份配置——选同一供应商建第二份时名称自动变
-`DeepSeek 2`，再用**备注**写明区别，列表显示成「供应商 — 备注」，一眼可辨。
+| 选项 | 实际请求头 | 谁用 |
+|---|---|---|
+| `AUTH_TOKEN`（默认） | `Authorization: Bearer <key>` | 绝大多数第三方中转 |
+| `API_KEY` | `x-api-key: <key>` | 官方 API，及少数中转 |
 
-**维护供应商预设**：`presets.json`（随工具发布）是供应商目录，新增配置时选「供应商」就来自这里。
-加一个供应商即多一个预设，无需改代码：
+### 预置配置
 
-```json
-[
-  {
-    "name": "DeepSeek",
-    "auth": "AUTH_TOKEN",
-    "effort": "max",
-    "urls": [ { "label": "Anthropic 兼容", "url": "https://api.deepseek.com/anthropic" } ],
-    "models": { "opus": "deepseek-v4-pro", "sonnet": "deepseek-v4-pro", "haiku": "deepseek-v4-flash" }
-  }
-]
-```
+| 配置 | BASE_URL | OPUS / SONNET | HAIKU（含后台任务） | effort |
+|---|---|---|---|---|
+| 官方 | 留空=登录态 | — | — | — |
+| DeepSeek | `https://api.deepseek.com/anthropic` | `deepseek-v4-pro` | `deepseek-v4-flash` | `max`（官方推荐） |
+| 智谱GLM | `https://open.bigmodel.cn/api/anthropic` | `GLM-4.7` | `glm-4.5-air` | — |
+| 小米MiMo | `https://api.xiaomimimo.com/anthropic` | `mimo-v2.5-pro` | `mimo-v2.5-pro` | — |
 
-- `urls` 可有**多个**（如 API 与 TokenPlan 不同地址），选该供应商时先挑一个。
-- `models` 是三档推荐映射，选供应商时自动填入，之后仍可手改。`auth` / `effort` 可选，一并带出。
-- 也可在 `~/.cc-mini/presets.json` 放一份自定义目录覆盖随工具发布的版本（优先级最高）。
+> 模型名随各家更新而变，以供应商官方接入文档为准。小米有按量付费和 TokenPlan 两个地址，选供应商时会让你挑。
 
-## 检查新版本
+### 进阶
 
-主菜单的「**更新检查**」开关默认**关闭**。切到「提醒」后，ccx 会在有新版本时于菜单顶部显示一行
-黄字提示，并给出升级命令（不会自动下载安装，你决定何时升）。
+- **多账号**：同一家建多份配置，名称自动追加「 2」「 3」…用**备注**区分，列表显示为「供应商 — 备注」。
+- **自定义供应商**：`presets.json` 是供应商目录，加一个 JSON 条目就多一个供应商，无需改代码。可在 `~/.cc-mini/presets.json` 放自定义版覆盖随工具发布的版本。
+- **第三方首次弹登录**：在 `~/.claude.json` 最外层加 `"hasCompletedOnboarding": true`（**只加这个键**，别覆盖整个文件——里面还有你的 MCP 配置）。
+- **更新检查**：主菜单可切「提醒」模式，新版本出现时菜单顶部黄字提示升级命令。每天最多查一次，不自动升级。
 
-- 不走 GitHub API，每天最多查一次，结果缓存在 `~/.cc-mini/update-check.json`；离线或失败都静默。
-- 检查在后台进行、不拖慢启动——新版本通常在**下次打开**时才提示。
-- 升级就是重新跑一次安装命令（原生版用[安装](#安装)里的一行命令，npm 版 `npm i -g @cc-x/cc-x@latest`）。
+---
 
-## 首次使用：跳过登录 / 引导
+## 数据与文件
 
-用第三方 API（token 鉴权）时，Claude Code **首次启动仍可能弹登录 / 引导**——因为它没记录“已完成引导”。
-一次性修复：在 `~/.claude.json`（Windows 为 `C:\Users\你的用户名\.claude.json`）的最外层 `{ }` 里
-**只加一个键**（其它内容原样保留）：
+- **配置（含明文密钥，勿外传）**：`~/.cc-mini/providers.json`（也存界面语言 `lang`、更新检查 `update`）
+- **供应商目录**：随工具发布的 `presets.json`；`~/.cc-mini/presets.json` 可覆盖
+- **「设为默认」写的是用户环境变量**（不是 Claude 配置文件）：
+  - Windows → 注册表 `HKCU\Environment` + 广播一次变更
+  - Unix → shell 启动文件 `# >>> xx >>>` … `# <<< xx <<<` 标记块（幂等重写，按 `$SHELL` 选文件）
+  - 语义一致：**只影响新终端**；切到「官方」会清除全部受管变量
+- **不修改任何 Claude Code 配置文件。**
 
-```json
-{
-  "hasCompletedOnboarding": true
-}
-```
+ccx 只动这 7 个「受管」环境变量，切换时清掉目标不用的：
+`ANTHROPIC_BASE_URL`、`ANTHROPIC_AUTH_TOKEN`、`ANTHROPIC_API_KEY`、`ANTHROPIC_DEFAULT_OPUS_MODEL`、`ANTHROPIC_DEFAULT_SONNET_MODEL`、`ANTHROPIC_DEFAULT_HAIKU_MODEL`、`CLAUDE_CODE_EFFORT_LEVEL`。
 
-> ⚠️ 这个文件还存着你的 MCP 等配置，**务必只“加键”、不要整体覆盖**。ccx 刻意不替你改它——它正是
-> 最不该被工具乱动的地方。
+> 💡 需要改 `settings.json`？直接用 Claude Code 的 `/update-config` 说需求（如"允许 npm 命令"），比让外部工具改可靠。
 
-## 数据与文件位置
+---
 
-- **配置（含明文密钥，勿外传）**：`~/.cc-mini/providers.json`（含界面语言 `lang`、更新检查 `update`）。
-- **供应商目录**：随工具发布的 `presets.json`，或 `~/.cc-mini/presets.json`（自定义覆盖）。
-- **更新检查缓存**：`~/.cc-mini/update-check.json`。
-- **「设为默认」写的是用户环境变量**（不是 Claude 配置文件）：
-  - **Windows** → 注册表 `HKCU\Environment` + 广播一次变更；
-  - **macOS / Linux** → shell 启动文件里的 `# >>> xx >>>` … `# <<< xx <<<` 标记块（幂等重写，按 `$SHELL` 选文件）。
-  - 二者语义一致：**只影响新开终端**；切到「官方」会清除全部受管变量。
-- **不修改任何 Claude 配置文件。**
+## FAQ
 
-ccx 只动这 7 个“受管”环境变量，其它一律不碰，切换时还会清掉目标没用到的那些：
-`ANTHROPIC_BASE_URL`、`ANTHROPIC_AUTH_TOKEN`、`ANTHROPIC_API_KEY`、`ANTHROPIC_DEFAULT_OPUS_MODEL`、
-`ANTHROPIC_DEFAULT_SONNET_MODEL`、`ANTHROPIC_DEFAULT_HAIKU_MODEL`、`CLAUDE_CODE_EFFORT_LEVEL`。
+**一个终端切了，影响另一个吗？** 不影响。「本次启用」进程级，「设为默认」只对新终端生效。
 
-> 💡 需要改 `settings.json` 时，直接用 Claude Code 官方的 `/update-config` 用自然语言说需求（如“允许运行
-> npm 命令”），比让外部工具乱改更可靠。
+**设为默认了，当前终端敲 `claude` 还是旧的？** 正常——当前终端是旧环境，新开即可。
 
-## 常见问题（FAQ）
+**报 `cannot be parsed as a URL`？** 某配置的 API 地址填了无效值，编辑改正或删除。
 
-**在一个终端切换，会影响另一个正在运行的终端吗？** 不会。「本次启用」是进程级；「设为默认」只对**新开**
-的进程生效，运行中的会话启动时已定型。
+**第三方 effort 没效果？** effort 是 Claude 模型特性，第三方不一定支持。DeepSeek 推荐 `max`，其余留空。
 
-**“设为默认”了，但当前终端敲 `claude` 还是旧的？** 正常——当前终端是旧环境，请**新开终端**。
+**密钥安全吗？** 明文存本机用户目录，受账户权限保护。别把 `providers.json` 提交到仓库。
 
-**出现 `... cannot be parsed as a URL`？** 某配置的 API 地址填成了无效值，进「编辑」改正或删除即可。
+**能指定安装目录吗？** 可以。Windows 安装脚本支持 `-InstallDir`；macOS / Linux 可用 `CCX_INSTALL_DIR` 或 `--install-dir`。只有少数用户需要改，默认安装最省心；如果改过目录，卸载时也传同一个目录。
 
-**第三方设了 effort 没反应？** effort 是 Claude 模型特性，第三方未必支持。DeepSeek 推荐 `max`，其余留空即可。
+**能手动下载二进制吗？** 可以，到 [GitHub Releases](https://github.com/becomeless/cc-x/releases/latest) 下载对应系统的 zip / tar.gz，解压后把 `xx` / `xx.exe` 放到 PATH 里的目录。普通用户建议用上面的安装命令：会自动选平台、做校验，并处理 PATH / 卸载。
 
-**密钥安全吗？** 明文存于本机用户目录、受账户权限保护。注意别把 `providers.json` 提交到仓库。
+---
 
 ## 卸载
 
-1. **先清环境变量**：在 `xx` 里执行「设为默认 → 官方」一次，清除全部受管变量。
-2. **卸载本体**：
+1. 先清环境变量：`xx` → 选「官方」→ 设为默认
+2. 卸载本体：
    - Windows 原生版：
      ```powershell
-     powershell -NoProfile -ExecutionPolicy Bypass -Command "$s = irm https://github.com/becomeless/cc-x/releases/latest/download/install.ps1; & ([scriptblock]::Create($s)) -Uninstall"
+     $s = irm https://github.com/becomeless/cc-x/releases/latest/download/install.ps1
+     & ([scriptblock]::Create($s)) -Uninstall
      ```
+     会删除安装文件，并自动清理对应的用户 PATH 条目。
    - macOS / Linux 原生版：
      ```bash
      curl -fsSL https://github.com/becomeless/cc-x/releases/latest/download/install.sh | sh -s -- --uninstall
      ```
-   - npm 版：`npm uninstall -g @cc-x/cc-x`。
-   - macOS / Linux 若用过「设为默认」，顺手删掉 shell 启动文件里的 `# >>> xx >>>` 标记块。
-3. 删除数据目录 `~/.cc-mini/`。
+   - npm：`npm uninstall -g @cc-x/cc-x`
+3. 删数据：`rm -rf ~/.cc-mini`
 
-## 设计原则与初心
-
-ccx 源于我用 cc-switch 时反复遇到的不顺——不是批评，cc-switch 很强大，我只是想走一条更轻的路。
-所以 ccx 只信奉一条：**越简单越好。** 只做“切 API”一件事；能不碰的就不碰（尤其**绝不写 Claude Code
-配置文件**）；每加一个功能前先问一句能不能不加。
-
-欢迎 Issue / PR——但**让它更简单的改动，比让它更强大的改动更受欢迎**；任何会写 Claude Code 配置文件
-的改动都不会被接受。
+---
 
 ## 许可
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cc-x/cc-x",
-  "version": "0.4.4",
+  "version": "0.4.6",
   "description": "Claude Code API 切换器（命令 xx）：在官方账号与第三方 Anthropic 兼容 API 间切换，纯环境变量、不碰 Claude Code 配置文件。",
   "keywords": [
     "claude",