patchcord 0.6.33 → 0.6.34

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchcord",
-  "version": "0.6.33",
+  "version": "0.6.34",
   "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/scripts/subscribe.mjs

@@ -617,7 +617,18 @@ function runOnce(ticket, baseUrl, getToken, refreshTicket) {
       // Skip terminal resolved replies — they carry thread_resolved_at and need
       // no action from the recipient. Notifying on them is the root cause of ack loops.
       if (rec.thread_resolved_at) return;
-      const from = rec.from_agent || "unknown";
+      // Qualify the sender when the message crosses a namespace boundary.
+      // A bare seat name is ambiguous the moment this agent is linked to two
+      // namespaces that share it, and `lead` is the seat name every team has.
+      // rec.namespace_id is OUR namespace here (the row is addressed to us);
+      // rec.from_namespace is the sender's. If either is missing we render
+      // bare rather than inventing an origin.
+      const fromAgent = rec.from_agent || "unknown";
+      const fromNs = rec.from_namespace;
+      const from =
+        fromNs && rec.namespace_id && fromNs !== rec.namespace_id
+          ? `${fromAgent}@${fromNs}`
+          : fromAgent;
       notify(`PATCHCORD: 1 new from ${from}`, { from, count: 1, kind: "message" });
     });
 

package/skills/inbox/SKILL.md

@@ -51,6 +51,14 @@ If `subscribe_appears_down: true` is in the response, your subscribe.mjs was run
 
 If there are pending messages, reply to all of them immediately. Do not ask the human first. Do not explain what you plan to reply. Just do the work described in each message, then reply with what you did, then tell the human what you received and what you did about it.
 
+## Name the other agent when you talk to the human
+
+When you tell a human that you sent, received, or replied to a message, always write the full address as `name@namespace` — never a bare role word like "the worker", "their lead", or "the team".
+
+The human cannot see your inbox. An unnamed recipient is a claim they cannot check. They need to see at a glance where work has stalled; if finding the stalled agent takes an investigation, twenty coordinated operations were worth nothing.
+
+`name` alone is not enough either once you are linked to more than one namespace — every team has a seat called `lead`, so two of them read identically.
+
 ## Sending
 
 1. inbox() - clear any pending messages that block outbound sends. From the response, note `self_subscribed` (your own push-receiving state).