claude-multi 0.12.0 → 0.13.0

package/CHANGELOG.md

@@ -5,6 +5,25 @@ 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.13.0] - 2026-10-31
+
+### Changed
+- **Provider templates refreshed for the October 2026 model lineups.** GLM now follows Z.ai's official Claude Code mapping: `glm-5.3[1m]` for opus and sonnet, `glm-5.3-flash[1m]` for haiku. GLM-5-Turbo is no longer a Coding Plan tier. MiniMax moves to `MiniMax-M3.1-Flash[1m]` in every slot. DeepSeek moves to `deepseek-flash[1m]` for opus, sonnet, and primary, with `deepseek-flash` for haiku and subagents. Kimi uses standard `kimi-k3.1-pro[1m]` in every slot, with Highspeed available as an optional faster tier. MiMo stays on V2.6 Pro and Flash.
+- **Qwen templates updated.** Pay-as-you-go uses `qwen3.8-max`, `qwen3.7-plus`, and `qwen3.8-flash`. The Coding Plan uses `qwen3.7-plus` in every slot because Qwen3.8 is not included in that plan. The retired `qwen3-coder-next` and `qwen3-coder-plus` IDs are gone.
+- **Output and context variables corrected.** Templates now use `CLAUDE_CODE_MAX_OUTPUT_TOKENS` instead of the inert `MAX_OUTPUT_TOKENS`, set `CLAUDE_CODE_MAX_CONTEXT_TOKENS` where needed, and use `CLAUDE_CODE_EFFORT_LEVEL` instead of undocumented effort variables. Deprecated `ANTHROPIC_SMALL_FAST_MODEL` entries are removed during sync.
+- Existing instances pick up the new mappings through the template drift check. Run `claude-multi doctor check` to see the change, then `claude-multi doctor fix` to apply it. API keys and user-tuned values are preserved.
+- Provider pages, docs, FAQ, and the environment-variable reference now match the shipped templates.
+- **Node.js 22 or newer is required.** Ink 7 does not support Node 18 or 20. Bun 1+ remains supported, and npm and pnpm work on Node 22+. The advertised Deno install path was removed because the package launcher is a POSIX shell script and `deno install -g npm:claude-multi` cannot execute it.
+- The npm package no longer installs the Astro site dependencies. They moved to `devDependencies`, so a global install pulls only the CLI bundle.
+- Added a `prepack` build and a test gate to the publish workflow, so a manual publish cannot ship an untested or unbuilt tarball.
+
+### Fixed
+- `claude-multi add --config <dir>` now uses the supplied directory. It previously joined the path under `~/.claude-` and created an unintended nested directory.
+
+### Blog
+- Blog post: [A Claude Code MCP workflow that actually runs](https://claude-multi.hmziq.xyz/blog/claude-code-mcp-workflow-automation/)
+- Blog post: [A reproducible LLM routing setup for Claude Code](https://claude-multi.hmziq.xyz/blog/llm-cost-optimization-routing/)
+
 ## [0.12.0] - 2026-08-26
 
 ### Changed
@@ -64,7 +83,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - `getSyncMode()` resolves the effective mode from the new `syncMode` field, falling back to the deprecated `autoSync` boolean for backward compatibility.
   - `canConvertSyncMode()` and `availableSyncModeConversions()` in `constants.ts` enforce downgrade-only rule.
   - `copyAllFromDefault()` now accepts a `SyncMode` parameter instead of a boolean.
-  - `detectBrokenSymlinks()` now detects broken individual symlinks inside real directories (half-manual mode), not just broken directory-level symlinks.
+  - `detectBrokenSymlinks()` now detects broken individual symlinks inside real directories (half-manual mode), in addition to broken directory-level symlinks.
   - TUI `ToggleAutoSync` screen rewritten as `Sync Mode` screen with color-coded mode labels and available-downgrade display.
   - Instance info screen (`ShowInstanceInfo`) shows sync mode with color-coded labels instead of binary on/off.
   - `plugin install/remove` commands blocked when instance is in half-manual mode (individually symlinked plugins cannot be individually managed).
@@ -127,9 +146,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 - **Instance details actions**: The instance details screen now has action buttons. Press Enter on any instance to access: Update settings template, Update alias wrapper, and Override alias to standard. Each action shows a live mismatch indicator (✓ up to date, ⚠ mismatch detected, ✗ wrapper missing).
-- `syncProviderTemplateForInstance()` in `config.ts` — on-demand provider template sync for a single instance. Re-applies the latest template env vars while preserving API keys and user-customized tunable vars.
-- `detectTemplateMismatch()` and `detectWrapperMismatch()` in `instance-diagnostics.ts` — compare an instance's current settings/wrapper against the expected provider template.
-- `TUNABLE_ENV_VARS` shared constant in `constants/env.ts` — single source of truth for env vars that are preserved during template sync and excluded from staleness checks.
+- `syncProviderTemplateForInstance()` in `config.ts`: on-demand provider template sync for a single instance. Re-applies the latest template env vars while preserving API keys and user-customized tunable vars.
+- `detectTemplateMismatch()` and `detectWrapperMismatch()` in `instance-diagnostics.ts`: compare an instance's current settings/wrapper against the expected provider template.
+- `TUNABLE_ENV_VARS` shared constant in `constants/env.ts`: single source of truth for env vars that are preserved during template sync and excluded from staleness checks.
 
 ### Changed
 - **Health screen rewrite**: Replaced static `IssueCard` list with a Select-based issue picker. Issues can now be selected, viewed in detail, and dismissed. Press Enter to view an issue, `d` to dismiss, `D` to dismiss all.
@@ -165,7 +184,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Instance migration tests: fast-path skip on current-version instances, mixed instances (some current, some old), `.claude.json` updates when the wrapper file is missing, and a verification that regenerated wrappers contain the global claude path.
 
 ### Fixed
-- Health test compared `fixWrapperVersions` output against `generateWrapperScript()` (resolves via env override) instead of `buildWrapperScript(inst, PINNED_CLAUDE_BIN)` (what the function actually uses). Would break if `CLAUDE_MULTI_CLAUDE_PATH` was set.
+- Health test compared `fixWrapperVersions` output against `generateWrapperScript()` (resolves via env override) instead of `buildWrapperScript(inst, PINNED_CLAUDE_BIN)` (what the function uses). Would break if `CLAUDE_MULTI_CLAUDE_PATH` was set.
 
 ### Added
 - Instances track the claude-multi version they were created with (`createdWithVersion`). New instances get the current version. Instances created before this field existed get `0.5` and show "before version tracking" in the UI.
@@ -177,15 +196,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `instanceMigrationVersion` in config now stores the actual package version rather than a separate numbering scheme.
 - The legacy sentinel (`"0.5"`) is defined once as `LEGACY_INSTANCE_VERSION` and imported everywhere, instead of being hardcoded in multiple files.
 - Wrapper script template exists in a single place (`buildWrapperScript` in `wrapper.ts`). Migration and health check both delegate to it instead of duplicating the template string.
-- Instance migration only rewrites wrappers when the file content actually differs (version check + content diff), instead of unconditionally regenerating every wrapper.
+- Instance migration only rewrites wrappers when the file content differs (version check + content diff), instead of unconditionally regenerating every wrapper.
 - `fixWrapperVersions` uses the canonical template targeting the pinned binary explicitly, with a content-diff check to avoid unnecessary writes.
 
 ### Fixed
 - Removed broken `compareVersions` references from `version.test.ts`.
-- `resolveClaudePath()` in `migration.ts` used `await` in a non-async function (TypeScript error). Removed — replaced by `generateWrapperScriptSafe` from `wrapper.ts`.
+- `resolveClaudePath()` in `migration.ts` used `await` in a non-async function (TypeScript error). Removed, replaced by `generateWrapperScriptSafe` from `wrapper.ts`.
 - Unused imports (`COMPATIBLE_CLAUDE_VERSION`, `installPinnedClaude`, `getPinnedBinaryVersion`, `isThirdPartyApiBroken`, `PINNED_CLAUDE_BIN`) removed from `migration.ts`.
 - `config.ts` `loadConfig` backfill loop now handles `noUncheckedIndexedAccess` correctly (pre-existing TypeScript error).
-- `createBackup` changed from async to sync (had no `await` expressions — pre-existing lint warning).
+- `createBackup` changed from async to sync (had no `await` expressions, pre-existing lint warning).
 - Array `.sort()` / `.reverse()` calls in `migration.ts` and `config.ts` changed to `.toSorted()` / `.toReversed()` (pre-existing lint warnings).
 - Duplicate `existsSync` import in `test/wrapper.test.ts` merged into single import.
 
@@ -194,15 +213,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Changed
 - Pinned Claude version updated from `2.1.153` to `2.1.156`. `isThirdPartyApiBroken()` now covers v2.1.154 through v2.1.155.
 - Auto-updates re-enabled. `PROVIDER_COMMON_ENV` no longer injects `DISABLE_AUTOUPDATER`/`DISABLE_UPDATES`. `autoUpdates` set to `true` in instance state.
-- `doctor fix` now reinstalls the pinned binary when its version differs from `COMPATIBLE_CLAUDE_VERSION`, not just when broken. Covers the upgrade path from the old v2.1.153 pin.
+- `doctor fix` now reinstalls the pinned binary when its version differs from `COMPATIBLE_CLAUDE_VERSION` or when broken. Covers the upgrade path from the old v2.1.153 pin.
 - Unknown CLI subcommands exit with an error instead of falling through to the Ink TUI.
 - All version pinning and compatibility code tagged with `[SAFE PARK]` comments for easy discovery and reactivation.
 
 ## [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.156 (the version that fixed the 3rd-party API breakage from v2.1.154–v2.1.155) 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–v2.1.155.
+- **`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.156 (the version that fixed the 3rd-party API breakage from v2.1.154-v2.1.155) 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-v2.1.155.
 - **`COMPATIBLE_CLAUDE_VERSION` constant** (`src/version.ts`): single source of truth for the pinned version (`2.1.156`).
 - **`PINNED_CLAUDE_BIN` in `src/paths.ts`**: shared path constant (previously duplicated in `wrapper.ts` and `health.ts`).
 
@@ -217,7 +236,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [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.
+- **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
@@ -507,6 +526,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Support for custom config and binary paths
 - Command-line interface built with Commander.js
 
+[0.13.0]: https://github.com/hmziqrs/claude-multi/compare/v0.12.0...v0.13.0
 [0.12.0]: https://github.com/hmziqrs/claude-multi/compare/v0.11.1...v0.12.0
 [0.11.0]: https://github.com/hmziqrs/claude-multi/compare/v0.10.0...v0.11.0
 [0.8.2]: https://github.com/hmziqrs/claude-multi/compare/v0.8.1...v0.8.2

package/README.md

@@ -23,201 +23,53 @@ https://github.com/user-attachments/assets/790edd9c-6ee2-425a-952c-397ad047d653
 
 ---
 
-## Why?
+## Why claude-multi
 
 Claude Code is great. Switching between providers and model setups is not.
 
-If you want to try GLM today and DeepSeek tomorrow, you usually end up editing `settings.json` by hand, juggling env vars, swapping keys, or maintaining a bunch of shell aliases nobody asked for.
+If you want to try GLM today and DeepSeek tomorrow, you usually end up editing `settings.json` by hand, juggling env vars, swapping keys, or maintaining a bunch of shell aliases.
 
-The other option is to use each provider's own CLI tool. That sounds clean until you realize every tool has its own workflow, its own flags, its own way of doing things. Learning a new harness for every model gets old fast.
+The other option is each provider's own CLI tool. Every tool has its own workflow, its own flags, its own way of doing things. Learning a new harness for every model gets old fast.
 
-So I went the other way: keep one harness I already like, and put the providers behind it. That's claude-multi. One workflow, many providers.
-
-And because it's still Claude Code under the hood, you keep everything you already use. `/loop`, `/goal`, skills, MCP servers, plugins, all of it. Switching providers does not mean rebuilding your setup from scratch.
+So I went the other way: keep one harness I already like, and put the providers behind it. It's still Claude Code under the hood, so `/loop`, `/goal`, skills, MCP servers, and plugins all keep working.
 
 ```bash
-claude          # your normal Claude Code setup
-claude-glm      # Claude Code using GLM / Z.ai config
-claude-deepseek # Claude Code using DeepSeek config
-claude-minimax  # Claude Code using MiniMax config
-```
-
-Each instance is isolated. All of them run the normal, unmodified Claude Code binary.
-
----
-
-## Features
-
-* Multiple Claude Code instances, one `claude-<name>` command each.
-* Provider templates for GLM/Z.ai, MiniMax, DeepSeek, Xiaomi MiMo, Moonshot Kimi, and Qwen.
-* Isolated config directories. Every instance gets its own `~/.claude-<name>/`.
-* A full terminal UI that covers adding, listing, plugins, MCP, and sync.
-* Plugin management per instance: enable, disable, install, copy, remove.
-* MCP management: list and copy server configs between instances.
-* Optional auto-sync that symlinks plugins and skills from your default `~/.claude`.
-* `doctor` reports provider template updates for existing instances and can apply them after making a backup.
-* No fork. It wraps your existing `claude` binary instead of patching it.
-
----
-
-## Requirements
-
-* Node.js 18+ or Bun 1+
-* Claude Code installed globally
-
-If you don't have Claude Code yet:
-
-```bash
-npm install -g @anthropic-ai/claude-code
+claude
+claude-glm
+claude-deepseek
+claude-minimax
 ```
 
 ---
 
 ## Install
 
-Bun:
-
-```bash
-bun add -g claude-multi
-```
-
-npm:
-
-```bash
-npm install -g claude-multi
-```
-
-pnpm:
-
-```bash
-pnpm add -g claude-multi
-```
+Requires Node.js 22+ or Bun 1+, and Claude Code installed globally (`npm install -g @anthropic-ai/claude-code`).
 
-Deno:
+claude-multi installs globally with bun, npm, or pnpm.
 
 ```bash
-deno install -g -A -n claude-multi npm:claude-multi
+bun add -g claude-multi
+# or: npm install -g claude-multi
+# or: pnpm add -g claude-multi
 ```
 
 ---
 
-## Getting started
-
-Launch the TUI:
+## Quick start
 
 ```bash
 claude-multi
 ```
 
-That's the only command you need to remember. Everything else lives inside the terminal UI.
-
-### The main menu
-
-When the TUI opens, you get something like this:
-
-```
-🤖 Claude Multi  -  Interactive Mode
-
-  ➕ Add new instance
-  📋 List all instances
-  ℹ️  Instance details
-  🔌 Manage plugins
-  🔄 Toggle auto-sync
-  🔗 Re-sync symlinks
-  🗑️  Remove instance
-  ⚙️  MCP servers
-  🚪 Exit
-```
-
-Arrow keys to move. `Enter` to pick. `ESC` to go back. `q` to quit.
-
-### Setting up your first instance
-
-Pick **➕ Add new instance**. The wizard has eight steps.
-
-**1. Instance name**
-
-Pick something short like `glm`, `deepseek`, or `work`. Letters, numbers, hyphens, and underscores only. Whatever you type here becomes your command, so `glm` gives you `claude-glm`.
-
-**2. Provider template**
-
-Pick one:
-
-* `glm` for GLM / Z.ai
-* `minimax` for MiniMax
-* `deepseek` for DeepSeek
-* `None / Custom` if you want to set things up by hand later
-
-**3. API key** *(only if you picked a provider)*
-
-Paste your key. It's masked while you type and gets written into the instance's `settings.json`.
-
-**4. Confirm paths**
-
-The wizard shows where things will go:
-
-* Config: `~/.claude-<name>/`
-* Binary: `~/.local/bin/claude-<name>`
-
-Hit `y` to accept. The defaults are fine for almost everyone.
-
-**5. Copy options**
-
-If you already have a `~/.claude` setup, you can carry pieces of it into the new instance:
+That's the only command to remember. Everything else happens in the terminal UI: pick Add new instance, and the wizard walks you through a name, a provider template, and an API key. When it finishes you have a `claude-<name>` command running real Claude Code against an isolated `~/.claude-<name>/` config.
 
-* **Nothing.** Start fresh, inherit nothing.
-* **Only `settings.json`.** Copy just the base settings file.
-* **Select plugins.** Cherry-pick plugins from your default setup.
-* **All files.** Settings, `CLAUDE.md`, plugins, skills, the whole thing.
+Two things worth knowing:
 
-**6. Select plugins** *(only if you picked "Select plugins")*
+- If the menu shows a `!` health hint, press `!` to see what's wrong and fix it.
+- After upgrading claude-multi, run `claude-multi doctor check` to apply provider template updates. It backs up `settings.json` first and keeps any values you changed yourself.
 
-A multi-select list of every plugin in your default `~/.claude`. `space` toggles. `enter` confirms.
-
-**7. Auto-sync** *(only if you picked "All files")*
-
-This asks whether to symlink `plugins/` and `skills/` back to `~/.claude`. Say `y` if you want to install a plugin once and have it show up in every instance. Say `n` if you want this instance to have its own independent copies.
-
-**8. Done**
-
-The wizard prints the new instance and its paths:
-
-```
-✓ Instance 'glm' created successfully!
-  ├─ Binary: /Users/you/.local/bin/claude-glm
-  └─ Config: /Users/you/.claude-glm
-```
-
-Run it:
-
-```bash
-claude-glm
-```
-
-That's a full Claude Code session on the provider you picked, with its own isolated config. Same `claude` you already know, just pointed at a different brain.
-
-### Other TUI flows
-
-* **📋 List all instances.** Every instance with its provider, paths, and sync status.
-* **ℹ️ Instance details.** Pick one to inspect its full config.
-* **🔌 Manage plugins.** Pick an instance, then enable, disable, install, copy, or remove plugins for it.
-* **🔄 Toggle auto-sync.** Flip symlink syncing on or off for a chosen instance.
-* **🔗 Re-sync symlinks.** Rebuild broken plugin or skill symlinks after you've moved `~/.claude` around.
-* **🗑️ Remove instance.** Delete an instance, its wrapper, and optionally its config dir.
-* **⚙️ MCP servers.** View MCP configs and copy them between instances.
-
-If the menu shows a `!` health hint, press `!` to see what's wrong and fix it.
-
-### Update an existing provider instance
-
-Provider templates change as providers ship new models or revise their settings. After updating claude-multi, check existing instances:
-
-```bash
-claude-multi doctor check
-claude-multi doctor fix
-```
-
-The TUI also shows `Run instance migrations` when an update is available. The sync updates model names and other template settings, while keeping API keys and values you changed yourself. It creates a backup before writing `settings.json`.
+Full documentation: **https://claude-multi.hmziq.xyz**
 
 ---
 
@@ -230,17 +82,17 @@ The TUI also shows `Run instance migrations` when an update is available. The sy
 | DeepSeek | `api.deepseek.com` | `deepseek` |
 | Xiaomi MiMo | `api.xiaomimimo.com` | `mimo` |
 | Xiaomi MiMo (Token Plan) | `token-plan-cn.xiaomimimo.com` | `mimo-token` |
-| Moonshot Kimi | `api.moonshot.ai` | `kimi-k2.7-code, kimi-k2.6, kimi-k2.5` |
+| Moonshot Kimi | `api.moonshot.ai` | `kimi` |
 | Alibaba Qwen | `dashscope-intl.aliyuncs.com` | `qwen` |
 | Alibaba Qwen Coding Plan | `coding-intl.dashscope.aliyuncs.com` | `qwen-coding` |
 
-The templates write `ANTHROPIC_BASE_URL`, `ANTHROPIC_MODEL`, and related env vars into `~/.claude-<name>/settings.json`. If you edit a setting, provider sync keeps your custom tunables but restores model slots to the current template.
+Templates write `ANTHROPIC_BASE_URL`, `ANTHROPIC_MODEL`, and related env vars into `~/.claude-<name>/settings.json`. Provider sync keeps values you changed yourself and restores model slots to the current template.
 
 ---
 
 ## How it works
 
-Every instance gets a config dir at `~/.claude-<name>/` and a wrapper script at `~/.local/bin/claude-<name>`. The wrapper sets `CLAUDE_CONFIG_DIR` and then runs the unmodified `claude` binary. No fork, no patch.
+Each instance is a config dir at `~/.claude-<name>/` plus a wrapper script at `~/.local/bin/claude-<name>` that sets `CLAUDE_CONFIG_DIR` and runs the unmodified `claude` binary. No fork, no patch. The instance registry lives in `~/.claude-multi/config.json`.
 
 ```js
 #!/usr/bin/env bun
@@ -248,79 +100,24 @@ process.env.CLAUDE_CONFIG_DIR = "/Users/you/.claude-glm"
 spawn("claude", process.argv.slice(2), { stdio: "inherit", env: process.env })
 ```
 
-Instance metadata sits in `~/.claude-multi/config.json`. When auto-sync is on, `plugins/` and `skills/` are symlinks back to `~/.claude/`, so installing a plugin once makes it show up everywhere.
-
----
-
-## File locations
-
-| Path | Purpose |
-|---|---|
-| `~/.claude-multi/config.json` | claude-multi instance registry |
-| `~/.claude-<name>/` | config directory for one instance |
-| `~/.local/bin/claude-<name>` | generated wrapper command on Linux/macOS |
-| `~/.claude/` | your default Claude Code config. Treated as the source for copy and sync operations. |
-
----
-
-## Auto-sync vs manual mode
-
-With auto-sync on, `plugins/` and `skills/` are symlinks pointing at your default `~/.claude/`. Install a plugin once, and every instance that opted in picks it up.
-
-Use manual mode when you want an instance that's fully independent. Just say `n` at the auto-sync step in the wizard. You can also flip this later from the main menu under **🔄 Toggle auto-sync**.
+Auto-sync symlinks `plugins/` and `skills/` back to `~/.claude/`, so a plugin you install once shows up in every instance that opted in. Skip it (or toggle it later in the menu) if you want an instance fully independent.
 
 ---
 
 ## Troubleshooting
 
-### `claude-<name>` command not found
-
-Your global binary directory probably isn't on `PATH`.
-
-For zsh on Linux/macOS:
-
-```bash
-echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc
-source ~/.zshrc
-```
-
-For Bash:
+**`claude-<name>` command not found.** Your `~/.local/bin` probably isn't on `PATH`:
 
 ```bash
-echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
-source ~/.bashrc
+echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc
 ```
 
-### Broken plugin or skill symlinks
-
-Open the TUI and pick **🔗 Re-sync symlinks**. Choose the broken instance (or all of them) and it rebuilds the links.
-
-### Health warnings in the menu
-
-If the main menu shows a yellow or red banner, hit `!` to open the health screen. It lists what's wrong (missing binary, broken symlinks, stale registry entries, that kind of thing) and offers fixes for each one.
-
-### Force the simpler prompts UI
-
-If the Ink TUI doesn't render right on your terminal:
-
-```bash
-CLAUDE_MULTI_INK=false claude-multi
-```
-
-You get a basic prompt-based UI with the same flows.
-
----
-
-## Roadmap ideas
+**Broken plugin or skill symlinks.** Pick Re-sync symlinks in the TUI.
 
-* More provider templates
-* Better docs for provider-specific models
-* Import and export instance profiles
-* Safer API key management
-* Preset workflows for coding, planning, review, and cheap exploration models
+**The Ink TUI renders wrong.** `CLAUDE_MULTI_INK=false claude-multi` gets you the plain prompts UI with the same flows.
 
 ---
 
 ## License
 
-MIT. See [LICENSE](./LICENSE) for the full text. Copyright (c) 2026 hmziqrs.
+MIT. See [LICENSE](./LICENSE). Copyright (c) 2026 hmziqrs.

package/bin/claude-multi.cmd

@@ -1,7 +1,6 @@
 @echo off
 setlocal
-:: Resolve package root (bin\ -> ..\)
-set "_cli=%~dp0..\dist\cli.js"
+set "_cli=%~dp0..\build\cli.js"
 
 where bun >nul 2>&1
 if not errorlevel 1 (
@@ -15,12 +14,6 @@ if not errorlevel 1 (
   exit /b %errorlevel%
 )
 
-where deno >nul 2>&1
-if not errorlevel 1 (
-  deno run -A "%_cli%" %*
-  exit /b %errorlevel%
-)
-
-echo claude-multi: no JavaScript runtime found (install bun, node, or deno) 1>&2
+echo claude-multi: no JavaScript runtime found (install bun or node 22+) 1>&2
 exit /b 1
 endlocal

package/bin/claude-multi.js

@@ -14,9 +14,7 @@ if command -v bun >/dev/null 2>&1; then
   exec bun "$CLI" "$@"
 elif command -v node >/dev/null 2>&1; then
   exec node "$CLI" "$@"
-elif command -v deno >/dev/null 2>&1; then
-  exec deno run -A "$CLI" "$@"
 else
-  echo "claude-multi: no JavaScript runtime found (install bun, node, or deno)" >&2
+  echo "claude-multi: no JavaScript runtime found (install bun or node 22+)" >&2
   exit 1
 fi