@drakon-systems/multi-clawd 1.4.0 → 1.4.2

package/README.md

@@ -167,7 +167,7 @@ dependency (the host provides it), so the install stays lean.
 **From ClawHub (alternative registry):**
 
 ```bash
-openclaw plugins install clawhub:drakon-systems/multi-clawd
+openclaw plugins install clawhub:@drakon-systems/multi-clawd
 ```
 
 **From source (contributors, or ahead of a release):**
@@ -224,17 +224,28 @@ install → re-add plan.
 
 ## Set up a second account
 
-**Easiest: the setup wizard.** It walks you through the whole shape below —
-main account, isolated second account, token storage, pool — and merges the
-result into `openclaw.json` non-destructively (backup first, merge by id,
-re-runs are no-ops, never sees a token value):
+**Easiest: the wizard, then the login command.** The wizard walks you through
+the whole shape below — main account, isolated second account, token storage,
+pool — and merges the result into `openclaw.json` non-destructively (backup
+first, merge by id, existing accounts never overwritten, re-runs are no-ops,
+never sees a token value). Then `login` performs the actual Claude sign-in
+for any account — right flow, right config dir, verified afterwards with the
+signed-in email shown:
 
 ```bash
-npm run setup                                            # source checkout
-node ~/.openclaw/extensions/multi-clawd/scripts/setup.mjs  # installed copy
-# add --dry-run to preview the changes without writing anything
+multi-clawd setup            # wire the accounts + pool (add --dry-run to preview)
+multi-clawd login claw2      # launch the second account's Claude sign-in
+multi-clawd login claw1      # (works for re-authing ANY account, any time)
 ```
 
+`login` knows what each account is: a native account signs in against the
+default dir/keychain, an isolated-dir account inside its own dir (created
+`0700` if missing), and token accounts get `claude setup-token` — in a
+throwaway scratch dir when the account has no dir of its own, so your main
+login is never disturbed. You do the OAuth in the launched flow; the CLI
+never captures, stores, or prints a token value.
+(From a source checkout, `npm run setup` still works for the wizard.)
+
 The key idea either way: your **main** account keeps the default `~/.claude`
 login untouched, and each **extra** account gets its *own isolated config
 dir* — a separate Claude "app" — so the logins can never clobber each other.
@@ -435,6 +446,19 @@ event, and no plugin API can force a rebuild. See `DESIGN.md`.
 
 ## Security
 
+**Full declaration of what this plugin touches — nothing else:**
+
+| Surface | What multi-clawd does |
+|---|---|
+| Network | **Zero egress of its own.** The only network activity is npm/registry traffic during `install`/`update`, and the Claude Code subprocesses talking to Anthropic exactly as the bundled backend does. No telemetry, no analytics, no vendor endpoints. |
+| Credentials | Reads each account's setup-token at launch (file, or a secret-manager reference resolved by your gateway) and passes it **only** via the child process env. Never written elsewhere, never logged, never printed — log redaction is covered by dedicated tests. |
+| Files read | `~/.openclaw/openclaw.json` (config), account config dirs you declare (e.g. `~/.claw2`), token files you declare. |
+| Files written | `~/.openclaw/state/multi-clawd/<account>.json` (local usage-health telemetry, stays on the box), config backups the wizard takes before merging, and — only if you accept the wizard's watchdog step — one systemd user unit / launchd plist pointing at the installed watchdog script. |
+| Processes | Spawns the `claude` CLI per turn (same as the bundled backend). The optional watchdog may restart the OpenClaw gateway when the eviction signature appears — that's its entire job, documented below. |
+| Consent | The wizard asks before every write, merges non-destructively, and never overwrites an existing account entry. `--dry-run` previews everything. |
+
+Housekeeping:
+
 - Tokens are never committed and never logged; `.gitignore` blocks token
   and account directories by default.
 - Prefer a secret reference (`oauthTokenRef`, v0.3) over a plaintext
@@ -477,10 +501,25 @@ Early but real — built for and dogfooded in production.
   (capped at 8d with a clock-skew alarm), reset-less windows keep TTL/decay,
   and model windows age by their own TTL independent of pool `staleAfterMs`
   — closes the quiet-pool blindness half of the no-flip failure class ✅
-- **v0.4** — standalone localhost proxy (OpenAI-compatible) so Hermes and
+- **v1.0** — the public line: published to npm as
+  [`@drakon-systems/multi-clawd`](https://www.npmjs.com/package/@drakon-systems/multi-clawd),
+  `openclaw` demoted to an optional peer, registry installs verified
+  end-to-end ✅
+- **v1.1–v1.2** — the `multi-clawd` CLI (`update` / `setup` / `doctor`);
+  wizard owns the eviction watchdog (schedules it, detects + repoints
+  orphaned units after migrations); wizard account-protection (existing
+  accounts default to keep-unchanged; suspicious secret refs challenged) ✅
+- **v1.3** — `multi-clawd explain`: the whole setup in plain English —
+  accounts, pool decisions, every fallback rung annotated, live health with
+  reset times ✅
+- **v1.4** — `multi-clawd login <account>`: the right Claude sign-in flow
+  for each account shape, verified afterwards (signed-in email shown, token
+  values never touched); ClawHub package published under
+  `@drakon-systems` ✅
+- **Next** — standalone localhost proxy (OpenAI-compatible) so Hermes and
   custom runtimes can share the pool; true per-session affinity; local
-  five-hour-window signal (turn counting)
-- **v1.0** — npm + ClawHub parity releases
+  five-hour-window signal (turn counting); per-account lock for the shim
+  persistence race
 
 See [`DESIGN.md`](./DESIGN.md) for the architecture, the three obvious
 approaches that *don't* work, and why.

package/dist/index.js

@@ -216,7 +216,7 @@ const SHIM_PATH = fileURLToPath(new URL("./shim.js", import.meta.url));
 export function healthStateFile(accountId) {
     return join(homedir(), ".openclaw", "state", "multi-clawd", `${accountId}.json`);
 }
-function buildBackend(account, execMode) {
+export function buildBackend(account, execMode) {
     return {
         id: account.id,
         liveTest: {
@@ -247,7 +247,7 @@ function buildBackend(account, execMode) {
             imagePathScope: "workspace",
             sessionArg: "--session-id",
             sessionMode: "always",
-            reseedFromRawTranscriptWhenUncompacted: false,
+            reseedFromRawTranscriptWhenUncompacted: true,
             sessionIdFields: ["session_id", "sessionId", "conversation_id", "conversationId"],
             systemPromptFileArg: "--append-system-prompt-file",
             systemPromptMode: "append",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@drakon-systems/multi-clawd",
-  "version": "1.4.0",
+  "version": "1.4.2",
   "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.",
   "type": "module",
   "license": "MIT",
@@ -69,5 +69,9 @@
     "openclaw": "2026.7.1",
     "typescript": "^5.9.0",
     "vitest": "^4.1.10"
+  },
+  "homepage": "https://github.com/Drakon-Systems-Ltd/multi-clawd#readme",
+  "bugs": {
+    "url": "https://github.com/Drakon-Systems-Ltd/multi-clawd/issues"
   }
 }