patchcord 0.5.34 → 0.5.36

package/package.json

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

package/skills/subscribe/SKILL.md

@@ -1,28 +1,32 @@
 ---
 name: patchcord:subscribe
 description: >
-  Start a background listener that wakes Claude the moment a new Patchcord
-  message arrives for this agent. Uses Supabase Realtime over WebSocket —
-  zero polling. Use when the user says "subscribe", "listen for patchcord
-  messages", "wake me when messages arrive", or runs /patchcord:subscribe.
+  Start a persistent background WebSocket listener (Supabase Realtime) that
+  wakes Claude when new Patchcord messages arrive. Survives across turns
+  until the user kills it or closes the session. Use ONLY when the user
+  explicitly runs /patchcord:subscribe.
 ---
 
+User invoked /patchcord:subscribe — do NOT substitute `wait_for_message()`. Spawn the listener.
+
 # Start
 
-Spawn under Monitor (not Bash with run_in_background — Monitor turns each stdout line into a notification):
+1. **Drain the inbox first.** Call `mcp__patchcord__inbox`. If anything is pending, process it per the patchcord:inbox skill before continuing. Backlog can accumulate while no listener was up; subscribe must catch it.
+
+2. **Spawn the listener under Monitor** (not Bash with run_in_background — Monitor turns each stdout line into a notification):
 
-```
-Monitor(
-  description: "patchcord realtime listener",
-  persistent: true,
-  timeout_ms: 3600000,
-  command: "exec npx patchcord subscribe"
-)
-```
+   ```
+   Monitor(
+     description: "patchcord realtime listener",
+     persistent: true,
+     timeout_ms: 3600000,
+     command: "exec npx patchcord subscribe"
+   )
+   ```
 
-`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.
+   `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.
 
-Then one line to the user: *"Patchcord listener active — I'll pick up new messages as they arrive."*
+3. **Tell the user one line:** *"Patchcord listener active — I'll pick up new messages as they arrive."*
 
 # When a notification fires
 

package/skills/wait/SKILL.md

@@ -1,13 +1,16 @@
 ---
 name: patchcord:wait
 description: >
-  Enter listening mode - wait for incoming patchcord messages. Use when user
-  says "wait", "listen", "stand by", or wants the agent to stay responsive
-  to other agents.
+  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.
 ---
 # patchcord:wait
 
-Enter listening mode. Call `wait_for_message()` to block until a message arrives (up to 5 minutes).
+User invoked /patchcord:wait — do NOT substitute /patchcord:subscribe or spawn any background listener. Use `wait_for_message()` only.
+
+Call `wait_for_message()` to block until a message arrives (up to 5 minutes).
 
 When a message arrives: