relay-companion 0.1.82 → 0.1.83

package/overlay/inbox.html

@@ -3100,7 +3100,7 @@
     if (info.awaitingTurn) {
       // Persistent until delivery / the auto-fresh hop — never a silent limbo.
       if (injectedNoteTimers.has(id)) { clearTimeout(injectedNoteTimers.get(id)); injectedNoteTimers.delete(id); }
-      setRowNote(id, "Handed to your current Claude chat…", "ok");
+      setRowNote(id, "Handed to your current Claude chat — lands when it next takes a turn. If it\u2019s idle: type anything there, or use Open in New Chat for instant.", "ok");
       return;
     }
     const hostName = info.host === "codex" ? "Codex" : "Claude";

package/overlay/main.cjs

@@ -1897,18 +1897,20 @@ async function openPacket(packetId, { sent = false, fresh = false } = {}) {
 // injection for an idle session sat invisible for minutes and the click read as
 // completely dead; a waiting state that never lies beats a success toast.
 //
-// The GRACE WINDOW closes the remaining gap. Nothing outside a session can make
-// it take a turn (verified against the platform docs: deep links only pre-fill
-// NEW sessions; no external submit API exists), so an idle chat cannot be woken
-// — but the user must still get the relay QUICKLY. A busy chat ingests at a
-// tool boundary within seconds; if the grace window passes unconsumed, the
-// target is idle: reclaim the injection (same rename-first consume-once
-// discipline as the hook, so a racing delivery always wins) and open the relay
-// in a fresh chat instead. Every click produces a visible result in seconds.
+// Nothing outside a session can make it take a turn (verified against the
+// platform docs: deep links only pre-fill NEW sessions; no external submit API
+// exists), so an idle chat cannot be woken — the honest waiting/delivered
+// states are the truth until the Relay channel plugin (the platform's supported
+// push-into-a-running-session mechanism) lands. The 0.1.82 grace hop — reclaim
+// after 6s and open a fresh chat — is now OFF by default: the same-evening
+// field verdict was that silently converting "current chat" into "new chat"
+// betrays the button. The user chose current; Open in New Chat sits one row
+// below for when they want instant. RELAY_CURRENT_CHAT_GRACE_MS > 0 re-enables
+// the hop for anyone who prefers motion over fidelity.
 const injectionWatchers = new Map(); // packetId -> interval
 const AUTO_FRESH_GRACE_MS = (() => {
   const raw = Number(process.env.RELAY_CURRENT_CHAT_GRACE_MS);
-  return Number.isFinite(raw) && raw >= 0 ? raw : 6000; // 0 disables auto-fresh
+  return Number.isFinite(raw) && raw > 0 ? raw : 0; // 0 (default): never hop
 })();
 function reclaimInjection(stagedPath) {
   const claimed = `${stagedPath}.${process.pid}.${Date.now()}.autofresh`;

package/package.json

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