claude-multi 0.5.7 → 0.6.0

package/CHANGELOG.md

@@ -5,19 +5,45 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.6.0] - 2026-05-29
+
+### Added
+- **`doctor fix` auto-installs pinned Claude binary**: when the compatible binary at `~/.claude-multi/bin` is missing or running an incompatible version, `doctor fix` now installs Claude Code v2.1.153 (the last version before 3rd-party API breakage) before fixing wrappers. Works from both CLI and TUI.
+- **Version verification on pinned binary**: `getPinnedBinaryVersion()` reads the installed version and triggers a reinstall if it's v2.1.154+.
+- **`COMPATIBLE_CLAUDE_VERSION` constant** (`src/version.ts`): single source of truth for the pinned version (`2.1.153`).
+- **`PINNED_CLAUDE_BIN` in `src/paths.ts`**: shared path constant (previously duplicated in `wrapper.ts` and `health.ts`).
+
+### Changed
+- **Global version banner**: now reads "Run 'claude-multi doctor fix' to install a compatible version" instead of the passive "wait for a fix" message.
+- **TUI "Fix wrappers" action**: installs the pinned binary first if missing, then fixes wrappers. Both the menu option and the `f` key in the health screen follow this flow.
+- **Wrapper scripts now use pinned binary by default**: `getClaudePath()` checks `~/.claude-multi/bin` before falling back to global `which claude`, so new instances automatically use the compatible version.
+
+### Fixed
+- **Tests**: integration tests updated for current version and help output.
+
+## [0.5.8] - 2026-05-28
+
+### Added
+- **Region selection for MiMo Token Plan** (`--region`): `mimo-token` provider now supports regional endpoints — China (`cn`), Singapore (`sgp`), Europe (`ams`). Users are prompted to pick a region after selecting `mimo-token` in all three entry points (CLI `--region` flag, interactive prompts, Ink TUI wizard). Defaults to `cn` for backward compatibility.
+- **API key prefix mapping** (`API_KEY_PREFIXES`): `mimo-token` shows `tp_...` placeholder in the API key input; all other providers show `sk-...`. Extensible map for future providers with non-standard key formats.
+
+### Changed
+- **`--provider` error message** (`src/cli.ts`): unknown provider error now dynamically lists all available providers instead of hardcoding three names.
+- **Region advisory**: both the interactive prompts and Ink TUI display a highlighted message reminding users to check their Xiaomi account console for the correct region.
+
 ## [0.5.7] - 2026-05-27
 
 ### Added
 - **Provider templates** (`src/templates.ts`): five new AI provider templates
-  - **Xiaomi MiMo** (`mimo`): MiMo-V2.5-Pro and MiMo-V2.5 via xiaomimimo.com — pay-per-token API
+  - **Xiaomi MiMo** (`mimo`): MiMo-V2.5-Pro and MiMo-V2.5 via xiaomimimo.com, pay-per-token API
   - **Xiaomi MiMo Token Plan** (`mimo-token`): MiMo-V2.5-Pro via xiaomimimo.com subscription; replace base URL with your regional endpoint (CN/SG/EU) from the subscription console
-  - **Moonshot Kimi** (`kimi`): Kimi K2.6 (opus) and Kimi K2.5 (sonnet/haiku) via moonshot.ai — pay-per-token
-  - **Alibaba Qwen** (`qwen`): Qwen3-Coder-Next/Plus/Flash via Alibaba DashScope — pay-per-token API
+  - **Moonshot Kimi** (`kimi`): Kimi K2.6 (opus) and Kimi K2.5 (sonnet/haiku) via moonshot.ai, pay-per-token
+  - **Alibaba Qwen** (`qwen`): Qwen3-Coder-Next/Plus/Flash via Alibaba DashScope, pay-per-token API
   - **Alibaba Qwen Coding Plan** (`qwen-coding`): Qwen3-Coder-Next/Plus/Flash via DashScope Coding Plan subscription
 
 ### Changed
 - **GLM template** (`glm`): display name updated to "GLM Coding Plan"; description now clarifies the Anthropic endpoint is coding-plan-only (standard Z.ai pay-per-token API has no Anthropic-compatible URL)
-- **Kimi template** (`kimi`): sonnet/haiku tiers use `kimi-k2.5` instead of `kimi-k2.6` — same family, ~37% cheaper; legacy K2 series EOL'd May 25 2026
+- **Kimi template** (`kimi`): sonnet/haiku tiers use `kimi-k2.5` instead of `kimi-k2.6`, same family, ~37% cheaper; legacy K2 series EOL'd May 25 2026
 
 ## [0.5.6] - 2026-05-23
 
