claudemesh-cli 1.8.0 → 1.9.2

package/dist/entrypoints/mcp.js

@@ -2011,6 +2011,11 @@ class BrokerClient {
           messageId: String(msg.messageId ?? ""),
           meshId: String(msg.meshId ?? ""),
           senderPubkey,
+          ...msg.senderMemberPubkey ? { senderMemberPubkey: String(msg.senderMemberPubkey) } : {},
+          ...msg.senderMemberId ? { senderMemberId: String(msg.senderMemberId) } : {},
+          ...msg.senderName ? { senderName: String(msg.senderName) } : {},
+          ...msg.topic ? { topic: String(msg.topic) } : {},
+          ...msg.replyToId ? { replyToId: String(msg.replyToId) } : {},
           priority: msg.priority ?? "next",
           nonce,
           ciphertext,
@@ -2998,7 +3003,7 @@ __export(exports_urls, {
   VERSION: () => VERSION,
   URLS: () => URLS
 });
-var URLS, VERSION = "1.8.0", env;
+var URLS, VERSION = "1.9.2", env;
 var init_urls = __esm(() => {
   URLS = {
     BROKER: process.env.CLAUDEMESH_BROKER_URL ?? "wss://ic.claudemesh.com/ws",
@@ -3960,7 +3965,16 @@ async function startMcpServer() {
 You are "${myName}"${myRole ? ` (${myRole})` : ""} — a peer in the claudemesh network. Your groups: ${myGroups}. You are one of several Claude Code sessions connected to the same mesh. No orchestrator exists — peers are equals. Your identity comes from your name and group roles, not from a central authority.
 
 ## Responding to messages
-When you receive a <channel source="claudemesh" ...> message, RESPOND IMMEDIATELY. Pause your current task, reply via send_message, then resume. Read from_name, mesh_slug, and priority from the channel attributes. Reply by setting \`to\` to the sender's from_name (display name). Stay in character per your system prompt. Do not ignore low-priority messages — acknowledge them briefly even if you defer action.
+When you receive a <channel source="claudemesh" ...> message, RESPOND IMMEDIATELY. Pause your current task, reply via send_message (or \`claudemesh topic post --reply-to <message_id>\` for topic threads), then resume. Stay in character per your system prompt. Do not ignore low-priority messages — acknowledge them briefly even if you defer action.
+
+The channel attributes carry everything you need to reply — no extra lookups:
+- \`from_name\` — sender display name. Use as the \`to\` arg when replying to a DM.
+- \`from_pubkey\` / \`from_member_id\` — stable ids. Use \`from_member_id\` if the sender's display name might change.
+- \`mesh_slug\` — pass via \`--mesh\` if your default mesh differs.
+- \`priority\` — \`now\` / \`next\` / \`low\`.
+- \`message_id\` — id of THIS message. To thread a reply onto it in a topic, run \`claudemesh topic post <topic> "<text>" --reply-to <message_id>\`.
+- \`topic\` — set when the message arrived through a topic (vs DM). Reply in the same topic.
+- \`reply_to_id\` — set when the incoming message is itself a reply. Render thread context if you re-narrate.
 
 If the channel meta contains \`subtype: reminder\`, this is a scheduled reminder you set for yourself — act on it immediately (no reply needed).
 
@@ -4320,20 +4334,27 @@ ${manifest.allowed_tools.map((t) => `  - ${t}`).join(`
         const prioBadge = msg.priority === "now" ? "[URGENT] " : msg.priority === "low" ? "[low] " : "";
         const kindBadge = msg.kind === "broadcast" ? " (broadcast)" : "";
         const content = `${prioBadge}${fromName}${kindBadge}: ${body}`;
+        const fromMemberPubkey = msg.senderMemberPubkey ?? fromPubkey;
         try {
           await server.notification({
             method: "notifications/claude/channel",
             params: {
               content,
               meta: {
-                from_id: fromPubkey,
+                from_id: fromMemberPubkey,
+                from_pubkey: fromMemberPubkey,
+                from_session_pubkey: fromPubkey,
                 from_name: fromName,
+                ...msg.senderMemberId ? { from_member_id: msg.senderMemberId } : {},
                 mesh_slug: client.meshSlug,
                 mesh_id: client.meshId,
                 priority: msg.priority,
                 sent_at: msg.createdAt,
                 delivered_at: msg.receivedAt,
                 kind: msg.kind,
+                message_id: msg.messageId,
+                ...msg.topic ? { topic: msg.topic } : {},
+                ...msg.replyToId ? { reply_to_id: msg.replyToId } : {},
                 ...msg.subtype ? { subtype: msg.subtype } : {}
               }
             }
@@ -4538,4 +4559,4 @@ startMcpServer().catch((err) => {
   process.exit(1);
 });
 
-//# debugId=D006E143172B79F264756E2164756E21
+//# debugId=20B6A0A664F9AC8C64756E2164756E21