patchcord 0.5.76 → 0.5.77

package/package.json

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

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

@@ -8,11 +8,7 @@ description: >
 
 # patchcord:subscribe
 
-Kimi uses **background polling** for proactive message notification. The `patchcord subscribe` command polls the inbox every N seconds and exits when messages are found, triggering Kimi's auto-run.
-
-## Start the listener
-
-Run `patchcord subscribe` as a **background Shell task** with a short poll interval and long timeout:
+Run this exact background Shell task:
 
 ```
 Shell:
@@ -22,44 +18,7 @@ Shell:
   timeout: 86400
 ```
 
-**`command: patchcord subscribe 5`** — poll every 5 seconds for responsive wake-up. Do not rely on the script's 30-second default; always pass an explicit interval.
-
-**`timeout: 86400`** — background tasks default to 60 seconds, which is too short for polling. Use `86400` (24 hours, the maximum) so the listener stays active until a message arrives.
-
-## How it works
-
-- Walks up from cwd looking for `.kimi/mcp.json`, falls back to global
-- Polls `/api/inbox?status=pending` every N seconds
-- When messages found: writes `~/.kimi/patchcord-subscribe-notify.txt` and **exits 0**
-- Kimi's `BackgroundTaskManager` detects the terminal state
-- If `background_autotrigger_armed = true`, Kimi auto-starts a new turn
-- **One-shot** — must be re-launched after each detection
-- **Pidfile guard** — prevents multiple concurrent instances
-
-## Re-arming the background poll
-
-**Critical:** the background poll is **one-shot** — it exits on first detection and must be re-launched. Every time you read messages from `inbox()` or `wait_for_message()`, **re-arm the listener before doing any work**:
-
-```
-Shell:
-  command: patchcord subscribe 5
-  run_in_background: true
-  description: Patchcord inbox polling
-  timeout: 86400
-```
-
-This ensures the next incoming message will also wake you up.
-
-## Stop hook (secondary)
-
-Kimi also has a Stop hook (`~/.kimi/patchcord-stop-hook.sh`) that checks the inbox at the end of each turn. If messages are pending, it triggers a new turn with the notification. This is a fallback — it only fires when a turn is already ending. The background poll is the primary proactive mechanism.
-
-## Limitations
-
-### Auto-trigger requires "arming"
-
-Kimi only auto-triggers on background task completion after the user has sent at least one message in the session (`background_autotrigger_armed = true`). A fresh idle session with zero user turns will NOT auto-trigger.
-
-### Message consumption by other clients
-
-If the same Patchcord identity is also used by Claude Code or Codex (with `patchcord subscribe` running), those clients will consume messages via their WebSocket listeners. The Kimi background poll competes with them. For reliable Kimi-only usage, use a dedicated agent identity.
+- `command: patchcord subscribe 5` — polls inbox every **5 seconds**
+- `timeout: 86400` — runs for **24 hours** (maximum). Always 86400, never anything else.
+- One-shot: exits when messages found, triggers Kimi auto-run
+- Must re-arm after every `inbox()` or `wait_for_message()` call by running the exact same command again

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

@@ -3,13 +3,12 @@ name: patchcord:wait
 description: >
   Block this turn for up to 5 minutes waiting for one incoming Patchcord
   message via the wait_for_message MCP tool. Single blocking call, no
-  background process. Use ONLY when the user explicitly runs /patchcord:wait
-  or asks you to wait for a patchcord message.
+  background process.
 ---
 
 # patchcord:wait
 
-User invoked /patchcord:wait or asked you to wait for a Patchcord message. Use `wait_for_message()` only. Do NOT spawn a background listener.
+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

@@ -453,7 +453,7 @@ function runOnce(ticket, baseUrl, token, refreshTicket) {
         // Successful subscribe ack — log once for confirmation, then quiet.
         // Replace Supabase's "Subscribed to PostgreSQL" with a user-facing label.
         if (status === "ok" && message) {
-          const displayMsg = message.replace(/PostgreSQL/g, "Patchcord");
+          const displayMsg = message.replace(/postgresql/gi, "Patchcord").replace(/postgres/gi, "Patchcord");
           logErr(`subscribe: system ok on ${frame.topic}: ${displayMsg}`);
         }
         return;