multi-claude-cli 0.15.0__tar.gz → 0.16.0__tar.gz

{multi_claude_cli-0.15.0/src/multi_claude_cli.egg-info → multi_claude_cli-0.16.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: multi-claude-cli
-Version: 0.15.0
+Version: 0.16.0
 Summary: Run several Claude Code accounts side by side: separate CLAUDE_CONFIG_DIR directories, launchers, proxies, environment variables and arguments.
 License: MIT
 Project-URL: Homepage, https://github.com/jakoes-wu/multi-claude
@@ -39,7 +39,7 @@ Dynamic: license-file
 
 Use several [Claude Code](https://code.claude.com/docs) accounts on one machine, at the same time. Each account keeps its own login, settings and history and, if you like, its own proxy. No more logging out and in again.
 
-It never copies or exports your login and never edits your shell startup files. Only `list` reads an account's access token and goes online, to ask Anthropic for the current plan (renewing the token first if it has expired); `list --offline` skips all of that.
+It never copies or exports your login and never edits your shell startup files. Only `list` reads an account's access token and goes online, to ask Anthropic for the current plan (renewing the token first if it has expired); `list --offline` skips all of that. `doctor --network` also goes online, but only when you ask for it and without any login.
 
 ```sh
 claude-work        # Claude Code with your work account
@@ -67,7 +67,7 @@ The launchers are plain shell scripts. They keep working even if you uninstall m
 ## Features
 
 - **Your login stays yours** — logins are never copied or exported. One command touches them: `list` takes each account's access token (from the keychain, or `.credentials.json` on Linux) to ask Anthropic which plan the account is on, and when that token has expired it renews it the way Claude Code does and saves the new one in the same place. Tokens stay in memory and go only to Anthropic (`api.anthropic.com`, and `platform.claude.com` for a renewal), through that account's proxy. `list --no-refresh` never writes, `list --offline` reads nothing. Every other command only checks whether a login exists. `migrate-default` and `restore` move whole account directories, and on Linux the credentials file moves with its directory without being opened.
-- **Only `list` goes online** — its plan lookup (one request per account, plus one to renew an expired token) is the only connection multi-claude makes: no telemetry, no usage reporting, no update checks. `list --offline` makes none. Only the installer, pipx or Homebrew download the package.
+- **Only `list` and `doctor --network` go online** — the plan lookup of `list` (one request per account, plus one to renew an expired token) and the connection check of `doctor --network` (one `HEAD /` without credentials to `api.anthropic.com` and `platform.claude.com` per proxy, repeated once if it fails) are the only connections multi-claude makes: no telemetry, no usage reporting, no update checks. `list --offline` makes none. Only the installer, pipx or Homebrew download the package.
 - **Leaves your shell alone** — when `PATH` needs a change, it prints the line to add instead of editing `~/.zshrc` or `~/.bashrc`.
 - **Changes only what you ask** — it writes its own configuration and state, the launchers, account directories (including the VS Code data that `code` keeps in `<root>/.apps`) and shared links. A Claude Code settings file is changed only by `statusline install` (the file you name, with a backup) and `add --config-from` (the new account's `settings.json`).
 - **Migrate the default account** — move your existing `~/.claude` into the account root without logging out. `claude` keeps working exactly as before.
@@ -80,7 +80,7 @@ The launchers are plain shell scripts. They keep working even if you uninstall m
 
 ## Prerequisites
 
-**Servers.** None. multi-claude runs only on your own computer; its only network requests are the plan lookups and token renewals of `list`, sent to Anthropic.
+**Servers.** None. multi-claude runs only on your own computer; its only network requests are the plan lookups and token renewals of `list` and the connection check of `doctor --network`, all sent to Anthropic.
 
 **Your computer.**
 
@@ -143,8 +143,19 @@ Run `./install.sh --help` for all options.
 
 ### Windows
 
-Windows support is new. Install with `pipx install multi-claude-cli`; the installer script is for macOS and Linux
-only. Everything above works the same way, with these differences:
+Windows support is new. Install it with pipx; the installer script is for macOS and Linux only. If `pipx` is not
+installed yet, run these in cmd or PowerShell (with Python 3.8 or later; use `python` instead of `py` if you do not
+have the Python launcher):
+
+```
+py -m pip install --user pipx
+py -m pipx ensurepath
+py -m pipx install multi-claude-cli
+```
+
+Then open a new terminal so the `PATH` change takes effect, and check with `multi-claude --version`. With pipx
+already on `PATH`, `pipx install multi-claude-cli` is enough. Everything above works the same way, with these
+differences:
 
 - Launchers are `claude-<name>.cmd` and `claude-auto.cmd` in `%USERPROFILE%\.local\bin` (the directory
   `pipx ensurepath` adds to `PATH`), so they run from PowerShell and cmd alike. They read the proxy, variables
@@ -495,6 +506,8 @@ Notes:
 
 `multi-claude doctor` checks, without changing anything: the configuration and any unfinished migration, whether `claude` and the launcher directory are on `PATH`, whether each launcher is up to date and not hidden by another file of the same name, whether each account directory exists and is private (`0700`), the default account's link, broken shared links, whether a login exists, and variables such as `ANTHROPIC_API_KEY` that override the accounts' logins. Every problem comes with the command that fixes it. It exits with 1 when there is an error; `--json` prints the results for scripts.
 
+`multi-claude doctor --network` also checks that each account can reach `api.anthropic.com` and `platform.claude.com` through the proxy it starts with (including the `env` of its `settings.json`). It connects step by step and says where it stopped: the proxy is not running, the proxy cannot get through, a name does not resolve, the secure connection was cut, the certificate could not be verified, a timeout, or `NO_PROXY` sends the account around its proxy. SOCKS and malformed proxy URLs, which Claude Code cannot use, are reported without connecting; https proxies are not checked. It sends one `HEAD /` per address and proxy (a second one if the first fails), with no login or token; addresses covered by `NO_PROXY` are checked directly.
+
 ```sh
 multi-claude completion bash > ~/.local/share/bash-completion/completions/multi-claude
 multi-claude completion zsh > "${fpath[1]}/_multi-claude"   # or any directory on your fpath
@@ -598,7 +611,7 @@ Every command's `--help` ends with examples you can copy, covering its options,
 | `multi-claude list [--verbose \| --json \| --names] [--no-refresh] [--offline]` | Show accounts, launchers, login state and the plan and billing channel looked up from Anthropic. `--json` adds usage and is meant for scripts; `--names` prints only the names; `--no-refresh` does not renew expired access tokens (never writes to a login); `--offline` skips the plan lookup (no token read, no network). A `RENEWS` column (and a `renews` key in `--json`) shows the renewal dates you recorded. |
 | `multi-claude usage [NAME] [--json]` | Show the last known 5-hour and 7-day usage of each account. |
 | `multi-claude usage --history [NAME] [--days N] [--by day\|model] [--json]` | Token usage per day or model, counted from the session files on this machine (default: 7 days). |
-| `multi-claude doctor [--json] [--verbose]` | Check the configuration, launchers, account directories, shared links, logins and environment. |
+| `multi-claude doctor [--json] [--verbose] [--network]` | Check the configuration, launchers, account directories, shared links, logins and environment; `--network` also checks each account's connection to Anthropic. |
 | `multi-claude route DIR NAME`, `route DIR --remove`, `route --default NAME`, `route --no-default` | Choose an account by directory for `claude-auto`. |
 | `multi-claude which [DIR]` | Show which account `claude-auto` would use in `DIR` (default: the current directory). |
 | `multi-claude rename OLD NEW` | Rename an account and its launcher. The directory and the login stay. |

{multi_claude_cli-0.15.0 → multi_claude_cli-0.16.0}/README.md

@@ -11,7 +11,7 @@
 
 Use several [Claude Code](https://code.claude.com/docs) accounts on one machine, at the same time. Each account keeps its own login, settings and history and, if you like, its own proxy. No more logging out and in again.
 
-It never copies or exports your login and never edits your shell startup files. Only `list` reads an account's access token and goes online, to ask Anthropic for the current plan (renewing the token first if it has expired); `list --offline` skips all of that.
+It never copies or exports your login and never edits your shell startup files. Only `list` reads an account's access token and goes online, to ask Anthropic for the current plan (renewing the token first if it has expired); `list --offline` skips all of that. `doctor --network` also goes online, but only when you ask for it and without any login.
 
 ```sh
 claude-work        # Claude Code with your work account
@@ -39,7 +39,7 @@ The launchers are plain shell scripts. They keep working even if you uninstall m
 ## Features
 
 - **Your login stays yours** — logins are never copied or exported. One command touches them: `list` takes each account's access token (from the keychain, or `.credentials.json` on Linux) to ask Anthropic which plan the account is on, and when that token has expired it renews it the way Claude Code does and saves the new one in the same place. Tokens stay in memory and go only to Anthropic (`api.anthropic.com`, and `platform.claude.com` for a renewal), through that account's proxy. `list --no-refresh` never writes, `list --offline` reads nothing. Every other command only checks whether a login exists. `migrate-default` and `restore` move whole account directories, and on Linux the credentials file moves with its directory without being opened.
-- **Only `list` goes online** — its plan lookup (one request per account, plus one to renew an expired token) is the only connection multi-claude makes: no telemetry, no usage reporting, no update checks. `list --offline` makes none. Only the installer, pipx or Homebrew download the package.
+- **Only `list` and `doctor --network` go online** — the plan lookup of `list` (one request per account, plus one to renew an expired token) and the connection check of `doctor --network` (one `HEAD /` without credentials to `api.anthropic.com` and `platform.claude.com` per proxy, repeated once if it fails) are the only connections multi-claude makes: no telemetry, no usage reporting, no update checks. `list --offline` makes none. Only the installer, pipx or Homebrew download the package.
 - **Leaves your shell alone** — when `PATH` needs a change, it prints the line to add instead of editing `~/.zshrc` or `~/.bashrc`.
 - **Changes only what you ask** — it writes its own configuration and state, the launchers, account directories (including the VS Code data that `code` keeps in `<root>/.apps`) and shared links. A Claude Code settings file is changed only by `statusline install` (the file you name, with a backup) and `add --config-from` (the new account's `settings.json`).
 - **Migrate the default account** — move your existing `~/.claude` into the account root without logging out. `claude` keeps working exactly as before.
@@ -52,7 +52,7 @@ The launchers are plain shell scripts. They keep working even if you uninstall m
 
 ## Prerequisites
 
-**Servers.** None. multi-claude runs only on your own computer; its only network requests are the plan lookups and token renewals of `list`, sent to Anthropic.
+**Servers.** None. multi-claude runs only on your own computer; its only network requests are the plan lookups and token renewals of `list` and the connection check of `doctor --network`, all sent to Anthropic.
 
 **Your computer.**
 
@@ -115,8 +115,19 @@ Run `./install.sh --help` for all options.
 
 ### Windows
 
-Windows support is new. Install with `pipx install multi-claude-cli`; the installer script is for macOS and Linux
-only. Everything above works the same way, with these differences:
+Windows support is new. Install it with pipx; the installer script is for macOS and Linux only. If `pipx` is not
+installed yet, run these in cmd or PowerShell (with Python 3.8 or later; use `python` instead of `py` if you do not
+have the Python launcher):
+
+```
+py -m pip install --user pipx
+py -m pipx ensurepath
+py -m pipx install multi-claude-cli
+```
+
+Then open a new terminal so the `PATH` change takes effect, and check with `multi-claude --version`. With pipx
+already on `PATH`, `pipx install multi-claude-cli` is enough. Everything above works the same way, with these
+differences:
 
 - Launchers are `claude-<name>.cmd` and `claude-auto.cmd` in `%USERPROFILE%\.local\bin` (the directory
   `pipx ensurepath` adds to `PATH`), so they run from PowerShell and cmd alike. They read the proxy, variables
@@ -467,6 +478,8 @@ Notes:
 
 `multi-claude doctor` checks, without changing anything: the configuration and any unfinished migration, whether `claude` and the launcher directory are on `PATH`, whether each launcher is up to date and not hidden by another file of the same name, whether each account directory exists and is private (`0700`), the default account's link, broken shared links, whether a login exists, and variables such as `ANTHROPIC_API_KEY` that override the accounts' logins. Every problem comes with the command that fixes it. It exits with 1 when there is an error; `--json` prints the results for scripts.
 
+`multi-claude doctor --network` also checks that each account can reach `api.anthropic.com` and `platform.claude.com` through the proxy it starts with (including the `env` of its `settings.json`). It connects step by step and says where it stopped: the proxy is not running, the proxy cannot get through, a name does not resolve, the secure connection was cut, the certificate could not be verified, a timeout, or `NO_PROXY` sends the account around its proxy. SOCKS and malformed proxy URLs, which Claude Code cannot use, are reported without connecting; https proxies are not checked. It sends one `HEAD /` per address and proxy (a second one if the first fails), with no login or token; addresses covered by `NO_PROXY` are checked directly.
+
 ```sh
 multi-claude completion bash > ~/.local/share/bash-completion/completions/multi-claude
 multi-claude completion zsh > "${fpath[1]}/_multi-claude"   # or any directory on your fpath
@@ -570,7 +583,7 @@ Every command's `--help` ends with examples you can copy, covering its options,
 | `multi-claude list [--verbose \| --json \| --names] [--no-refresh] [--offline]` | Show accounts, launchers, login state and the plan and billing channel looked up from Anthropic. `--json` adds usage and is meant for scripts; `--names` prints only the names; `--no-refresh` does not renew expired access tokens (never writes to a login); `--offline` skips the plan lookup (no token read, no network). A `RENEWS` column (and a `renews` key in `--json`) shows the renewal dates you recorded. |
 | `multi-claude usage [NAME] [--json]` | Show the last known 5-hour and 7-day usage of each account. |
 | `multi-claude usage --history [NAME] [--days N] [--by day\|model] [--json]` | Token usage per day or model, counted from the session files on this machine (default: 7 days). |
-| `multi-claude doctor [--json] [--verbose]` | Check the configuration, launchers, account directories, shared links, logins and environment. |
+| `multi-claude doctor [--json] [--verbose] [--network]` | Check the configuration, launchers, account directories, shared links, logins and environment; `--network` also checks each account's connection to Anthropic. |
 | `multi-claude route DIR NAME`, `route DIR --remove`, `route --default NAME`, `route --no-default` | Choose an account by directory for `claude-auto`. |
 | `multi-claude which [DIR]` | Show which account `claude-auto` would use in `DIR` (default: the current directory). |
 | `multi-claude rename OLD NEW` | Rename an account and its launcher. The directory and the login stay. |

{multi_claude_cli-0.15.0 → multi_claude_cli-0.16.0}/src/multi_claude/__init__.py

@@ -1,3 +1,3 @@
 """multi-claude：管理多个 Claude Code 账号的配置目录、启动命令、代理与启动参数。"""
 
-__version__ = "0.15.0"
+__version__ = "0.16.0"

{multi_claude_cli-0.15.0 → multi_claude_cli-0.16.0}/src/multi_claude/cli.py

@@ -217,6 +217,7 @@ _SUBCOMMAND_EXAMPLES = {
         ("multi-claude doctor", "check the setup and suggest fixes"),
         ("multi-claude doctor --verbose", "also list the checks that passed"),
         ("multi-claude doctor --json", "for scripts"),
+        ("multi-claude doctor --network", "also check that each account can reach Anthropic (uses the network)"),
     ],
     "route": [
         ("multi-claude route ~/work work", "claude-auto uses work under ~/work"),
@@ -397,6 +398,9 @@ def build_parser() -> argparse.ArgumentParser:
     p_doctor = sub.add_parser("doctor", description="check the accounts, launchers and environment (read-only)")
     p_doctor.add_argument("--json", action="store_true", help="print machine-readable JSON")
     p_doctor.add_argument("--verbose", action="store_true", help="also list the checks that passed")
+    p_doctor.add_argument("--network", action="store_true",
+                          help="also connect to api.anthropic.com and platform.claude.com through each account's "
+                               "proxy (sends no credentials)")
 
     p_route = sub.add_parser("route", description="choose an account by directory for claude-auto: route DIR NAME, "
                                            "route DIR --remove, route --default NAME, route --no-default")
@@ -655,7 +659,7 @@ def main(argv: Optional[List[str]] = None) -> int:
         print(completion.render(args.shell, build_parser()), end="")
         return accounts.EXIT_OK
     if args.command == "doctor":
-        return cmd_doctor(args.json, args.verbose)
+        return cmd_doctor(args.json, args.verbose, args.network)
 
     try:
         notice = migrate.pending_journal_notice()
@@ -2508,9 +2512,9 @@ def cmd_statusline(action: str, path: str, dry_run: bool) -> int:
     return accounts.EXIT_OK
 
 
-def cmd_doctor(as_json: bool, verbose: bool) -> int:
+def cmd_doctor(as_json: bool, verbose: bool, network: bool = False) -> int:
     try:
-        checks = doctor.run_checks()
+        checks = doctor.run_checks(network)
     except OSError as exc:
         # 意外的读写错误也记成一条检查结果，保证 --json 在任何情况下都输出合法 JSON。
         checks = [doctor.Check("doctor", doctor.LEVEL_ERROR, "-", "{}: {}".format(type(exc).__name__, exc))]

{multi_claude_cli-0.15.0 → multi_claude_cli-0.16.0}/src/multi_claude/doctor.py

@@ -2,6 +2,8 @@
 
 所有检查都不修改任何东西、不读凭据：登录检查沿用 identity.probe 的存在性探测。
 每条非 ok 结果的 message 里给出修复命令，由用户自己执行。
+加 `--network` 时另由 netcheck.py 联网检查每个账号能否连上 api.anthropic.com 与 platform.claude.com
+（每个地址一次不带凭据的 HEAD /，不读凭据）；不加时不联网。
 配置文件或迁移记录损坏时不抛异常，而是记成对应检查项的 error，其余不依赖配置的检查照常执行，
 这样 `doctor --json` 在任何状态下都输出合法 JSON。
 """
@@ -29,7 +31,7 @@ class Check(NamedTuple):
     message: str
 
 
-def run_checks() -> List[Check]:
+def run_checks(network: bool = False) -> List[Check]:
     checks: List[Check] = []
     checks.append(_check_journal())
     config, config_check = _load()
@@ -42,6 +44,10 @@ def run_checks() -> List[Check]:
     for account in config.accounts.values():
         checks.extend(_check_account(config, account))
     checks.extend(_check_routes(config))
+    if network:
+        # 只在 --network 时 import：netcheck 反向 import 本模块的 Check，放在顶部会循环导入。
+        from . import netcheck
+        checks.extend(netcheck.run(config))
     return checks