relay-companion 0.1.477 → 0.1.478

package/bootstrap/relay-background-install.cjs

@@ -6,6 +6,7 @@ const path = require("node:path");
 const { spawn } = require("node:child_process");
 
 const STATUS_VERSION = 1;
+const RUNNING_STATUSES = ["starting", "installing", "waiting_authorization"];
 
 function statusPath({ homeDir = os.homedir(), env = process.env } = {}) {
   return env.RELAY_BACKGROUND_INSTALL_STATUS || path.join(env.RELAY_CONFIG_DIR || path.join(homeDir, ".relay"), "companion-install.json");
@@ -42,7 +43,7 @@ function processAlive(pid) {
 
 function installationStatus(options = {}) {
   const state = readStatus(options);
-  if (["starting", "installing"].includes(state.status) && !processAlive(state.pid)) {
+  if (RUNNING_STATUSES.includes(state.status) && !processAlive(state.pid)) {
     return { ...state, status: "failed", reason: "installer_stopped", finishedAt: new Date().toISOString() };
   }
   return state;
@@ -57,7 +58,7 @@ function startBackgroundInstall({
 } = {}) {
   const paths = { homeDir, env };
   const existing = installationStatus(paths);
-  if (["starting", "installing"].includes(existing.status)) {
+  if (RUNNING_STATUSES.includes(existing.status)) {
     return { ok: true, started: false, alreadyRunning: true, status: existing };
   }
   fs.mkdirSync(path.dirname(statusPath(paths)), { recursive: true, mode: 0o700 });
@@ -86,6 +87,37 @@ function option(argv, name) {
   return index >= 0 ? argv[index + 1] : "";
 }
 
+// Download and verify first, but never activate or enroll Companion until the
+// helper has verified the browser grant and finished its atomic handoff. Only
+// inspect file existence here; account/consent checks remain in adoption.
+async function waitForAgentAuthorization({
+  env = process.env,
+  homeDir = os.homedir(),
+  exists = fs.existsSync,
+  now = Date.now,
+  sleep = (ms) => new Promise((resolve) => setTimeout(resolve, ms)),
+  timeoutMs = 30 * 60 * 1000,
+  intervalMs = 1000,
+} = {}) {
+  const root = env.RELAY_CONFIG_DIR || path.join(homeDir, ".relay");
+  const credential = env.RELAY_AGENT_CONFIG || path.join(root, "agent-protocol.json");
+  const pending = env.RELAY_AGENT_AUTHORIZATION || path.join(root, "agent-authorization.json");
+  const deadline = now() + timeoutMs;
+  const options = { env, homeDir };
+  let waiting = false;
+  while (exists(pending) || !exists(credential)) {
+    if (!waiting) {
+      atomicWriteJson(statusPath(options), { ...readStatus(options), status: "waiting_authorization" });
+      waiting = true;
+    }
+    if (now() >= deadline) {
+      throw new Error("Companion is downloaded but browser approval is not complete. Finish the Relay connection, then retry background-install.");
+    }
+    await sleep(Math.min(intervalMs, deadline - now()));
+  }
+  if (waiting) atomicWriteJson(statusPath(options), { ...readStatus(options), status: "installing" });
+}
+
 async function runWorker(argv = process.argv.slice(2), { spawnImpl = spawn, env = process.env } = {}) {
   const entry = path.resolve(option(argv, "--entry") || path.resolve(__dirname, "relay-setup.cjs"));
   if (path.basename(entry) !== "relay-setup.cjs" || !fs.existsSync(entry)) throw new Error("Relay's background installer entry is invalid.");
@@ -146,4 +178,5 @@ module.exports = {
   runWorker,
   startBackgroundInstall,
   statusPath,
+  waitForAgentAuthorization,
 };

package/bootstrap/relay-setup.cjs

@@ -1377,6 +1377,9 @@ async function setup(argv = []) {
     // archives instead of leaking hundreds of megabytes per interrupted attempt.
     removeAbandonedRuntimeDownloads(layout.releasesDir);
     const runtime = await stageVerifiedRuntime({ version, platformKey, destination: layout.releaseRoot });
+    if (setupCompatibilityArgs.includes("--agent-protocol") && process.env.RELAY_BACKGROUND_INSTALL_WORKER === "1") {
+      await require("./relay-background-install.cjs").waitForAgentAuthorization();
+    }
     const activated = await activateRuntime(layout, runtime, version, { setupCompatibilityArgs });
     if (setupCompatibilityArgs.includes("--code")) {
       console.log(`Relay ${version} is installed and paired. The Relay pill is open.`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "relay-companion",
-  "version": "0.1.477",
+  "version": "0.1.478",
   "description": "Install Relay for Claude Code, Cowork, and Codex, then sign in from the Relay pill.",
   "homepage": "https://sendrelays.com/get-started",
   "repository": {

package/skill/manifest.json

@@ -1,13 +1,13 @@
 {
   "schemaVersion": 1,
   "name": "relay",
-  "version": "1.1.7",
+  "version": "1.1.8",
   "consentVersion": 2,
-  "baseUrl": "https://sendrelays.com/skills/relay/v1.1.7",
+  "baseUrl": "https://sendrelays.com/skills/relay/v1.1.8",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "ad86c448a5296a60ec1e4f974d941e6374f1863141d6b2dfbce11edca821cefa"
+      "sha256": "ea97b5ec82fd7545a6c851829658e41ab02525cfb06d03d5f1ad25c1aaafcf5b"
     },
     {
       "path": "agents/openai.yaml",

package/skill/relay/SKILL.md

@@ -50,14 +50,22 @@ from the pasted `/i/:token/agent` Relay invite. Never ask the person to paste a
 password, Google credential, one-time code, or Relay access token into chat. Use
 the browser approval URL for identity and permission. Start with the pinned
 protocol helper in this conversation; no skill discovery or agent restart is
-needed. After connect-finish succeeds, follow the invitation's host activation
-procedure: install the skill, attempt supported discovery refresh in the running
-Claude Code or Codex host, and verify the scope of activation. Start
-background-install on a supported desktop. It adopts this same
-approved account without another login. Skip desktop installation on a
-hosted/headless machine. Keep the Companion
-installation non-blocking; continue as soon as the HTTPS protocol is ready and
-report a later installation failure as a recoverable app-install issue.
+needed. Run connect-start and open its approval URL in the person's usual
+browser. With setup permission already given, start the same pinned package's
+background-install on a supported desktop before yielding to wait for browser
+approval. It downloads and verifies Companion while the person approves; do not
+postpone it until authorization finishes. The installer waits for the verified
+connection before adopting that account and activating Companion, without
+another login. Skip desktop installation on a hosted/headless machine.
+
+After browser approval, run connect-finish, then follow the invitation's host
+activation procedure: install the skill, attempt supported discovery refresh in
+the running Claude Code or Codex host, and verify the scope of activation. Keep
+Companion installation non-blocking; continue as soon as the HTTPS protocol is
+ready. If the approval link expires, renew browser approval without restarting
+a running installer. Check background-status; retry installation only if it
+failed or stopped, and report installation failures separately from the working
+connection.
 
 Create the authorization with `POST /v1/agent/authorizations` and consume it
 after browser approval with `POST /v1/agent/authorizations/:id/consume`. Treat