@@ -27,7 +53,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Changed
 - **Runtime-agnostic launcher** (`bin/claude-multi.js`): polyglot bin entry is simultaneously valid POSIX sh and ESM JavaScript
   - On Linux/macOS: shell shebang detects bun/node/deno and execs the correct runtime
-  - On Windows + bun global install: bun's `.exe` shim reads the `.js` extension and runs directly as ESM — no `/bin/sh` lookup required
+  - On Windows + bun global install: bun's `.exe` shim reads the `.js` extension and runs directly as ESM, no `/bin/sh` lookup required
   - On Windows + npm install: npm's `.cmd` shim calls `node` on the `.js` file
   - Shebang changed to `#!/usr/bin/env bun` so bun's Windows shim can resolve itself in `PATH`
 
@@ -44,10 +70,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 - **Cross-runtime support**: all package-manager operations (`upgradeClaudeMulti`, `getCurrentVersion`, `updateClaudeCode`) now use the detected package manager instead of hard-coding bun commands
-- `getLatestVersion()` replaced `bun pm npm view` with a direct `fetch()` to the npm registry — works in any runtime
+- `getLatestVersion()` replaced `bun pm npm view` with a direct `fetch()` to the npm registry, works in any runtime
 - `getDefaultBinaryPath()` selects the correct global bin directory for the active package manager on Windows (was always `%LOCALAPPDATA%\bun\bin`)
 - Generated wrapper shebang changed from `#!/usr/bin/env bun` to `#!/usr/bin/env node`
-- Default action (no subcommand) always launches the Ink TUI and awaits `waitUntilExit()` — the `CLAUDE_MULTI_INK=false` prompts fallback is removed
+- Default action (no subcommand) always launches the Ink TUI and awaits `waitUntilExit()`, the `CLAUDE_MULTI_INK=false` prompts fallback is removed
 - Update check is now **opt-in**: set `CLAUDE_MULTI_UPDATE_CHECK=true` to enable; it no longer runs on every invocation
 - Removed `interactive` / `i` command alias (default action covers this)
 
@@ -117,11 +143,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - Verify MCP configuration
   - Copy between instances
 - **CLI Plugin Commands**: 5 new `plugins` sub-commands
-  - `plugins install <instance> <ids...>` — install plugins with collision detection
-  - `plugins remove <instance> <ids...>` — remove plugins with symlink guard
-  - `plugins list-defaults` — list all 50 default plugins with category/MCP badges
-  - `plugins list-installed [instance]` — list installed plugins per instance
-  - `plugins check-collisions <instance> <ids...>` — detect MCP name conflicts
+  - `plugins install <instance> <ids...>`, install plugins with collision detection
+  - `plugins remove <instance> <ids...>`, remove plugins with symlink guard
+  - `plugins list-defaults`, list all 50 default plugins with category/MCP badges
+  - `plugins list-installed [instance]`, list installed plugins per instance
+  - `plugins check-collisions <instance> <ids...>`, detect MCP name conflicts
 - **Provider Templates**: DeepSeek provider template added
 - **Instance State**: `initializeInstanceState()` creates `.claude.json` with `hasCompletedOnboarding: true`
 - **Provider Env**: `mergeProviderEnv()` integrates provider template env vars into instance settings
@@ -131,7 +157,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `copyAllFromDefault()` restored `autoSync` parameter for symlink-based plugin sync
 - `syncPluginsAndSkills()` creates actual symlinks instead of copying files
 - Broken symlink detection uses `lstatSync` (works when `existsSync` returns false)
-- `~/.claude` is strictly read-only — never modified by any operation
+- `~/.claude` is strictly read-only, never modified by any operation
 - Atomic file writes for both config.json and settings.json (temp-file-rename pattern)
 - Lazy path resolution in migration.ts and health.ts for testability
 
@@ -139,7 +165,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `syncPluginsAndSkills` was doing recursive copy instead of creating symlinks
 - `copyAllFromDefault` `autoSync` parameter was removed, breaking symlink-based sync
 - Broken symlinks not cleaned before creating new ones (used `lstatSync` instead of `existsSync`)
-- `isClaudeCodeRunning()` blocked tests — skips in `NODE_ENV=test`
+- `isClaudeCodeRunning()` blocked tests, skips in `NODE_ENV=test`
 - `writeFileSync` not imported in config.ts
 - `McpSourceDetails` prop name mismatch in ManageMcp
 - `renameSync` dynamic import in `saveConfigAtomic` replaced with top-level import