patchcord 0.6.4 → 0.6.6

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

package/bin/patchcord.mjs

@@ -1195,7 +1195,10 @@ if (cmd === "login" || cmd === "orchestrator" || cmd === "teamlead" || cmd === "
     const hostname = run("hostname -s") || run("hostname") || "unknown";
     writeWorkerConfig(tool, dir, base, json.token, hostname);
     if (role) {
-      try { writeFileSync(join(dir, "AGENTS.md"), `# ${arg} — role: ${role}\n\nYou are \`${arg}\` in the \`${ns}\` Patchcord team. Role: ${role}.\nCoordinate with teammates over Patchcord (inbox / send_message / reply).\n`); } catch {}
+      const agyNote = (tool === "antigravity" || tool === "agy")
+        ? "\nMux prompts with a concrete task take priority — do not call inbox() before doing the work in the prompt.\n"
+        : "";
+      try { writeFileSync(join(dir, "AGENTS.md"), `# ${arg} — role: ${role}\n\nYou are \`${arg}\` in the \`${ns}\` Patchcord team. Role: ${role}.\nCoordinate with teammates over Patchcord (send_message / reply). Call inbox only on explicit wake or after finishing the current task.${agyNote}`); } catch {}
     }
     // Record in the local team manifest so `team launch` / `team status` see it.
     try {
@@ -1949,6 +1952,18 @@ if (!cmd || cmd === "install" || cmd === "agent" || cmd?.startsWith("--")) {
     if (removedStaleGlobal) {
       globalChanges.push("Removed global Patchcord skills/instructions (agy reads ~/.gemini/skills — per-project only)");
     }
+    // agy-cli loads ALL of ~/.gemini/skills in every folder — warn if orchestrator/mux
+    // skills are present (they say "call inbox first" and override mux task prompts).
+    const geminiSkillsRoot = join(HOME, ".gemini", "skills");
+    if (existsSync(geminiSkillsRoot)) {
+      const noisy = ["orchestrator-comms", "orchestrator-team", "orchestrator-flow", "mux", "actor-lead", "actor-team-lead"];
+      let entries = [];
+      try { entries = readdirSync(geminiSkillsRoot, { withFileTypes: true }).filter((d) => d.isDirectory()).map((d) => d.name); } catch {}
+      const found = entries.filter((n) => noisy.some((p) => n.includes(p)));
+      if (found.length) {
+        console.log(`  ${M.yellow}warning:${M.rst} ~/.gemini/skills has orchestrator/mux skills (${found.join(", ")}) — agy-cli reads them globally and may call inbox before your mux task. Keep orchestrator skills in ~/.claude/skills or ~/.codex/skills only.`);
+      }
+    }
     // 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.4",
+  "version": "0.6.6",
   "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/antigravity/inbox/SKILL.md

@@ -9,7 +9,14 @@ 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.
 
-Invoke with `/patchcord-inbox` when Patchcord MCP is connected in this project.
+**TASK PRIORITY:** If the user's current message already names a concrete task
+(mux paste, file to build, "Focus on X", deliverables listed), do that work
+FIRST. Do NOT call inbox() or recall() before executing the task. The task text
+IS the assignment — inbox is for when the prompt is only a wake or you need
+message IDs after the work is done.
+
+Invoke with `/patchcord-inbox` when Patchcord MCP is connected AND you need to
+check team mail (not at session start, not before a concrete task in the prompt).
 
 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.
 

package/scripts/kimi-subscribe.sh

@@ -49,10 +49,16 @@ fi
 
 BASE_URL=$(echo "$URL" | sed 's|/mcp$||; s|/mcp/bearer$||')
 
-# Derive agent identity for pidfile
+# Poll loop: count_only + no registry write — same cost model as subscribe.mjs
+# drainQueueOnce (id SELECT only). Kimi cannot hold a WebSocket/Realtime
+# listener (no Monitor; task must exit to wake), so polling is the transport;
+# the bug was fetching full message bodies every tick.
+INBOX_POLL_QS="status=pending&limit=5&count_only=1&touch_presence=0"
+
+# Derive agent identity for pidfile (count_only, no registry write)
 IDENTITY_RESP=$(curl -s --max-time 5 \
   -H "Authorization: Bearer ${TOKEN}" \
-  "${BASE_URL}/api/inbox?limit=0" 2>/dev/null || echo "{}")
+  "${BASE_URL}/api/inbox?limit=0&count_only=1&touch_presence=0" 2>/dev/null || echo "{}")
 NAMESPACE_ID=$(echo "$IDENTITY_RESP" | jq -r '.namespace_id // empty' 2>/dev/null || true)
 AGENT_ID=$(echo "$IDENTITY_RESP" | jq -r '.agent_id // empty' 2>/dev/null || true)
 
@@ -99,7 +105,7 @@ echo "PATCHCORD: subscribe started (poll ${INTERVAL}s) for ${AGENT_ID}@${NAMESPA
 while true; do
   RESP=$(curl -s --max-time 10 \
     -H "Authorization: Bearer ${TOKEN}" \
-    "${BASE_URL}/api/inbox?status=pending&limit=5" 2>/dev/null || echo "{}")
+    "${BASE_URL}/api/inbox?${INBOX_POLL_QS}" 2>/dev/null || echo "{}")
 
   COUNT=$(echo "$RESP" | jq -r '.pending_count // 0' 2>/dev/null || echo "0")
 

package/skills/inbox/SKILL.md

@@ -19,6 +19,8 @@ This skill governs those 7 MCP tools. It applies only if they are actually avail
 - Do NOT read a bearer token out of `.mcp.json`, `settings.json`, `mcp_config.json`, or any other config file, and do NOT call the patchcord HTTP API (`/api/inbox`, etc.) directly. A token belongs to the one agent it was issued to; using another agent's token — or any token you found on disk — is never correct.
 - Just proceed with the user's actual request.
 
+**TASK PRIORITY (when MCP tools ARE present):** If the user's current message already contains a concrete task, do that work FIRST. Do not call inbox() first. Inbox is for explicit check-inbox requests, wake-only nudges, or finding the next task after you finish — not before executing a mux prompt that already spells out the work.
+
 A missing tool means patchcord is not configured for this agent. That is a normal, silent state, not a problem to work around.
 
 ## Do the work, never just acknowledge
@@ -45,7 +47,7 @@ The user can undo any change in 3 seconds with git. A wrong action costs nothing
 
 The following applies only when the patchcord MCP tools are present in this session (see the gate above). If they are absent, skip this entire section.
 
-Call inbox(). It returns pending messages, recently active agents, and your own push-receiving state via `self_subscribed`. Note that value — it determines whether you should call `wait_for_message` after sends for the rest of the session.
+**If the current user message already contains a concrete task, skip inbox and do that work first** (see TASK PRIORITY above). Otherwise call inbox() when the prompt is a wake-only nudge or you need coordination before starting work. It returns pending messages, recently active agents, and your own push-receiving state via `self_subscribed`. Note that value — it determines whether you should call `wait_for_message` after sends for the rest of the session.
 
 If `subscribe_appears_down: true` is in the response, your subscribe.mjs was running but appears dead. Tell the human: "Patchcord subscribe seems to have died — run `/patchcord:subscribe` to restart push delivery." Do not try to restart it yourself.