@cabane/companion 0.6.138 → 0.6.140

package/README.md

@@ -212,7 +212,7 @@ Run `cabane-companion start --foreground`. Configure the supervisor itself for r
 
 There's a deliberate split. **What the agent is** — its mode, MCP servers, model, reasoning, and charter — is configured in **Cabane** (Workspace settings → Agents) and delivered to the Companion per turn, so an edit in Cabane lands on the next turn with **no restart**. The Companion holds only the bits that can't travel from a server: the **working directory** an agent runs in (a path on _this_ machine) and your **secrets**.
 
-An agent can reach MCP servers two ways, and they don't overlap. **The agent's own MCP servers** are part of what the agent is: set on its Agents page, they go with it into every room. **Connections** belong to a person instead: you add one under Workspace settings → Connections (an endpoint and a pasted key, stored encrypted in Cabane), then bring it into a room from the room's menu and pick which agents there may use it. On each turn in that room, Cabane attaches the room's connections for that agent and sends the key with the turn, into the harness's environment and never onto its command line. Nothing is configured on this machine. Replacing, disconnecting or deleting a key takes effect on the agent's next turn, and nothing is revoked at the service itself.
+An agent can reach MCP servers two ways, and they don't overlap. **The agent's own MCP servers** are part of what the agent is: set on its Agents page, they go with it into every room. **Connections** belong to a person instead: you add one under Workspace settings → Connections (an endpoint and a pasted key, stored encrypted in Cabane), then add it to a room from the room's menu and pick which agents there may use it. On each turn in that room, Cabane attaches the room's connections for that agent and sends the key with the turn, into the harness's environment and never onto its command line. Nothing is configured on this machine. Replacing, disconnecting or deleting a key takes effect on the agent's next turn, and nothing is revoked at the service itself.
 
 ### Agent modes (set in Cabane)
 

package/dist/cli.js

@@ -12517,9 +12517,18 @@ async function postJson(baseUrl, path, body) {
 }
 function requestEnrollmentCode(baseUrl, opts = {}) {
   return postJson(baseUrl, "/api/device-enrollment/code", {
-    ...opts.label ? { label: opts.label } : {}
+    ...opts.label ? { label: opts.label } : {},
+    ...hostFacts()
   });
 }
+function hostFacts() {
+  const nodeMajor = Number.parseInt(process.versions.node.split(".")[0] ?? "", 10);
+  return {
+    platform: process.platform,
+    arch: process.arch,
+    ...Number.isInteger(nodeMajor) ? { nodeMajor } : {}
+  };
+}
 function deviceLabelFromHostname(hostname5) {
   const trimmed = hostname5.trim().replace(/\.local$/i, "");
   if (trimmed.length === 0) return void 0;

package/dist/pairing-config.js

@@ -453,9 +453,18 @@ async function postJson(baseUrl, path, body) {
 }
 function requestEnrollmentCode(baseUrl, opts = {}) {
   return postJson(baseUrl, "/api/device-enrollment/code", {
-    ...opts.label ? { label: opts.label } : {}
+    ...opts.label ? { label: opts.label } : {},
+    ...hostFacts()
   });
 }
+function hostFacts() {
+  const nodeMajor = Number.parseInt(process.versions.node.split(".")[0] ?? "", 10);
+  return {
+    platform: process.platform,
+    arch: process.arch,
+    ...Number.isInteger(nodeMajor) ? { nodeMajor } : {}
+  };
+}
 function pollOnce(baseUrl, deviceCode) {
   return postJson(baseUrl, "/api/device-enrollment/poll", { deviceCode });
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cabane/companion",
-  "version": "0.6.138",
+  "version": "0.6.140",
   "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",