Clother

Clother
  One CLI to switch between Claude Code providers instantly.

Why Clother?

Switching Claude Code providers usually means changing env vars, endpoints, models, and launcher scripts by hand.
Clother gives you one install and one command pattern across Claude, Z.AI, Kimi, Alibaba, OpenRouter, local backends, China endpoints, and many other Anthropic-compatible providers.

Table of Contents

- Installation
- Core Usage
  - Benchmarking
- Provider Reference
- Troubleshooting
- VS Code Integration
- Platform Support
- Under the Hood
- Contributors
- Star History
- License

Installation

Homebrew (macOS recommended)

All clother-* provider launchers are installed directly into $(brew --prefix)/bin by the formula — no extra setup needed. brew upgrade clother keeps everything up to date.

Update:

curl (macOS / Linux)

Update:

This installs:
- clother
- clother-* provider launchers
- resume compatibility for claude --resume ...

Install Options

By default, Clother installs launchers to:
- the same directory as your existing claude binary, when claude is already on PATH
- otherwise macOS: ~/bin
- otherwise Linux: ~/.local/bin (XDG standard)

If the chosen bin directory is not on PATH, clother install prints a warning with the exact directory to add.

You can override this with --bin-dir or the CLOTHER_BIN environment variable:

Clother keeps claude --resume ... working with Clother features after install.

Core Usage

Commands

Update

Routes to brew upgrade clother under Homebrew, or downloads the latest release for curl installs. Also refreshes provider symlinks.

Downloads go over https only, never follow a redirect off GitHub, and are checked against the release's checksums.txt before anything is replaced. If the update cannot be downloaded or verified, the…