@drakon-systems/multi-clawd 1.3.0 → 1.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +44 -9
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -11,7 +11,7 @@ same model, next account, full harness on every hop.
11
11
 
12
12
  [![OpenClaw plugin](https://img.shields.io/badge/OpenClaw-plugin-ff4f00)](https://docs.openclaw.ai/plugins)
13
13
  [![npm](https://img.shields.io/badge/npm-%40drakon--systems%2Fmulti--clawd-cb3837)](https://www.npmjs.com/package/@drakon-systems/multi-clawd)
14
- [![version](https://img.shields.io/badge/version-1.0.1-4c9aff)](CHANGELOG.md)
14
+ [![version](https://img.shields.io/npm/v/%40drakon-systems%2Fmulti-clawd?color=4c9aff&label=version)](CHANGELOG.md)
15
15
  [![license: MIT](https://img.shields.io/badge/license-MIT-2ea44f)](LICENSE)
16
16
  [![TypeScript](https://img.shields.io/badge/TypeScript-strict-3178c6)](tsconfig.json)
17
17
 
@@ -21,6 +21,37 @@ same model, next account, full harness on every hop.
21
21
 
22
22
  ---
23
23
 
24
+ ## Quick start
25
+
26
+ ```bash
27
+ npm i -g @drakon-systems/multi-clawd # the CLI (once)
28
+
29
+ multi-clawd update # install (or update) the OpenClaw plugin — right flags, restart, doctor
30
+ multi-clawd setup # guided wizard: accounts, isolated second login, pool, watchdog
31
+ multi-clawd explain # your whole setup in plain English — accounts, chain, live health
32
+ multi-clawd doctor # health check (add --probe for a live end-to-end turn)
33
+ ```
34
+
35
+ That's the entire lifecycle. `update` installs the plugin when it's missing and
36
+ upgrades it when it's not — nobody types registry flags. `setup` walks you
37
+ through the whole shape below and merges config **non-destructively** (backup
38
+ first, existing accounts never overwritten, re-runs are no-ops). Prefer not to
39
+ install anything? Every command also runs as
40
+ `npx @drakon-systems/multi-clawd <command>`.
41
+
42
+ **The 3-step picture** `setup` walks you through:
43
+
44
+ 1. **Main account** — your existing `claude` login, used as-is (nothing to do).
45
+ 2. **Second account** — lives in its **own isolated config dir** (a separate
46
+ Claude "app", e.g. `~/.claw2`), so the two logins can never clobber each
47
+ other; token via a secret-manager reference (recommended), token file, or
48
+ the dir's own login.
49
+ 3. **The pool** — one backend id (`clawd/…`) fronting both: every launch runs
50
+ on the first account that isn't nearly maxed out, and your fallback chain
51
+ routes through it.
52
+
53
+ Then `multi-clawd explain` shows you exactly what you built.
54
+
24
55
  ## Why
25
56
 
26
57
  OpenClaw's bundled `claude-cli` backend runs Claude Code on a **single**
@@ -113,20 +144,24 @@ Code backend runs.
113
144
 
114
145
  ## Install
115
146
 
116
- **From npm (recommended):**
147
+ **The CLI does it all (recommended)** — see [Quick start](#quick-start):
148
+
149
+ ```bash
150
+ npm i -g @drakon-systems/multi-clawd && multi-clawd update
151
+ ```
152
+
153
+ `update` runs the registry install with the right flags, offers the gateway
154
+ restart, and finishes with a doctor health check. Prefer the raw form?
117
155
 
118
156
  ```bash
119
157
  openclaw plugins install @drakon-systems/multi-clawd --pin
120
158
  openclaw gateway restart
121
159
  ```
122
160
 
123
- The gateway pulls the prebuilt package — no clone, no build step, nothing to
124
- keep in sync. `--pin` records the exact resolved version, so an upgrade is a
125
- deliberate `@latest`, never a surprise. `openclaw` itself is a *peer*
126
- dependency (the host provides it), so the install stays lean. Confirm with
127
- `openclaw plugins list` (expect `multi-clawd` enabled) — it also shows the
128
- install path; run the doctor from there:
129
- `node <install-path>/scripts/doctor.mjs`.
161
+ Either way the gateway pulls the prebuilt package — no clone, no build step,
162
+ nothing to keep in sync. `--pin` records the exact resolved version, so an
163
+ upgrade is a deliberate act, never a surprise. `openclaw` itself is a *peer*
164
+ dependency (the host provides it), so the install stays lean.
130
165
 
131
166
  **From ClawHub (alternative registry):**
132
167
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@drakon-systems/multi-clawd",
3
- "version": "1.3.0",
3
+ "version": "1.3.1",
4
4
  "description": "Multi-account Claude Code failover for OpenClaw — register additional Claude (Max/Pro) logins as first-class CLI backends and keep the full skills/MCP harness across every account.",
5
5
  "type": "module",
6
6
  "license": "MIT",