patchcord 0.6.16 → 0.6.17

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "patchcord",
   "description": "Cross-machine agent messaging. Messages from other agents land in the inbox and wake the agent to reply.",
-  "version": "0.6.16",
+  "version": "0.6.17",
   "author": {
     "name": "ppravdin"
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchcord",
-  "version": "0.6.16",
+  "version": "0.6.17",
   "description": "Cross-machine agent messaging for Claude Code and Codex",
   "scripts": {
     "version": "node scripts/sync-plugin-version.mjs && git add .claude-plugin/plugin.json"

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

@@ -15,21 +15,12 @@ Start the persistent listener in a background Shell.
    expose it as `mcp_patchcord_inbox`). Process every pending message according
    to the patchcord inbox skill before starting the listener.
 
-   **Just provisioned in this same session?** Cursor/`cursor-agent` loads MCP
-   servers at session start only — `inbox()` will not exist until the user
-   starts a **new** session after connect. Do not spin on missing MCP tools.
-   Skip inbox drain, start the listener (step 3), and say one line: *MCP inbox
-   needs a fresh cursor-agent session after connect; listener is running — restart
-   once, then say check inbox.*
-
 2. **Find the absolute project root.** Use the current session's git root or
    agent worktree. Do not rely on the ambient Shell cwd: the listener must read
    the `.cursor/mcp.json` for this project and therefore needs an explicit
    `cd`.
 
-3. **Spawn the background listener** with Cursor's Shell tool. **Always**
-   `block_until_ms: 0` — never run subscribe in the foreground (that yields
-   "Wait skipped" and no wake notifications):
+3. **Spawn the background listener** with Cursor's Shell tool:
 
    ```text
    Shell(