relay-companion 0.1.90 → 0.1.92

package/overlay/inbox.html

@@ -251,11 +251,11 @@
 
   /* subject: single-line serif, right-edge fade mask */
   .rk-subject {
-    font-family:var(--serif); font-size:15px; line-height:1.3; color:var(--muted); font-weight:400;
+    font-family:var(--serif); font-size:15px; line-height:1.32; color:var(--muted); font-weight:400;
     margin-top:5px;
     /* Two full lines with an ellipsis: titles must be scannable when choosing
        which relay to open — the old right-edge fade cut them after a few words. */
-    overflow:hidden; display:-webkit-box; -webkit-line-clamp:2; -webkit-box-orient:vertical;
+    overflow:hidden; display:-webkit-box; -webkit-line-clamp:3; -webkit-box-orient:vertical;
     overflow-wrap:anywhere;
     transition:color .28s var(--settle);
   }
@@ -743,6 +743,8 @@
   .sv-err { margin-top:8px; padding:0 16px; }
   .sv-note { padding:10px 16px 0; font-size:11.5px; color:#1a7f37; line-height:1.4; }
   .sv-version { padding:20px 16px 12px; font-family:var(--mono); font-size:10.5px; color:var(--muted-3); }
+  .sv-update { display:flex; flex-direction:column; gap:8px; align-items:flex-start; }
+  .sv-update-btn { width:auto; padding:7px 12px; border-radius:8px; font-family:var(--sans); font-size:12px; }
   /* signed-out call-to-action on the Relays empty state — quiet filled pill (th-count language) */
   .sv-signin-banner {
     appearance:none; border:0; cursor:pointer; margin-top:2px;
@@ -1697,6 +1699,7 @@
         </span>
         <span class="th-title">${esc(t.latest.title)}</span>
         ${tMenu}
+        ${newestInbound ? `<div class="row-err${rowNotes.get(newestInbound.id)?.cls === "ok" ? " ok" : ""}" data-err="${esc(newestInbound.id)}" data-stop="1">${esc(rowNotes.get(newestInbound.id)?.text || "")}</div>` : ""}
       </div>`;
     }).join("");
     prevRelayIds = new Set(allRows.map((r) => r.id));
@@ -1792,11 +1795,11 @@
     const subject = relaySubject(r);
     const sender = relaySender(r);
     const actions = relayActionsHtml(r);
-    // result / task_completed / plain message carry a body preview beneath the subject.
-    // (human_question's body IS the subject, so no duplicate preview there.)
-    const body = r.bodyMarkdown || r.body || "";
-    const preview = kind === "human_question" ? "" : bodyPreview(body, subject, 110);
-    const previewHtml = preview ? `<div class="rk-preview">${esc(preview)}</div>` : "";
+    // Cards show the TITLE ONLY. The old truncated body preview leaked the
+    // agent-oriented detail layer — often unreadable out of context — and cost a
+    // third of the row to say little. Titles now carry what/why/ask (see
+    // relay_send's title guidance), so the detail waits for Preview or an open.
+    const previewHtml = "";
     const canDelete = kind === "plain_relay" || kind === "human_question" || kind === "task_completed" || kind === "task_cancelled" || kind === "task_failed";
     const deleteButton = canDelete ? `<button class="row-delete" type="button" data-delete="${esc(r.id)}" data-stop="1" aria-label="Move to Recently Deleted" title="Move to Recently Deleted"><svg width="13" height="13" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" stroke-linejoin="round"><path d="M4 7h16M9 7V4h6v3M7 7l1 13h8l1-13M10 11v5M14 11v5"/></svg></button>` : "";
     const expanded = r.id === expandedRelayId;
@@ -2942,6 +2945,7 @@
   // relays plus the live Sent list. Local data only — the pill shows the
   // user's own exchanges; the API's /v1/threads serves web and agents.
   let threadDetailId = null; // threadId while a thread's history is open
+  let threadDetailScrolledFor = null; // thread already auto-scrolled to newest (reset on leave)
   let threadDetailPartyHint = ""; // who it's with, for the header while messages load
   function threadMessages() {
     const msgs = [];
@@ -3033,7 +3037,19 @@
     const threadActions = threadOpenTarget
       ? openActionsHtml(threadOpenTarget.id, { thread: true, previewable: Boolean(newestInbound) })
       : "";
-    thHistoryEl.innerHTML = threadActions + thread.msgs.map((m) => `
+    // Open-status notes ("Handed to your current chat…" / "✓ Delivered" /
+    // open errors) must render HERE too: users who live in the thread view
+    // click these buttons and previously got zero feedback — a working
+    // hand-off was indistinguishable from a dead one (Sven, 2026-08-05,
+    // twice). Rendered from rowNotes so every payload-push rebuild keeps it.
+    const threadNote = threadOpenTarget
+      ? `<div class="row-err${rowNotes.get(threadOpenTarget.id)?.cls === "ok" ? " ok" : ""}" data-err="${esc(threadOpenTarget.id)}" data-stop="1">${esc(rowNotes.get(threadOpenTarget.id)?.text || "")}</div>`
+      : "";
+    // Chat-shaped, like every messaging app (and Claude itself — Sven's field
+    // note): messages read oldest -> newest downward, the open actions sit at
+    // the BOTTOM next to the newest message, and entering the thread lands you
+    // at the newest message, not the stalest.
+    thHistoryEl.innerHTML = thread.msgs.map((m) => `
       <button class="th-msg${m.unread ? " unread" : ""}" type="button" data-msg="${esc(m.id)}" data-dir="${m.direction}">
         <span class="th-msg-top">
           <span class="th-dir${m.direction === "out" ? " out" : ""}">${m.direction === "out" ? "←" : "→"}</span>
@@ -3041,7 +3057,13 @@
           <span class="th-time">${esc(timeAgo(m.at))}</span>
         </span>
         <span class="th-msg-title">${esc(m.title)}</span>
-      </button>`).join("");
+      </button>`).join("") + threadActions + threadNote;
+    // Land at the newest message when ENTERING the thread; rebuilds of the same
+    // open thread (payload pushes) keep the user's scroll position untouched.
+    if (threadDetailScrolledFor !== thread.threadId) {
+      threadDetailScrolledFor = thread.threadId;
+      requestAnimationFrame(() => { scrollEl.scrollTop = scrollEl.scrollHeight; });
+    }
     for (const el of thHistoryEl.querySelectorAll(".th-msg")) {
       el.addEventListener("click", () => {
         const id = el.getAttribute("data-msg");
@@ -3057,6 +3079,7 @@
   }
   thBackEl.addEventListener("click", () => {
     threadDetailId = null;
+    threadDetailScrolledFor = null;
     activeView = "relays";
     syncTabs();
     applyView();
@@ -3134,11 +3157,28 @@
     if (svPairOpen) html += svPairRowHtml();
     if (svNote) html += `<div class="sv-note">${esc(svNote)}</div>`;
     html += `<div class="row-err sv-err" id="svErr">${esc(svError)}</div>`;
-    html += `<div class="sv-version">${esc(info.version ? `Relay ${info.version}` : "Relay")}</div>`;
+    // Version line doubles as the manual update backstop: if the auto-updater
+    // has not refreshed this machine, say so here and make it one click.
+    if (info.updateAvailable) {
+      html += `<div class="sv-version sv-update">
+        <span>Relay ${esc(info.version || "")} · update ${esc(info.updateAvailable)} ready</span>
+        <button class="oa-item oa-primary sv-update-btn" type="button" id="svUpdate" ${info.updating ? "disabled" : ""}>${info.updating ? "Updating…" : "Update and Restart"}</button>
+      </div>`;
+    } else {
+      html += `<div class="sv-version">${esc(info.version ? `Relay ${info.version}` : "Relay")}</div>`;
+    }
     settingsViewEl.innerHTML = html;
     wireSettings();
   }
   function wireSettings() {
+    const upd = document.getElementById("svUpdate");
+    if (upd) {
+      upd.addEventListener("click", async () => {
+        upd.disabled = true;
+        upd.textContent = "Updating…";
+        try { await window.relay.updateNow(); } catch {}
+      });
+    }
     for (const z of settingsViewEl.querySelectorAll('[data-stop="1"]')) {
       z.addEventListener("click", (e) => e.stopPropagation());
     }

package/overlay/main.cjs

@@ -451,6 +451,10 @@ function accountInfo() {
     email: user.email || "",
     deviceName: String(cfg.deviceName || "").trim() || os.hostname(),
     version: pillVersion(),
+    // Surfaced in the Settings card so a stale machine is visible in the app,
+    // not only in the tray menu.
+    updateAvailable: availableUpdate || "",
+    updating: updateInFlight,
     setupPath: "/app/setup",
   };
 }
@@ -3093,6 +3097,47 @@ function quitRelayCompletely() {
   } catch {}
 }
 
+
+// ---- update availability (the manual backstop) -----------------------------
+// The daemon self-updates, but an update can be pending for a while (the
+// restart cooldown), or fail quietly, and then a machine silently runs old
+// code — exactly what happened to a Windows user who sat nine versions behind.
+// The pill therefore checks the registry itself and, when a newer version
+// exists, surfaces it where a person will actually see it: the tray menu and
+// the Settings card, each offering a one-click "restart now" that runs the
+// same installer with manual intent (which bypasses the cooldown).
+let availableUpdate = null; // version string when newer than what we run
+let updateInFlight = false;
+async function checkForUpdate() {
+  try {
+    const mod = await import(pathToFileURL(path.join(__dirname, "..", "src", "auto-update.js")).href);
+    const latest = await mod.fetchLatestVersion({});
+    const current = pillVersion();
+    availableUpdate = latest && mod.isNewerVersion(latest, current) ? latest : null;
+    if (availableUpdate) syncTray();
+  } catch {}
+}
+function runUpdateNow() {
+  if (updateInFlight) return;
+  updateInFlight = true;
+  try {
+    const child = spawn(process.execPath, [RELAY_CLI, "update"], {
+      detached: true,
+      stdio: "ignore",
+      env: { ...process.env, ELECTRON_RUN_AS_NODE: "1" },
+    });
+    child.on("error", (error) => {
+      updateInFlight = false;
+      console.error(`[overlay] ${new Date().toISOString()} manual update failed:`, error && error.message);
+    });
+    child.unref();
+  } catch (error) {
+    updateInFlight = false;
+    console.error(`[overlay] ${new Date().toISOString()} manual update spawn failed:`, error && error.message);
+  }
+  if (win && !win.isDestroyed()) win.webContents.send("updateStarted");
+}
+
 function createTray() {
   const icon = createTrayIcon();
   if (!icon || icon.isEmpty()) {
@@ -3123,6 +3168,12 @@ function createTray() {
           { label: pillIsOnScreen() ? "Hide Relay" : "Show Relay", click: toggleFromTray },
           ...previewItem,
           { type: "separator" },
+          // Mirrors what good menu-bar apps do: state the version you are on,
+          // and when a newer one is waiting make restarting a single click.
+          ...(availableUpdate
+            ? [{ label: `Update ready (${availableUpdate}) — restart now?`, click: runUpdateNow }]
+            : [{ label: `Relay ${pillVersion()}`, enabled: false }]),
+          { type: "separator" },
           { label: "Quit Relay", click: quitRelayCompletely },
         ]),
       );
@@ -3242,6 +3293,10 @@ ipcMain.handle("relay:contactsSearch", (_e, q) => groupCall((c) => c.searchConta
 ipcMain.handle("relay:accountInfo", () => accountInfo());
 ipcMain.handle("relay:pairWithCode", (_e, input) => pairWithCode(input));
 ipcMain.handle("relay:signOut", () => signOutAccount());
+ipcMain.handle("relay:updateNow", () => {
+  runUpdateNow();
+  return { ok: true };
+});
 
 // The overlay is normally focusable:false so it never steals keyboard focus from
 // Claude/Codex. Text fields (the contact form, quick reply) need focus, so the renderer
@@ -3434,6 +3489,10 @@ if (!gotSingleInstanceLock) {
     if (process.platform === "darwin" && app.dock) app.dock.hide(); // accessory: no dock icon, no NC banners
     createWindow();
     createTray();
+    // Update availability: one check after boot, then hourly. Cheap (a dist-tags
+    // GET) and it only ever surfaces UI — the daemon still owns actual updating.
+    setTimeout(() => checkForUpdate(), 20000).unref?.();
+    setInterval(() => checkForUpdate(), 60 * 60 * 1000).unref?.();
     installActiveSpaceWatcher();
     installPowerAttentionLifecycle();
     // Display topology changes are the remaining event that can strand the

package/overlay/preload.cjs

@@ -68,6 +68,8 @@ contextBridge.exposeInMainWorld("relay", {
   accountInfo: () => ipcRenderer.invoke("relay:accountInfo"),
   pairWithCode: (input) => ipcRenderer.invoke("relay:pairWithCode", input),
   signOut: () => ipcRenderer.invoke("relay:signOut"),
+  // Manual update backstop, when the auto-updater has not refreshed this machine.
+  updateNow: () => ipcRenderer.invoke("relay:updateNow"),
 
 
   // window plumbing

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "relay-companion",
-  "version": "0.1.90",
+  "version": "0.1.92",
   "description": "Relay companion for ordinary messages, with dormant coordination features available only by explicit opt-in.",
   "type": "module",
   "bin": {

package/src/mcp.js

@@ -38,12 +38,12 @@ export const TOOLS = [
         title: {
           type: "string",
           description:
-            "The concise, high-level human-facing takeaway. This is shown first and most prominently, so keep it to one clear phrase or sentence.",
+            "The human-readable layer of the relay, and the ONLY thing shown on the recipient's card — write it to carry real information, not to name a topic. In as few words as it honestly takes (aim ~8-20 words, hard stop around 140 characters), answer: what is this, why does this person care, is anything expected of them, and by when. Value-centric and human, never a detail dump: 'Postmark account still pending approval — DNS is ready, nothing needed from you until they reply' beats 'Postmark update'. State the ask explicitly when there is one, and say so plainly when there is not. The recipient reads this alone, decides whether to act, and only then opens the relay for the full detail in bodyMarkdown — so a title that merely labels the subject forces a pointless open.",
         },
         bodyMarkdown: {
           type: "string",
           description:
-            "The complete human-facing detail you formulate from the sender's request and relevant context. Use readable Markdown (short paragraphs, headings, bullets, tables, or code where useful) and do not merely repeat the title. This is the message body, not a private recipient-agent briefing.",
+            "The high-detail layer, read AFTER the title earns the open. Formulate the complete human-facing detail from the sender's request and relevant context in readable Markdown (short paragraphs, headings, bullets, tables, or code where useful). Never merely repeat the title; the title already carried the what/why/ask, so this is the substance behind it. This is the message body, not a private recipient-agent briefing.",
         },
         userInstructions: { type: "string", description: "Optional private instruction for how the recipient's agent should handle a handoff." },
         targetSurfaces: {