@drakon-systems/multi-clawd 1.7.0 → 1.7.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.
- package/README.md +32 -2
- package/openclaw.plugin.json +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -153,7 +153,37 @@ npm i -g @drakon-systems/multi-clawd && multi-clawd update
|
|
|
153
153
|
```
|
|
154
154
|
|
|
155
155
|
`update` runs the registry install with the right flags, offers the gateway
|
|
156
|
-
restart, and finishes with a doctor health check.
|
|
156
|
+
restart, and finishes with a doctor health check.
|
|
157
|
+
|
|
158
|
+
> ### ⚠️ Keeping up to date: there are two halves
|
|
159
|
+
>
|
|
160
|
+
> One package installs as **two separate artifacts**, and they update by
|
|
161
|
+
> different routes:
|
|
162
|
+
>
|
|
163
|
+
> | Half | What it is | How it updates |
|
|
164
|
+
> |---|---|---|
|
|
165
|
+
> | **The plugin** | serves your turns — pooling, rotation, credentials | `multi-clawd update` |
|
|
166
|
+
> | **The CLI** | the `multi-clawd` command — `doctor`, `chain`, `setup`, `explain` | `npm i -g @drakon-systems/multi-clawd@latest` |
|
|
167
|
+
>
|
|
168
|
+
> **`multi-clawd update` upgrades the plugin, not itself.** Since v1.6.0 it
|
|
169
|
+
> notices when the command has fallen behind and offers to update it — but
|
|
170
|
+
> that notice ships *in the command*, so a CLI older than v1.6.0 has no code
|
|
171
|
+
> to warn you with. We found this on three of our own machines, all running
|
|
172
|
+
> current plugins behind commands that were three versions stale.
|
|
173
|
+
>
|
|
174
|
+
> **So run the global install once, by hand, to arm it:**
|
|
175
|
+
>
|
|
176
|
+
> ```bash
|
|
177
|
+
> npm i -g @drakon-systems/multi-clawd@latest
|
|
178
|
+
> ```
|
|
179
|
+
>
|
|
180
|
+
> After that it maintains itself. It matters because `doctor` and `chain` live
|
|
181
|
+
> in the CLI — a stale command reports *stale diagnostics about a current
|
|
182
|
+
> plugin*, which is a confusing way to be told nothing is wrong. `multi-clawd
|
|
183
|
+
> version` shows both halves, and since v1.6.0 says plainly whether the pair
|
|
184
|
+
> is a problem.
|
|
185
|
+
|
|
186
|
+
Prefer the raw form?
|
|
157
187
|
|
|
158
188
|
```bash
|
|
159
189
|
openclaw plugins install @drakon-systems/multi-clawd --pin
|
|
@@ -189,7 +219,7 @@ openclaw plugins install (Get-Location).Path
|
|
|
189
219
|
**Or let your agent install it.** Running an OpenClaw assistant or Claude
|
|
190
220
|
Code on the target machine already? Paste it this and go make coffee:
|
|
191
221
|
|
|
192
|
-
> Read https://raw.githubusercontent.com/Drakon-Systems-Ltd/multi-clawd/v1.7.
|
|
222
|
+
> Read https://raw.githubusercontent.com/Drakon-Systems-Ltd/multi-clawd/v1.7.1/SETUP-AGENT.md
|
|
193
223
|
> and follow it to set up multi-clawd on this machine. I own a second
|
|
194
224
|
> Claude account — ask me when you need me to log in.
|
|
195
225
|
|
package/openclaw.plugin.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"id": "multi-clawd",
|
|
3
3
|
"name": "multi-clawd",
|
|
4
|
-
"version": "1.7.
|
|
4
|
+
"version": "1.7.1",
|
|
5
5
|
"description": "Register additional Claude Code logins (Max/Pro accounts) as first-class OpenClaw CLI backends for cross-account failover, keeping the full skills/MCP harness on every account.",
|
|
6
6
|
"cliBackends": [
|
|
7
7
|
"claw1",
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@drakon-systems/multi-clawd",
|
|
3
|
-
"version": "1.7.
|
|
3
|
+
"version": "1.7.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",
|