@paigy/harness 0.1.6 → 0.1.8

package/README.md

@@ -157,12 +157,13 @@ re-voiceable, revocable.
 ## Install anywhere (the curl path)
 
 ```sh
-curl -fsSL https://paigy.ai/install.sh | sh
+curl -fsSL https://paigy.ai/install | sh
 ```
 
-Installs the npm CLI (one self-contained file — the workspace libs are bundled),
-runs `paigy-harness pair` (device flow with a terminal QR, landing in the Desktop
-slot), and prints the host/service next steps. `paigy-harness service` installs a
+Installs the npm CLI (one self-contained file — the workspace libs are bundled) and
+runs `paigy-harness setup`: QR-pairs the machine, hatches each detected agent's
+identity (no codes), registers the MCP + statusline, grants a workspace, installs
+the host service. `paigy-harness service` installs a
 macOS launchd agent so hosting survives reboots — the host loop IS the service,
 launchd just keeps it alive (the old "no daemon" note was about the WAKE channel,
 which still belongs to paigy-listen).
@@ -191,7 +192,7 @@ import Electron — a machine with only the CLI is exactly as launchable as one
 the window.
 
 Pairing is one-time and lives in `~/.paigy` — the app reads it, never mints it. If
-you've never paired: `npx -y -p @paigy/mcp paigy-mcp-onboard`.
+you've never paired: `paigy-harness setup`.
 
 ## Uninstall
 
@@ -224,7 +225,7 @@ LAST, after the hooks are gone.
   token — per-run identity is threaded through every network touch (`run.ts` binds
   submit/check/ack once per session), so parallel sessions never share a
   conversation. "Stop sessions" stops them all; per-session stop is UI away.
-- **Deliberately no auto-start daemon.** A promptless harness has no thread to pump,
-  and `paigy-listen` + `PAIGY_ON_WAKE` (#486) already own the standing wake channel —
-  a launchd `paigy-harness` would be a second daemon racing the first. The composition
-  is: the listener wakes on Paigy work, and what it runs can be `paigy-harness`.
+- **The host service IS the daemon** (`paigy-harness service`, launchd, KeepAlive) —
+  it claims phone launches and runs sessions. The WAKE channel for terminal-agent
+  replies still belongs to `paigy-listen` + `PAIGY_ON_WAKE` (#486); spawn-on-wake
+  needs the slot-lease design in companion.md before it auto-wires.

package/dist/cli.js

@@ -30825,7 +30825,7 @@ var authToken = (explicit) => explicit ?? tokenOverride ?? readToken();
 async function hatch(name, voice = null) {
   const res = ensureAuthed(await reach(`${BACKEND_URL}/api/hatch`, {
     method: "POST",
-    headers: { "content-type": "application/json", authorization: `Bearer ${readToken()}` },
+    headers: { "content-type": "application/json", authorization: `Bearer ${authToken()}` },
     body: JSON.stringify({ name, voice })
   }));
   if (!res.ok) throw new Error(`hatch failed: ${res.status} ${await res.text()}`);
@@ -32510,7 +32510,9 @@ async function main() {
       }
     } else console.log("start hosting with: paigy-harness host   (keep it running under your init system)");
     const TERMINAL_AGENTS = [
-      { cli: "claude", name: "Claude Code", slot: "mcp-agent", wire: "claude mcp add --scope user paigy -- npx -y @paigy/mcp@latest" },
+      // Wire = MCP registration + the plugin (skills, hooks, idle-escalation — the
+      // piece that makes a LIVE session notice your requests without polling).
+      { cli: "claude", name: "Claude Code", slot: "mcp-agent", wire: "claude mcp add --scope user paigy -- npx -y @paigy/mcp@latest && claude plugin marketplace add paigy-ai/mcp; claude plugin install paigy" },
       { cli: "codex", name: "Codex", slot: "codex", wire: "codex mcp add paigy -- npx -y @paigy/mcp@latest" },
       { cli: "antigravity", name: "Antigravity", slot: "antigravity" }
     ];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@paigy/harness",
-  "version": "0.1.6",
+  "version": "0.1.8",
   "description": "Run Claude Code / Codex on this machine, bridged to Paigy — launchable from your phone.",
   "license": "MIT",
   "type": "module",