@sym-bot/mesh-channel 0.3.8 → 0.3.10

package/.claude-plugin/marketplace.json

@@ -1,19 +1,19 @@
 {
-  "name": "sym-mesh-channel",
+  "name": "sym-bot",
   "owner": {
     "name": "SYM.BOT",
     "email": "info@sym.bot"
   },
   "metadata": {
     "description": "Real-time communication and collaboration among Claude Code sessions — agent-to-agent cognitive signals over Bonjour LAN or WebSocket relay, on the Mesh Memory Protocol (MMP).",
-    "version": "0.3.8"
+    "version": "0.3.10"
   },
   "plugins": [
     {
       "name": "sym-mesh-channel",
       "source": "./",
       "description": "Real-time communication and collaboration among Claude Code sessions. Turns Claude Code into a peer node on the SYM mesh — two or more sessions discover each other via Bonjour (LAN) or a WebSocket relay (cross-network) and exchange structured cognitive signals as channel notifications. Each peer has its own Ed25519 identity, SVAF content gating, and local memory. Built on the Mesh Memory Protocol (MMP), an open peer-to-peer protocol for multi-agent collective intelligence.",
-      "version": "0.3.8",
+      "version": "0.3.10",
       "author": {
         "name": "Hongwei Xu",
         "email": "hongwei@sym.bot"

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "sym-mesh-channel",
-  "version": "0.3.8",
+  "version": "0.3.10",
   "description": "Real-time Claude-to-Claude mesh. Agent-to-agent cognitive signals over Bonjour LAN or WebSocket relay.",
   "author": {
     "name": "Hongwei Xu",

package/.mcp.json

@@ -2,7 +2,10 @@
   "mcpServers": {
     "claude-sym-mesh": {
       "command": "npx",
-      "args": ["-y", "@sym-bot/mesh-channel@0.3.8"],
+      "args": [
+        "-y",
+        "@sym-bot/mesh-channel@0.3.10"
+      ],
       "env": {
         "SYM_RELAY_URL": "${user_config.relay_url}",
         "SYM_RELAY_TOKEN": "${user_config.relay_token}",

package/README.md

@@ -7,7 +7,7 @@
 ```
 # in Claude Code — the first line is one-time setup
 /plugin marketplace add sym-bot/sym-mesh-channel
-/plugin install sym-mesh-channel@sym-mesh-channel
+/plugin install sym-mesh-channel@sym-bot
 ```
 
 [![npm](https://img.shields.io/npm/v/@sym-bot/mesh-channel)](https://www.npmjs.com/package/@sym-bot/mesh-channel)
@@ -66,16 +66,26 @@ They're **not alternatives** — the channel is built *on* sym and speaks the sa
 
 ## Quick start
 
-Install the published plugin from the SYM marketplace — in Claude Code:
+Install the published plugin from the **sym-bot** marketplace — in Claude Code:
 
 ```
 /plugin marketplace add sym-bot/sym-mesh-channel
-/plugin install sym-mesh-channel@sym-mesh-channel
+/plugin install sym-mesh-channel@sym-bot
 ```
 
-That's the whole setup: all 11 MCP tools, plus peer messages appearing in Claude's context mid-turn with no tool call — the "Claude thinks with the mesh" experience the screenshots above show. **One install covers every Claude Code session on the machine** — open as many as you like (one per repo, or one planning while another codes); each picks up the mesh on resume. The first command is a one-time marketplace registration.
+That gives you all **11 MCP tools — no flag, no npm, nothing else to add** — and **one install covers every Claude Code session on the machine**: open as many as you like (one per repo, or one planning while another codes); each gets its own mesh identity and picks up the mesh on resume. The first command is a one-time marketplace registration.
 
-Also in the official [Anthropic Plugin Directory](https://claude.ai/settings/plugins) — browse `/plugin` → **Discover** and search "mesh", or install from `@claude-community` after `/plugin marketplace add anthropics/claude-plugins-community`. If real-time `<channel>` notifications don't arrive, see [Troubleshooting](#channel-notifications-never-arrive-even-though-peers-are-connected).
+Also in the official [Anthropic Plugin Directory](https://claude.ai/settings/plugins) — `/plugin` → **Discover** → search "mesh", or `/plugin install sym-mesh-channel@claude-community` after `/plugin marketplace add anthropics/claude-plugins-community`.
+
+### Real-time push (the `<channel>` experience)
+
+The tools above are pull-based. For a peer's message to **land in Claude's context mid-turn, with no tool call** — the "Claude thinks with the mesh" experience the screenshots show — Claude Code has to load this plugin's *channel*, which is currently gated behind a flag while it awaits Anthropic's approved-channels allowlist:
+
+```
+claude --dangerously-load-development-channels plugin:sym-mesh-channel@sym-bot
+```
+
+The flag becomes unnecessary once the channel is allowlisted — tracked in [anthropics/claude-plugins-official#1512](https://github.com/anthropics/claude-plugins-official/issues/1512).
 
 ## What you get
 
@@ -321,12 +331,12 @@ Some corporate networks block mDNS multicast entirely — try a hotspot or home
 
 ### `<channel>` notifications never arrive even though peers are connected
 
-The published plugin loads the channel on its own. If `<channel>` notifications still don't arrive, real-time push may not yet be enabled on your account — as a fallback, launch Claude Code with the development-channels flag matching your install path:
+The 11 tools work without any flag. The real-time `<channel>` **push** is separate: Claude Code only delivers channel notifications for channels on its **approved-channels allowlist**, and sym-mesh-channel isn't on it yet — so push requires the development-channels flag matching your install path:
 
-- plugin install: `--dangerously-load-development-channels plugin:sym-mesh-channel@sym-mesh-channel`
+- plugin install: `--dangerously-load-development-channels plugin:sym-mesh-channel@sym-bot`
 - npm install: `--dangerously-load-development-channels server:claude-sym-mesh`
 
-The tools work regardless; only the async push surface may be gated. Status tracked in [anthropics/claude-plugins-official#1512](https://github.com/anthropics/claude-plugins-official/issues/1512).
+This is an Anthropic-side gate, not a bug here — once the channel is allowlisted the flag is no longer needed. Tracked in [anthropics/claude-plugins-official#1512](https://github.com/anthropics/claude-plugins-official/issues/1512).
 
 ### `sym_status` says "Relay: connected" when you didn't configure one
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sym-bot/mesh-channel",
-  "version": "0.3.8",
+  "version": "0.3.10",
   "description": "MCP server — real-time agent-to-agent cognition for Claude Code remote teams via the SYM mesh.",
   "main": "server.js",
   "bin": {

package/server.js

@@ -7,6 +7,25 @@ if (process.argv[2] === 'init') {
   return;
 }
 
+// ── stdout discipline (v0.3.9) ──────────────────────────────────────────────
+// MCP frames JSON-RPC on stdout. Any non-JSON write there — ours or, far more
+// often, a dependency's load banner (e.g. "[encoder] Semantic encoder ready"
+// from the semantic model) — corrupts the stream and makes Claude Code drop the
+// connection (-32000) or log "Ignoring non-JSON line on stdout". Guard it: lines
+// that look like JSON-RPC (start with '{') pass through to the real stdout;
+// everything else is redirected to stderr. Installed before any require so it
+// catches dependency output at load time.
+const __realStdoutWrite = process.stdout.write.bind(process.stdout);
+process.stdout.write = function (chunk, ...rest) {
+  try {
+    const s = typeof chunk === 'string' ? chunk : chunk.toString('utf8');
+    if (s.trimStart().startsWith('{')) return __realStdoutWrite(chunk, ...rest);
+    return process.stderr.write(chunk, ...rest);
+  } catch {
+    return __realStdoutWrite(chunk, ...rest);
+  }
+};
+
 /**
  * sym-mesh-channel — MCP server that makes Claude Code a peer node on the SYM mesh.
  *
@@ -192,7 +211,26 @@ function defaultNodeName() {
   }
   return `claude-${clean(require('os').hostname())}`;
 }
-const NODE_NAME = process.env.SYM_NODE_NAME || defaultNodeName();
+// Live-collision auto-suffix (v0.3.10): @sym-bot/sym already reclaims STALE locks
+// (dead holder), so crashed sessions self-heal. But two LIVE sessions wanting the
+// same name — a duplicate dev agent, or two sessions sharing a fixed SYM_NODE_NAME
+// — would hard-fail with EIDENTITYLOCK. Resolve the name up front: if the base is
+// held by a live process, append -2/-3/… so the second session coexists instead of
+// failing. A dead or absent holder keeps the base name (sym reclaims it on start).
+function resolveNodeName(base) {
+  const fs = require('fs'), os = require('os'), path = require('path');
+  const alive = (pid) => { try { process.kill(pid, 0); return true; } catch (e) { return e.code === 'EPERM'; } };
+  for (let i = 0; i < 64; i++) {
+    const name = i === 0 ? base : `${base}-${i + 1}`;
+    try {
+      const pid = parseInt(fs.readFileSync(path.join(os.homedir(), '.sym', 'nodes', name, 'lock.pid'), 'utf8').trim(), 10);
+      if (pid && alive(pid)) continue; // live holder → try the next suffix
+    } catch { /* no lock file → name is free */ }
+    return name; // free, or a stale lock sym will reclaim on start()
+  }
+  return base;
+}
+const NODE_NAME = resolveNodeName(process.env.SYM_NODE_NAME || defaultNodeName());
 
 // ── Mesh group (MMP §5.8) ──────────────────────────────────
 //