patchcord 0.6.1 → 0.6.2

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.1",
+  "version": "0.6.2",
   "author": {
     "name": "ppravdin"
   },

package/bin/patchcord.mjs

@@ -1889,6 +1889,28 @@ if (!cmd || cmd === "install" || cmd === "agent" || cmd?.startsWith("--")) {
         }
       } catch {}
     }
+    // Older installers seeded Antigravity-only skills globally, and the
+    // Antigravity CLI caches each MCP server's tools/instructions globally.
+    // Both survive removal of the global mcp_config entry and can make a bare
+    // agy session synthesize an unconditional Patchcord rule in every folder.
+    // Antigravity is project-scoped, so remove only Patchcord's stale global
+    // artifacts; other MCP servers and Antigravity state stay untouched.
+    const staleAntigravityPatchcord = [
+      join(HOME, ".gemini", "antigravity", "skills", "patchcord"),
+      join(HOME, ".gemini", "antigravity", "skills", "patchcord-wait"),
+      join(HOME, ".gemini", "antigravity-cli", "skills", "patchcord"),
+      join(HOME, ".gemini", "antigravity-cli", "skills", "patchcord-wait"),
+      join(HOME, ".gemini", "antigravity-cli", "mcp", "patchcord"),
+    ];
+    let removedStaleAntigravity = false;
+    for (const stale of staleAntigravityPatchcord) {
+      if (existsSync(stale)) {
+        try { rmSync(stale, { recursive: true, force: true }); removedStaleAntigravity = true; } catch {}
+      }
+    }
+    if (removedStaleAntigravity) {
+      globalChanges.push("Removed stale global Antigravity Patchcord instructions (agy is per-project)");
+    }
     // true = configured, false = file absent (definitely not), null = unparseable (unknown)
     const hasPatchcordMcp = (p, keyPath) => {
       if (!existsSync(p)) return false;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchcord",
-  "version": "0.6.1",
+  "version": "0.6.2",
   "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/kimi/inbox/SKILL.md

@@ -5,6 +5,12 @@ description: Read Patchcord inbox and reply to messages
 
 Run this with `/skill:patchcord-inbox`. (Kimi Code has no `/flow:` — `/skill:` injects this as a prompt and you act on it.)
 
+## Applies only when Patchcord MCP tools are loaded
+
+If the `inbox` MCP tool is not available in this session, this skill does not
+apply. Do nothing: do not run the Patchcord CLI, read a token from a config
+file, or call the HTTP API. A missing project MCP config is a normal state.
+
 Call the `inbox` MCP tool now. In its response, the first header line is YOUR own identity (the recipient); the real sender of each message is on a `From X` line — never confuse the two.
 
 For each pending message, classify it and act:

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

@@ -5,6 +5,12 @@ description: Start the Patchcord background polling listener
 
 Run this with `/skill:patchcord-subscribe`. (Kimi Code has no `/flow:` — `/skill:` injects this as a prompt and you act on it.)
 
+## Applies only when Patchcord MCP tools are loaded
+
+If the `inbox` MCP tool is not available in this session, this skill does not
+apply. Do nothing: do not run the Patchcord CLI, read a token from a config
+file, or call the HTTP API. A missing project MCP config is a normal state.
+
 First, call the `inbox` MCP tool and DRAIN every pending message before starting the listener (the listener exits immediately if messages are already waiting). In the inbox response, the first header line is YOUR identity (recipient); the real sender is on each `From X` line. For each message:
 - **ACK** (thanks, noted, works, ok, 👍) → `reply(message_id, resolve=true)`, no content.
 - **BLOCKED** → `reply(message_id, "<reason>", defer=true)`.

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

@@ -5,6 +5,12 @@ description: Wait for one incoming Patchcord message
 
 Run this with `/skill:patchcord-wait`. (Kimi Code has no `/flow:` — `/skill:` injects this as a prompt and you act on it.)
 
+## Applies only when Patchcord MCP tools are loaded
+
+If the `wait_for_message` MCP tool is not available in this session, this skill
+does not apply. Do nothing: do not run the Patchcord CLI, read a token from a
+config file, or call the HTTP API. A missing project MCP config is a normal state.
+
 Call the `wait_for_message` MCP tool now to block until a message arrives or ~5 minutes elapse.
 
 When a message arrives, classify it and act: