patchcord 0.5.88 → 0.5.90

package/package.json

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

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

@@ -8,7 +8,7 @@ type: flow
 
 ```mermaid
 flowchart TD
-  A([BEGIN]) --> B[Call the inbox MCP tool. For each pending message: do the work it asks for, then call reply with the message_id and a concrete summary of what you did.]
+  A([BEGIN]) --> B[Call the inbox MCP tool. Reading the response: the first header line shows YOUR own identity (the recipient). The actual sender of each message is shown on a 'From X' line — never confuse the header with the sender. For each pending message: do the work it asks for, then call reply with the message_id and a concrete summary of what you did.]
   B --> C[Call the Shell tool with these exact parameters to re-arm the listener: command='patchcord subscribe --kimi 5', run_in_background=true, timeout=86400, description='Patchcord listener'.]
   C --> D([END])
 ```

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

@@ -8,7 +8,7 @@ type: flow
 
 ```mermaid
 flowchart TD
-  A([BEGIN]) --> B[First, call the inbox MCP tool. If there are pending messages, do the work each message asks for and call reply with the message_id and a concrete summary of what you did. Do NOT skip this step — the listener exits immediately if messages are already waiting, so you must drain them before starting it.]
+  A([BEGIN]) --> B[First, call the inbox MCP tool. Reading the response: the first header line shows YOUR own identity (the recipient). The actual sender of each message is shown on a 'From X' line — never confuse the header with the sender. If there are pending messages, do the work each message asks for and call reply with the message_id and a concrete summary of what you did. Do NOT skip this step — the listener exits immediately if messages are already waiting, so you must drain them before starting it.]
   B --> C[Now call the Shell tool with these exact parameters: command='patchcord subscribe --kimi 5', run_in_background=true, timeout=86400, description='Patchcord listener'. Then tell the user in one sentence: Patchcord listener active.]
   C --> D([END])
 ```

package/scripts/kimi-session-start.sh

@@ -24,9 +24,8 @@ if command -v jq >/dev/null 2>&1; then
   fi
 fi
 
-# --force tells kimi-subscribe.sh to kill any orphan listener (from a prior
-# Kimi session for this same project) before claiming the pidfile. Subscribe
-# resolves the project-specific pidfile name from .kimi/mcp.json itself, so
-# concurrent sessions for OTHER projects are untouched.
-nohup bash "$KIMI_SUB" --force 5 >/dev/null 2>&1 &
+# kimi-subscribe.sh always replaces any existing listener for this project,
+# so SessionStart starts a fresh listener even if a previous Kimi session
+# left one running.
+nohup bash "$KIMI_SUB" 5 >/dev/null 2>&1 &
 exit 0

package/scripts/kimi-subscribe.sh

@@ -14,19 +14,6 @@ set -euo pipefail
 
 command -v jq >/dev/null 2>&1 || { echo "jq required" >&2; exit 1; }
 
-# Parse --force flag (kills any existing listener for THIS project first).
-# SessionStart hook passes --force so fresh sessions always get a fresh listener.
-FORCE=0
-ARGS=()
-for arg in "$@"; do
-  if [ "$arg" = "--force" ]; then
-    FORCE=1
-  else
-    ARGS+=("$arg")
-  fi
-done
-set -- "${ARGS[@]+"${ARGS[@]}"}"
-
 # Resolve MCP config: per-project first, then global
 KIMI_MCP=""
 dir="$PWD"
@@ -73,29 +60,21 @@ fi
 PIDFILE="/tmp/patchcord_subscribe_${NAMESPACE_ID}_${AGENT_ID}.pid"
 NOTIFY_FILE="${HOME}/.kimi/patchcord-subscribe-notify.txt"
 
-# Pidfile guard.
-# --force: kill the existing listener (if any) and take over. Used by SessionStart
-#   so a fresh Kimi session always gets a fresh listener for this project.
-# default: if another instance is alive, exit 0 with a clear message so user-
-#   invoked flow skill calls are idempotent (no "background task failed").
+# Always replace any existing listener for this project. Otherwise the agent
+# sees an instant exit ("already running") and narrates it as "listener failed
+# to start" / "exited cleanly because no messages" — confusing UX. By killing
+# the old one, the new task stays in "running" state in Kimi's task browser,
+# which is what the user expects when they invoke /flow:patchcord:subscribe.
 if [ -f "$PIDFILE" ]; then
   OLD_PID=$(cat "$PIDFILE" 2>/dev/null || echo "")
   if [ -n "$OLD_PID" ] && kill -0 "$OLD_PID" 2>/dev/null; then
-    if [ "$FORCE" = "1" ]; then
-      kill "$OLD_PID" 2>/dev/null || true
-      # Wait briefly for the old process to clean up its pidfile
-      for _ in 1 2 3 4 5; do
-        kill -0 "$OLD_PID" 2>/dev/null || break
-        sleep 0.2
-      done
-      rm -f "$PIDFILE" 2>/dev/null || true
-    else
-      echo "Patchcord listener active."
-      exit 0
-    fi
-  else
-    rm -f "$PIDFILE" 2>/dev/null || true
+    kill "$OLD_PID" 2>/dev/null || true
+    for _ in 1 2 3 4 5; do
+      kill -0 "$OLD_PID" 2>/dev/null || break
+      sleep 0.2
+    done
   fi
+  rm -f "$PIDFILE" 2>/dev/null || true
 fi
 echo $$ > "$PIDFILE"