claudemesh-cli 1.8.0 → 1.9.2

package/README.md

@@ -2,7 +2,9 @@
 
 Peer mesh for Claude Code sessions. Connect multiple Claude Code instances into a shared mesh with real-time messaging, shared state, memory, file sharing, vector store, scheduled jobs, and more — all driven from the `claudemesh` CLI. The MCP server is a tool-less push-pipe that delivers inbound peer messages to Claude as `<channel>` interrupts; everything else lives behind CLI verbs that Claude learns from the auto-installed `claudemesh` skill.
 
-> **What's new in 1.8.0:** per-topic end-to-end encryption (v0.3.0 phase 3, CLI side). `claudemesh topic post <topic> <msg>` encrypts the body with `crypto_secretbox` under the topic's symmetric key — broker stores ciphertext only. `claudemesh topic tail` now decrypts v2 messages on render and runs a background re-seal loop every 30s, so new topic joiners get their sealed keys without manual action. `topic-key` cache is process-only — kill the CLI, the key forgets. Web dashboard reads v1 plaintext for now (phase 3.5 brings browser-side identity).
+> **What's new in 1.9.x:** topic threading + multi-session reliability fixes. `claudemesh topic post <topic> <msg> --reply-to <id>` threads a reply onto a previous topic message (full id or 8+ char prefix); `topic tail` renders `↳ in reply to <name>: "<snippet>"` above replies and shows a copyable `#xxxxxxxx` short id on every row. `<channel>` MCP attrs now carry `from_member_id`, `from_pubkey` (stable), `from_session_pubkey` (ephemeral), `message_id`, `topic`, `reply_to_id` — everything the recipient needs to reply directly. Broker fixes (v0.3.2): replies to a stale session pubkey now resolve to the owning member's live session instead of bouncing with "not online", and broadcast `*` no longer loopbacks decrypt-fail warnings to the sender's sibling sessions.
+>
+> **What was new in 1.8.0:** per-topic end-to-end encryption (v0.3.0 phase 3, CLI side). `claudemesh topic post <topic> <msg>` encrypts the body with `crypto_secretbox` under the topic's symmetric key — broker stores ciphertext only. `claudemesh topic tail` now decrypts v2 messages on render and runs a background re-seal loop every 30s, so new topic joiners get their sealed keys without manual action. `topic-key` cache is process-only — kill the CLI, the key forgets. Web dashboard reads v1 plaintext for now (phase 3.5 brings browser-side identity).
 >
 > **What was new in 1.7.0:** terminal parity for the v1.6.x server features. New verbs: `claudemesh topic tail` (live SSE message stream — Ctrl-C to exit), `claudemesh notification list` (recent `@you` mentions across topics), `claudemesh member list` (mesh roster with online dots, distinct from `peer list`'s live-session view). Each command auto-mints a 5-minute read-only apikey via the WebSocket and revokes it on exit, so no token plumbing is needed.
 >

package/dist/entrypoints/cli.js

@@ -88,7 +88,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",
@@ -2779,6 +2779,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,
@@ -11798,6 +11803,17 @@ var exports_topic_tail = {};
 __export(exports_topic_tail, {
   runTopicTail: () => runTopicTail
 });
+function rememberRendered(cache2, m, text) {
+  cache2.set(m.id, {
+    name: m.senderName || m.senderPubkey.slice(0, 8),
+    snippet: text.replace(/\s+/g, " ").slice(0, 60)
+  });
+  if (cache2.size > RECENT_CACHE_MAX) {
+    const firstKey = cache2.keys().next().value;
+    if (firstKey)
+      cache2.delete(firstKey);
+  }
+}
 function decodeV1(b64) {
   try {
     return Buffer.from(b64, "base64").toString("utf-8");
@@ -11824,15 +11840,24 @@ function fmtTime(iso) {
     return iso;
   }
 }
-async function printMessage(m, topicKey, json) {
+async function printMessage(m, topicKey, json, cache2) {
   const text = await decryptForRender(m, topicKey);
   if (json) {
     console.log(JSON.stringify({ ...m, message: text }));
+    rememberRendered(cache2, m, text);
     return;
   }
   const v2Marker = (m.bodyVersion ?? 1) === 2 ? dim("\uD83D\uDD12 ") : "";
-  process.stdout.write(`  ${dim(fmtTime(m.createdAt))}  ${bold(m.senderName || m.senderPubkey.slice(0, 8))}  ${v2Marker}${text}
+  if (m.replyToId) {
+    const parent = cache2.get(m.replyToId);
+    const ref = parent ? `${parent.name}: "${parent.snippet}${parent.snippet.length === 60 ? "…" : ""}"` : `${m.replyToId.slice(0, 8)}…`;
+    process.stdout.write(`  ${dim("↳ in reply to " + ref)}
 `);
+  }
+  const idTag = dim(`#${m.id.slice(0, 8)}`);
+  process.stdout.write(`  ${dim(fmtTime(m.createdAt))}  ${bold(m.senderName || m.senderPubkey.slice(0, 8))}  ${idTag}  ${v2Marker}${text}
+`);
+  rememberRendered(cache2, m, text);
 }
 async function* readSseStream(reader) {
   const decoder = new TextDecoder;
@@ -11891,6 +11916,7 @@ async function runTopicTail(name, flags) {
       topicName: cleanName
     });
     const topicKey = keyResult.ok ? keyResult.topicKey ?? null : null;
+    const snippetCache = new Map;
     let resealTimer = null;
     if (topicKey) {
       const reseal = async () => {
@@ -11943,7 +11969,7 @@ async function runTopicTail(name, flags) {
           render.section(`${clay("#" + cleanName)} on ${dim(meshSlug)} — backfill ${history.messages.length}, then live`);
         }
         for (const m of history.messages.slice().reverse()) {
-          await printMessage(m, topicKey, flags.json ?? false);
+          await printMessage(m, topicKey, flags.json ?? false, snippetCache);
         }
       } catch (err) {
         render.warn(`backfill failed: ${err.message}`);
@@ -11982,7 +12008,7 @@ async function runTopicTail(name, flags) {
         if (ev.event === "message") {
           try {
             const m = JSON.parse(ev.data);
-            await printMessage(m, topicKey, flags.json ?? false);
+            await printMessage(m, topicKey, flags.json ?? false, snippetCache);
           } catch {}
         }
       }
@@ -12000,6 +12026,7 @@ async function runTopicTail(name, flags) {
     }
   });
 }
+var RECENT_CACHE_MAX = 256;
 var init_topic_tail = __esm(() => {
   init_urls();
   init_with_rest_key();
@@ -12060,6 +12087,27 @@ async function runTopicPost(topicName, message, flags) {
         return EXIT.INTERNAL_ERROR;
       }
     }
+    let replyToId;
+    if (flags.replyTo) {
+      if (flags.replyTo.length >= 16) {
+        replyToId = flags.replyTo;
+      } else if (flags.replyTo.length >= 6) {
+        const recent = await request({
+          path: `/api/v1/topics/${encodeURIComponent(cleanName)}/messages?limit=200`,
+          method: "GET",
+          token: secret
+        });
+        const hit = recent.messages?.find((r) => r.id.startsWith(flags.replyTo));
+        if (!hit) {
+          render.err(`--reply-to ${flags.replyTo}: no recent message id starts with that prefix`);
+          return EXIT.INVALID_ARGS;
+        }
+        replyToId = hit.id;
+      } else {
+        render.err("--reply-to needs at least 6 characters of the message id");
+        return EXIT.INVALID_ARGS;
+      }
+    }
     const result = await request({
       path: "/api/v1/messages",
       method: "POST",
@@ -12069,7 +12117,8 @@ async function runTopicPost(topicName, message, flags) {
         ciphertext,
         nonce,
         bodyVersion,
-        ...mentions.length > 0 ? { mentions } : {}
+        ...mentions.length > 0 ? { mentions } : {},
+        ...replyToId ? { replyToId } : {}
       }
     });
     if (flags.json) {
@@ -12077,7 +12126,8 @@ async function runTopicPost(topicName, message, flags) {
       return EXIT.SUCCESS;
     }
     const versionTag = bodyVersion === 2 ? green("\uD83D\uDD12 v2") : dim("v1");
-    render.ok("posted", `${clay("#" + cleanName)}  ${versionTag}  ${dim(`(${result.notifications} mentions)`)}`);
+    const replyTag = result.replyToId ? `  ${dim("↳ " + result.replyToId.slice(0, 8))}` : "";
+    render.ok("posted", `${clay("#" + cleanName)}  ${versionTag}${replyTag}  ${dim(`(${result.notifications} mentions)`)}`);
     return EXIT.SUCCESS;
   });
 }
@@ -12445,7 +12495,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).
 
@@ -12805,20 +12864,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 } : {}
               }
             }
