@cabane/companion 0.6.2 → 0.6.3

package/dist/cli.js

@@ -7331,7 +7331,10 @@ ${reason}`,
       ...this.opts.local.claudeCode ? { claudeCode: this.opts.local.claudeCode } : {}
     });
     const onWarn = (msg, meta) => turnLog.warn(meta ?? {}, msg);
-    const adapters = [createClaudeCodeAdapter({ queryFn: this.opts.queryFn, onWarn })];
+    const adapters = [];
+    if (this.opts.claudeCodeAvailable?.() ?? true) {
+      adapters.push(createClaudeCodeAdapter({ queryFn: this.opts.queryFn, onWarn }));
+    }
     if (this.opts.opencodeServerUrl) {
       adapters.push(createOpencodeAdapter({ serverUrl: this.opts.opencodeServerUrl, onWarn }));
     }
@@ -8384,7 +8387,7 @@ var CompanionSupervisor = class {
           // until the first re-probe lands. Same exit-0 `claude --version` signal
           // either way, so the manifest's claude-code advertising is unchanged in
           // meaning — just refreshed on the beat instead of frozen at boot.
-          claudeCode: this.harnessSignals?.claudeOnPath ?? this.claudeCode,
+          claudeCode: this.claudeCodePresent(),
           opencode: !!this.config.opencode?.serverUrl,
           // CT481: advertise codex when the operator enabled it (config-gated,
           // like opencode — the CLI's presence is the operator's responsibility;
@@ -8607,6 +8610,13 @@ var CompanionSupervisor = class {
       "companion: stopped agent (unassigned)"
     );
   }
+  // CT833: is Claude Code on this machine right now? The ONE signal both the
+  // heartbeat manifest and the dispatcher's adapter registry read, so what the
+  // device advertises and what it can actually select can't disagree. Live (the
+  // per-beat re-probe), falling back to the boot probe until the first one lands.
+  claudeCodePresent() {
+    return this.harnessSignals?.claudeOnPath ?? this.claudeCode;
+  }
   buildDispatcher(ctx) {
     if (this.dispatcherFactory) return this.dispatcherFactory(ctx);
     return new Dispatcher({
@@ -8624,6 +8634,10 @@ var CompanionSupervisor = class {
       }),
       runConfig: ctx.runConfig,
       log: this.log,
+      // CT833: register the claude-code adapter only when `claude` is actually on
+      // this machine — read per turn (not captured here), so a harness installed
+      // after boot works on the next turn exactly as it appears on the next beat.
+      claudeCodeAvailable: () => this.claudeCodePresent(),
       // CT270: the opencode server URL (operator-configured), when this device
       // offers the opencode runtime. Threaded so an opencode turn selects the
       // opencode adapter; unset leaves the device claude-code-only.

package/dist/runtime.js

@@ -6984,7 +6984,10 @@ ${reason}`,
       ...this.opts.local.claudeCode ? { claudeCode: this.opts.local.claudeCode } : {}
     });
     const onWarn = (msg, meta) => turnLog.warn(meta ?? {}, msg);
-    const adapters = [createClaudeCodeAdapter({ queryFn: this.opts.queryFn, onWarn })];
+    const adapters = [];
+    if (this.opts.claudeCodeAvailable?.() ?? true) {
+      adapters.push(createClaudeCodeAdapter({ queryFn: this.opts.queryFn, onWarn }));
+    }
     if (this.opts.opencodeServerUrl) {
       adapters.push(createOpencodeAdapter({ serverUrl: this.opts.opencodeServerUrl, onWarn }));
     }
@@ -8037,7 +8040,7 @@ var CompanionSupervisor = class {
           // until the first re-probe lands. Same exit-0 `claude --version` signal
           // either way, so the manifest's claude-code advertising is unchanged in
           // meaning — just refreshed on the beat instead of frozen at boot.
-          claudeCode: this.harnessSignals?.claudeOnPath ?? this.claudeCode,
+          claudeCode: this.claudeCodePresent(),
           opencode: !!this.config.opencode?.serverUrl,
           // CT481: advertise codex when the operator enabled it (config-gated,
           // like opencode — the CLI's presence is the operator's responsibility;
@@ -8260,6 +8263,13 @@ var CompanionSupervisor = class {
       "companion: stopped agent (unassigned)"
     );
   }
+  // CT833: is Claude Code on this machine right now? The ONE signal both the
+  // heartbeat manifest and the dispatcher's adapter registry read, so what the
+  // device advertises and what it can actually select can't disagree. Live (the
+  // per-beat re-probe), falling back to the boot probe until the first one lands.
+  claudeCodePresent() {
+    return this.harnessSignals?.claudeOnPath ?? this.claudeCode;
+  }
   buildDispatcher(ctx) {
     if (this.dispatcherFactory) return this.dispatcherFactory(ctx);
     return new Dispatcher({
@@ -8277,6 +8287,10 @@ var CompanionSupervisor = class {
       }),
       runConfig: ctx.runConfig,
       log: this.log,
+      // CT833: register the claude-code adapter only when `claude` is actually on
+      // this machine — read per turn (not captured here), so a harness installed
+      // after boot works on the next turn exactly as it appears on the next beat.
+      claudeCodeAvailable: () => this.claudeCodePresent(),
       // CT270: the opencode server URL (operator-configured), when this device
       // offers the opencode runtime. Threaded so an opencode turn selects the
       // opencode adapter; unset leaves the device claude-code-only.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cabane/companion",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "type": "module",
   "description": "The Cabane Companion (headless): connect a coding 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",