@drakon-systems/multi-clawd 1.4.0 → 1.4.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 +18 -7
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -224,17 +224,28 @@ install → re-add plan.
224
224
 
225
225
  ## Set up a second account
226
226
 
227
- **Easiest: the setup wizard.** It walks you through the whole shape below
228
- main account, isolated second account, token storage, pool — and merges the
229
- result into `openclaw.json` non-destructively (backup first, merge by id,
230
- re-runs are no-ops, never sees a token value):
227
+ **Easiest: the wizard, then the login command.** The wizard walks you through
228
+ the whole shape below — main account, isolated second account, token storage,
229
+ pool — and merges the result into `openclaw.json` non-destructively (backup
230
+ first, merge by id, existing accounts never overwritten, re-runs are no-ops,
231
+ never sees a token value). Then `login` performs the actual Claude sign-in
232
+ for any account — right flow, right config dir, verified afterwards with the
233
+ signed-in email shown:
231
234
 
232
235
  ```bash
233
- npm run setup # source checkout
234
- node ~/.openclaw/extensions/multi-clawd/scripts/setup.mjs # installed copy
235
- # add --dry-run to preview the changes without writing anything
236
+ multi-clawd setup # wire the accounts + pool (add --dry-run to preview)
237
+ multi-clawd login claw2 # launch the second account's Claude sign-in
238
+ multi-clawd login claw1 # (works for re-authing ANY account, any time)
236
239
  ```
237
240
 
241
+ `login` knows what each account is: a native account signs in against the
242
+ default dir/keychain, an isolated-dir account inside its own dir (created
243
+ `0700` if missing), and token accounts get `claude setup-token` — in a
244
+ throwaway scratch dir when the account has no dir of its own, so your main
245
+ login is never disturbed. You do the OAuth in the launched flow; the CLI
246
+ never captures, stores, or prints a token value.
247
+ (From a source checkout, `npm run setup` still works for the wizard.)
248
+
238
249
  The key idea either way: your **main** account keeps the default `~/.claude`
239
250
  login untouched, and each **extra** account gets its *own isolated config
240
251
  dir* — a separate Claude "app" — so the logins can never clobber each other.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@drakon-systems/multi-clawd",
3
- "version": "1.4.0",
3
+ "version": "1.4.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",