@cabane/companion 0.6.181 → 0.6.183

package/README.md

@@ -44,16 +44,26 @@ The script brings its own Node (checksum-checked, into `~/.cabane`) and needs no
 npm i -g @cabane/companion && cabane setup CODE
 ```
 
-Either way `cabane setup CODE` pairs the device to your account, joins it to that workspace, detects your harnesses, and starts the Companion: as a service on macOS and Linux, in the background elsewhere. No confirm, no name screen, no browser on the device. The same line on a device that is already paired joins it to the workspace and mints nothing.
+Either way `cabane setup CODE` pairs the device to your account, joins it to that workspace, starts the Companion in the background, waits for its first check-in, and ends with the device's state in Cabane's words. No confirm, no name screen, no browser on the device. The same line on a device that is already paired joins it to the workspace and mints nothing.
 
 ```
-✓ Claude Code   signed in (2.1.289) — connected
-  Codex         not signed in — run  codex login
-  OpenCode      not running
-All set here. Back to the browser.
+✓ Paired as "maya-mbp" with Acme.
+  Cabane is running in the background. This device is ready — checked in 2s ago.
+
+  Harnesses on this device
+  ✓ Claude Code   connected — signed in (2.1.289)
+    Codex         needs sign-in — run  codex login
+    OpenCode      off — not running
+
+  Status  cabane status     Stop  cabane stop     Log  cabane logs
+  Start at login and keep Cabane updating itself:  cabane service install
+
+  In Cabane: https://app.cabane.ai/acme/settings/devices
 ```
 
-With nothing signed in, the device still pairs and the Companion still runs; the rows say which harness needs sign-in, and the device shows **Needs attention** in Cabane until one is usable. Sign in, and the next check finds it: no restart.
+The device is online the moment the Companion checks in, before any harness is checked; Cabane shows it as **Checking harnesses…** until the first detection lands, then **Ready** or **Needs attention**. With nothing signed in, the device still pairs and the Companion still runs; the rows say which harness needs sign-in. Sign in, and the next check finds it: no restart. A harness that was signed in earlier in this run stays offered through a lapsed login, so a turn reaches the device, fails with the sign-in notice, and the first reply after you sign in again runs with no wait.
+
+Setup never installs the service. Run `cabane service install` when you want the Companion to start at login and keep itself updated; the closing block names it.
 
 A fresh device runs nothing yet. In a workspace, open an agent's page and assign it to the device; the Companion picks the assignment up on its next poll.
 
@@ -61,23 +71,23 @@ If `cabane` isn't found afterwards, open a new terminal, or run the `source` lin
 
 ## Commands
 
-| Command                              | What it does                                                                                                                                                            |
-| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `setup [CODE]`                       | With a code: pair or join, detect harnesses, start. Without: a re-runnable checklist that reports harnesses and starts what isn't running.                              |
-| `start [--foreground]`               | Run in the background. Never asks. Unpaired, it names `setup`. `--foreground` stays attached, for a supervisor of your own.                                             |
-| `stop`                               | Stop a running Companion cleanly. Ends any turn in progress.                                                                                                            |
-| `status`                             | Version and install, the paired device by its Cabane name, whether it's running, each harness's state, the sandbox posture, declared secret names, and local overrides. |
-| `update [--auto on\|off]`            | Install the version Cabane names now; with `--auto`, set whether the Companion keeps itself up to date.                                                                 |
-| `service install\|uninstall\|status` | Run as a systemd user service or a LaunchAgent that starts at boot and restarts if it stops; remove it; show its state.                                                 |
-| `logs [-n N] [-f]`                   | Recent log lines, or follow.                                                                                                                                            |
-| `transcript [file] [--last] [-f]`    | Read back a full agent turn, tool calls and results included.                                                                                                           |
-| `logout [--purge]`                   | Remove the device token and cached agent credentials. Doesn't remove the device from Cabane.                                                                            |
+| Command                              | What it does                                                                                                                                                                                               |
+| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `setup [CODE]`                       | With a code: pair or join, detect harnesses, start. Without: a re-runnable checklist that reports harnesses and starts what isn't running.                                                                 |
+| `start [--foreground]`               | Run in the background. Never asks. Unpaired, it names `setup`. `--foreground` stays attached, for a supervisor of your own.                                                                                |
+| `stop`                               | Stop a running Companion cleanly. Ends any turn in progress.                                                                                                                                               |
+| `status`                             | Version and install, the paired device by its Cabane name, its state in Cabane's words and when it last checked in, each harness's state, the sandbox posture, declared secret names, and local overrides. |
+| `update [--auto on\|off]`            | Install the version Cabane names now; with `--auto`, set whether the Companion keeps itself up to date.                                                                                                    |
+| `service install\|uninstall\|status` | Run as a systemd user service or a LaunchAgent that starts at boot and restarts if it stops; remove it; show its state.                                                                                    |
+| `logs [-n N] [-f]`                   | Recent log lines, or follow.                                                                                                                                                                               |
+| `transcript [file] [--last] [-f]`    | Read back a full agent turn, tool calls and results included.                                                                                                                                              |
+| `logout [--purge]`                   | Remove the device token and cached agent credentials. Doesn't remove the device from Cabane.                                                                                                               |
 
 Anything else about a device is done in Cabane, on the device's page.
 
 ## Keeping it running
 
-Under the service the Companion restarts if it stops, comes back after a reboot, and follows the version Cabane names: it installs the new version under `~/.cabane/versions`, checks it starts, and swaps between turns. A version that can't start is rolled back by the boot guard. `cabane update --auto off` stops updates; without the service, `cabane update` installs and the next `cabane start` runs it.
+Without the service, a reboot or a crash leaves the Companion stopped until the next `cabane start`, and the device shows **Offline** in Cabane. Under the service it restarts if it stops, comes back after a reboot, and follows the version Cabane names: it installs the new version under `~/.cabane/versions`, checks it starts, and swaps between turns. A version that can't start is rolled back by the boot guard. `cabane update --auto off` stops updates; without the service, `cabane update` installs and the next `cabane start` runs it.
 
 Other supervisors: run `cabane start --foreground` with `CABANE_COMPANION_SUPERVISED=1` set, using the absolute paths `~/.cabane/node/bin/node` and `~/.cabane/current/dist/bin.js`, which don't move on an update.
 

package/dist/cli.js

@@ -12554,11 +12554,24 @@ function parseHarnessRuntime(raw) {
   if (key === "opencode") return "opencode";
   return null;
 }
-function advertisedRuntimes(detection) {
-  return usableRuntimes(detection);
+function stillRunnable(agent) {
+  return agent.state === "usable" || agent.state === "signed_out" || agent.state === "problem" && agent.check.status === "check_failed";
+}
+function rememberUsed(used, detection) {
+  const next = /* @__PURE__ */ new Set();
+  for (const runtime of ["claude-code", "codex"]) {
+    const agent = detection[runtime];
+    if (agent.state === "usable" || used.has(runtime) && stillRunnable(agent)) next.add(runtime);
+  }
+  return next;
+}
+function advertisedRuntimes(detection, used) {
+  return HARNESS_RUNTIMES.filter(
+    (runtime) => detection[runtime].state === "usable" || used.has(runtime) && stillRunnable(detection[runtime])
+  );
 }
 function deriveHarnessSnapshot(detection) {
-  const advertised = new Set(advertisedRuntimes(detection));
+  const advertised = new Set(usableRuntimes(detection));
   const harnesses = HARNESS_RUNTIMES.map(
     (runtime) => derive(runtime, detection[runtime], advertised.has(runtime))
   );
@@ -16163,6 +16176,9 @@ var CompanionSupervisor = class {
   // control socket, so none can disagree with what is advertised. Null until
   // the first detection; a heartbeat spawns nothing and reads this.
   detection = null;
+  // The bundled harnesses a detection in this run found usable, which stay offered
+  // through a lapsed sign-in (`rememberUsed`). Empty until the first detection.
+  used = /* @__PURE__ */ new Set();
   detecting = null;
   // Liveness may be acknowledged before discovery. Execution waits on this
   // first look only, never on a periodic refresh of an established inventory.
@@ -16407,8 +16423,7 @@ var CompanionSupervisor = class {
   async sendHeartbeat(first = false) {
     if (!this.deviceApi) return;
     try {
-      if (!first && this.detection && advertisedRuntimes(this.detection).length === 0)
-        await this.detect();
+      if (!first && this.detection && this.advertised().length === 0) await this.detect();
       const store = loadSecretStoreTolerant(
         (m) => this.log.warn({ err: m }, "Could not read the secrets file. Check ~/.cabane/secrets.json.")
       );
@@ -16742,11 +16757,15 @@ var CompanionSupervisor = class {
   bundledResolution(runtime) {
     return this.resolveBundled(runtime);
   }
-  // Does this device OFFER a runtime — found usable by the last detection? The
-  // ONE signal the heartbeat manifest, the adapter registry and the dispatcher
-  // read, so what the device advertises and what it can select can't disagree.
+  // Does this device OFFER a runtime — usable now, or used in this run and still
+  // runnable? The ONE signal the heartbeat manifest, the adapter registry and the
+  // dispatcher read, so what the device advertises and what it can select can't
+  // disagree.
   offered(runtime) {
-    return this.detection !== null && advertisedRuntimes(this.detection).includes(runtime);
+    return this.advertised().includes(runtime);
+  }
+  advertised() {
+    return this.detection ? advertisedRuntimes(this.detection, this.used) : [];
   }
   // The address an OpenCode turn runs against: the serve detection found, else
   // the configured one, for the model list a beat still asks for.
@@ -17405,6 +17424,7 @@ var CompanionSupervisor = class {
         ...this.probeOpencode ? { probeOpencode: this.probeOpencode } : {}
       });
       this.detection = detection;
+      this.used = rememberUsed(this.used, detection);
       this.logBundledTransitions();
       this.harnessVersions = {
         claudeCode: detectedVersion(detection["claude-code"]),
@@ -17459,7 +17479,7 @@ var CompanionSupervisor = class {
     const health = this.connectorHealth.reports();
     if (health.length === 0 || !this.detection) return health;
     const named = new Set(health.map((r) => r.runtime));
-    const bare = advertisedRuntimes(this.detection).filter((runtime) => !named.has(runtime)).map((runtime) => ({ runtime }));
+    const bare = this.advertised().filter((runtime) => !named.has(runtime)).map((runtime) => ({ runtime }));
     return [...health, ...bare];
   }
   // Beat NOW and wait for it to land. `start` calls this before asking the

package/dist/runtime.js

@@ -13042,11 +13042,24 @@ function withTimeout(promise, fallback, timeoutMs) {
 }
 
 // src/harness-status.ts
-function advertisedRuntimes(detection) {
-  return usableRuntimes(detection);
+function stillRunnable(agent) {
+  return agent.state === "usable" || agent.state === "signed_out" || agent.state === "problem" && agent.check.status === "check_failed";
+}
+function rememberUsed(used, detection) {
+  const next = /* @__PURE__ */ new Set();
+  for (const runtime of ["claude-code", "codex"]) {
+    const agent = detection[runtime];
+    if (agent.state === "usable" || used.has(runtime) && stillRunnable(agent)) next.add(runtime);
+  }
+  return next;
+}
+function advertisedRuntimes(detection, used) {
+  return HARNESS_RUNTIMES.filter(
+    (runtime) => detection[runtime].state === "usable" || used.has(runtime) && stillRunnable(detection[runtime])
+  );
 }
 function deriveHarnessSnapshot(detection) {
-  const advertised = new Set(advertisedRuntimes(detection));
+  const advertised = new Set(usableRuntimes(detection));
   const harnesses = HARNESS_RUNTIMES.map(
     (runtime) => derive(runtime, detection[runtime], advertised.has(runtime))
   );
@@ -14095,6 +14108,9 @@ var CompanionSupervisor = class {
   // control socket, so none can disagree with what is advertised. Null until
   // the first detection; a heartbeat spawns nothing and reads this.
   detection = null;
+  // The bundled harnesses a detection in this run found usable, which stay offered
+  // through a lapsed sign-in (`rememberUsed`). Empty until the first detection.
+  used = /* @__PURE__ */ new Set();
   detecting = null;
   // Liveness may be acknowledged before discovery. Execution waits on this
   // first look only, never on a periodic refresh of an established inventory.
@@ -14339,8 +14355,7 @@ var CompanionSupervisor = class {
   async sendHeartbeat(first = false) {
     if (!this.deviceApi) return;
     try {
-      if (!first && this.detection && advertisedRuntimes(this.detection).length === 0)
-        await this.detect();
+      if (!first && this.detection && this.advertised().length === 0) await this.detect();
       const store = loadSecretStoreTolerant(
         (m) => this.log.warn({ err: m }, "Could not read the secrets file. Check ~/.cabane/secrets.json.")
       );
@@ -14674,11 +14689,15 @@ var CompanionSupervisor = class {
   bundledResolution(runtime) {
     return this.resolveBundled(runtime);
   }
-  // Does this device OFFER a runtime — found usable by the last detection? The
-  // ONE signal the heartbeat manifest, the adapter registry and the dispatcher
-  // read, so what the device advertises and what it can select can't disagree.
+  // Does this device OFFER a runtime — usable now, or used in this run and still
+  // runnable? The ONE signal the heartbeat manifest, the adapter registry and the
+  // dispatcher read, so what the device advertises and what it can select can't
+  // disagree.
   offered(runtime) {
-    return this.detection !== null && advertisedRuntimes(this.detection).includes(runtime);
+    return this.advertised().includes(runtime);
+  }
+  advertised() {
+    return this.detection ? advertisedRuntimes(this.detection, this.used) : [];
   }
   // The address an OpenCode turn runs against: the serve detection found, else
   // the configured one, for the model list a beat still asks for.
@@ -15337,6 +15356,7 @@ var CompanionSupervisor = class {
         ...this.probeOpencode ? { probeOpencode: this.probeOpencode } : {}
       });
       this.detection = detection;
+      this.used = rememberUsed(this.used, detection);
       this.logBundledTransitions();
       this.harnessVersions = {
         claudeCode: detectedVersion(detection["claude-code"]),
@@ -15391,7 +15411,7 @@ var CompanionSupervisor = class {
     const health = this.connectorHealth.reports();
     if (health.length === 0 || !this.detection) return health;
     const named = new Set(health.map((r) => r.runtime));
-    const bare = advertisedRuntimes(this.detection).filter((runtime) => !named.has(runtime)).map((runtime) => ({ runtime }));
+    const bare = this.advertised().filter((runtime) => !named.has(runtime)).map((runtime) => ({ runtime }));
     return [...health, ...bare];
   }
   // Beat NOW and wait for it to land. `start` calls this before asking the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cabane/companion",
-  "version": "0.6.181",
+  "version": "0.6.183",
   "type": "module",
   "description": "The Cabane Companion (headless): connect an agent on your machine to your Cabane workspace as a responder — drive work against your own codebase, files, and MCP servers without putting any of it in Cabane.",
   "license": "UNLICENSED",