patchcord 0.5.62 → 0.5.64

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchcord",
-  "version": "0.5.62",
+  "version": "0.5.64",
   "description": "Cross-machine agent messaging for Claude Code and Codex",
   "author": "ppravdin",
   "license": "MIT",

package/scripts/subscribe.mjs

@@ -221,6 +221,25 @@ async function run() {
     process.exit(0);
   });
 
+  // Exit when our stdout consumer (Monitor) dies. Node ignores SIGPIPE by
+  // default, so the EPIPE error surfaces on the stream instead. Without this
+  // the process orphans after the session ends and the pidfile guard blocks
+  // the next session from starting a fresh listener.
+  process.stdout.on("error", (err) => {
+    if (err.code === "EPIPE") {
+      cleanup();
+      process.exit(0);
+    }
+  });
+
+  // Keepalive: write a line every 30 s so EPIPE is detected promptly even
+  // when no messages arrive. The Monitor command pipes through
+  // `grep --line-buffered '^PATCHCORD:'` which drops these lines silently.
+  const _keepaliveTimer = setInterval(() => {
+    try { process.stdout.write("HEARTBEAT\n"); } catch (_) {}
+  }, 30_000);
+  process.on("exit", () => clearInterval(_keepaliveTimer));
+
   logErr(`subscribe: agent=${ticket.agent_id} namespaces=${ticket.namespace_ids.join(",")}`);
 
   let backoffIdx = 0;
@@ -432,8 +451,10 @@ function runOnce(ticket, baseUrl, token, refreshTicket) {
           return;
         }
         // Successful subscribe ack — log once for confirmation, then quiet.
+        // Replace Supabase's "Subscribed to PostgreSQL" with a user-facing label.
         if (status === "ok" && message) {
-          logErr(`subscribe: system ok on ${frame.topic}: ${message}`);
+          const displayMsg = message.replace(/PostgreSQL/g, "Patchcord");
+          logErr(`subscribe: system ok on ${frame.topic}: ${displayMsg}`);
         }
         return;
       }

package/skills/subscribe/SKILL.md

@@ -20,10 +20,12 @@ User invoked /patchcord:subscribe — do NOT substitute `wait_for_message()`. Sp
      description: "patchcord realtime listener",
      persistent: true,
      timeout_ms: 3600000,
-     command: "exec patchcord subscribe"
+     command: "patchcord subscribe | grep --line-buffered '^PATCHCORD:'; exit ${PIPESTATUS[0]}"
    )
    ```
 
+   The grep filter drops internal `HEARTBEAT` keepalive lines (written every 30 s to detect a dead pipe) — only `PATCHCORD:` lines fire notifications. `${PIPESTATUS[0]}` preserves subscribe's exit code through the pipe.
+
    `subscribe.mjs` handles its own pidfile guard — if another listener is already active for this agent it exits with code 2 and stderr `already running (pid N)`. Monitor catches the stream-end event; read the output file and report.
 
 3. **Tell the user one line:** *"Patchcord listener active — I'll pick up new messages as they arrive."*
@@ -57,4 +59,4 @@ Report the cause in one sentence. STOP.
 
 **Forbidden on failure:** no `pgrep`/`ps`/`kill`/`pkill`/`killall`, no pidfile writes, no respawning. The script manages pidfile cleanup itself; respawning will not fix a config problem.
 
-Clean exit (code 0) with no error line = the user closed the session or killed the process. Nothing to do.
+No matching error pattern = the listener exited cleanly (session ended, user killed it, or EPIPE detected). Nothing to do.