@@ -13772,7 +13838,7 @@ Topic  (conversation scope, v0.2.0)
   claudemesh topic history <t>     fetch message history [--limit --before]
   claudemesh topic read <topic>    mark all as read
   claudemesh topic tail <topic>    live SSE tail [--limit --forward-only]
-  claudemesh topic post <t> <msg>  encrypted REST post (v0.3.0 v2)
+  claudemesh topic post <t> <msg>  encrypted REST post (v0.3.0 v2) [--reply-to <id>]
   claudemesh send "#topic" "msg"   send to a topic (WS path, v1 plaintext)
   claudemesh member list           mesh roster with online state [--online]
   claudemesh notification list     recent @-mentions of you [--since <ISO>]
@@ -14567,7 +14633,8 @@ async function main() {
         const postFlags = {
           mesh: flags.mesh,
           json: !!flags.json,
-          plaintext: !!flags.plaintext
+          plaintext: !!flags.plaintext,
+          replyTo: flags["reply-to"] || flags.replyTo
         };
         const message = positionals.slice(2).join(" ");
         const { runTopicPost: runTopicPost2 } = await Promise.resolve().then(() => (init_topic_post(), exports_topic_post));
@@ -14660,4 +14727,4 @@ main().catch((err) => {
   process.exit(EXIT.INTERNAL_ERROR);
 });
 
-//# debugId=25484051F3F24E9464756E2164756E21
+//# debugId=25CA2A7E4B8DBD3564756E2164756E21