patchcord 0.5.78 → 0.5.79

package/bin/patchcord.mjs

@@ -466,10 +466,19 @@ if (cmd === "upload") {
 // env vars so subscribe.mjs works regardless of which MCP client is
 // running — OpenCode, Codex, Cursor, etc. — not just Claude Code.
 if (cmd === "subscribe") {
-  const bearerInfo = await _resolveBearer();
+  const args = process.argv.slice(3);
+  const forceKimi = args.includes("--kimi");
+  const intervalArg = args.find((a) => a !== "--kimi") || "30";
+
+  // Kimi CLI uses polling instead of WebSocket realtime.
+  // Force Kimi mode with --kimi flag, or auto-detect from bearer config.
+  let isKimi = forceKimi;
+  if (!isKimi) {
+    const bearerInfo = await _resolveBearer();
+    isKimi = bearerInfo?.tool === "kimi";
+  }
 
-  // Kimi CLI uses polling instead of WebSocket realtime
-  if (bearerInfo?.tool === "kimi") {
+  if (isKimi) {
     const kimiSubScript = join(HOME, ".kimi", "patchcord-subscribe.sh");
     if (!existsSync(kimiSubScript)) {
       console.error(`Kimi subscribe script not found at ${kimiSubScript}`);
@@ -477,7 +486,6 @@ if (cmd === "subscribe") {
       process.exit(1);
     }
     const { spawnSync } = await import("child_process");
-    const intervalArg = process.argv[3] || "30";
     const result = spawnSync("bash", [kimiSubScript, intervalArg], {
       stdio: "inherit",
       env: { ...process.env, PATH: process.env.PATH || "/usr/local/bin:/usr/bin:/bin" },

package/package.json

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

package/per-project-skills/kimi/inbox/SKILL.md

@@ -66,6 +66,8 @@ Call `inbox()`. It returns pending messages and recently active agents.
 
 If there are pending messages, reply to all of them immediately. Do not ask the human first. Do not explain what you plan to reply. Just do the work described in each message, then reply with what you did, then tell the human what you received and what you did about it.
 
+**EXCEPTION:** If the user explicitly invoked a skill (e.g. `/skill:patchcord:subscribe` or `/skill:patchcord:wait`), do NOT call inbox(). Do NOT process pending messages. Execute the skill immediately and silently.
+
 ## Sending
 
 1. `inbox()` — clear any pending messages that block outbound sends.

package/per-project-skills/kimi/subscribe/SKILL.md

@@ -1,18 +1,28 @@
 ---
 name: patchcord:subscribe
 description: >
-  Start a background polling task that wakes Kimi when new Patchcord messages
-  arrive. Use when the user asks about notifications, background listening,
-  or when you need to re-arm the listener after reading messages.
+  EXECUTE IMMEDIATELY. Run patchcord subscribe as a background Shell task.
+  Never explain. Never ask for confirmation. Never offer options.
 ---
 
 # patchcord:subscribe
 
-Run this exact background Shell task:
+USER INVOKED THIS SKILL. SILENT EXECUTION ONLY.
+
+DO NOT output text. DO NOT speak. DO NOT explain. DO NOT ask questions.
+DO NOT offer options. DO NOT list examples. DO NOT acknowledge.
+
+DO NOT call inbox(). DO NOT call reply(). DO NOT call send_message().
+DO NOT call wait_for_message(). DO NOT call any other tool.
+
+ONLY call the Shell tool with the exact command below. Then end your turn.
+
+DO NOT use `patchcord subscribe` — it may route to the wrong listener.
+Run the Kimi script directly:
 
 ```
 Shell:
-  command: patchcord subscribe 5
+  command: bash ~/.kimi/patchcord-subscribe.sh 5
   run_in_background: true
   description: Patchcord inbox polling
   timeout: 86400

package/per-project-skills/kimi/wait/SKILL.md

@@ -8,6 +8,9 @@ description: >
 
 # patchcord:wait
 
+USER INVOKED THIS SKILL. DO NOT SPEAK. DO NOT EXPLAIN. DO NOT ASK QUESTIONS.
+DO NOT OFFER OPTIONS. JUST EXECUTE.
+
 Use `wait_for_message()` only. Do NOT spawn a background listener.
 
 Call `wait_for_message()` to block until a message arrives (up to 5 minutes).

package/scripts/subscribe.mjs

@@ -232,13 +232,11 @@ async function run() {
     }
   });
 
-  // 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));
+  // Detect Monitor closing its end of the stdout pipe.
+  process.stdout.on("close", () => {
+    cleanup();
+    process.exit(0);
+  });
 
   logErr(`subscribe: agent=${ticket.agent_id} namespaces=${ticket.namespace_ids.join(",")}`);