agent-comms 8.11.0 → 8.13.0

package/.claude-plugin/marketplace.json

@@ -15,7 +15,7 @@
         "source": "url",
         "url": "https://github.com/ExaDev/agent-comms.git"
       },
-      "version": "8.11.0"
+      "version": "8.13.0"
     }
   ]
 }

package/.claude-plugin/plugin.json

@@ -18,5 +18,5 @@
   },
   "name": "agent-comms",
   "repository": "https://github.com/ExaDev/agent-comms",
-  "version": "8.11.0"
+  "version": "8.13.0"
 }

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 ExaDev
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -2,7 +2,7 @@
 
 [![GitHub](https://img.shields.io/badge/GitHub-181717?logo=github&logoColor=white)](https://github.com/ExaDev/agent-comms)
 [![npm](https://img.shields.io/badge/npm-CB3837?logo=npm&logoColor=white)](https://www.npmjs.com/package/agent-comms)
-[![version](https://img.shields.io/badge/version-8.11.0-blue)](https://github.com/ExaDev/agent-comms/releases/tag/v8.11.0)
+[![version](https://img.shields.io/badge/version-8.13.0-blue)](https://github.com/ExaDev/agent-comms/releases/tag/v8.13.0)
 [![CI](https://img.shields.io/github/actions/workflow/status/ExaDev/agent-comms/ci.yml?branch=main)](https://github.com/ExaDev/agent-comms/actions)
 
 Cross-harness communication mesh for LLM agents: rooms, DMs, presence, and visibility over TCP with zero filesystem dependencies.
@@ -453,7 +453,7 @@ Every bridge answers SIGTERM, SIGINT and SIGHUP by marking its own agent offline
 
 ## Gateway trust and connection codes
 
-Every store holds its own session on the relay hub (`wss://mesh.exadev.io/` by default), each Claude Code session the default cc-peer front handles included, and dials it again with a growing delay whenever the hub drops it. Being reachable from another machine therefore does not depend on which store holds the local coordinator role, and a coordinator handover leaves every other store's hub session alone. A store holds a session only while it has an agent that is not a ghost and its machine trusts at least one remote device, principal or machine, so before that nothing of it reaches the hub, not even its device id. A visible agent advertises itself, its presence and its hosted rooms; a hidden agent advertises only its device id, which is what lets it be reached by that id.
+Every store holds its own session on the relay hub (`wss://mesh.exadev.io/` by default; set `AGENT_COMMS_HUB_URL` to a `ws://` or `wss://` URL to use a self-hosted one instead, such as a node started with `npx wire-mesh`), each Claude Code session the default cc-peer front handles included, and dials it again with a growing delay whenever the hub drops it. Being reachable from another machine therefore does not depend on which store holds the local coordinator role, and a coordinator handover leaves every other store's hub session alone. A store holds a session only while it has an agent that is not a ghost and its machine trusts at least one remote device, principal or machine, so before that nothing of it reaches the hub, not even its device id. A visible agent advertises itself, its presence and its hosted rooms; a hidden agent advertises only its device id, which is what lets it be reached by that id.
 
 The hub is a set rather than one address. A store holds its one hub session over the relay it ranks highest: a relay served on its own machine, then a relay on the local network offered by a trusted device, then any trusted device offering relay service, then the configured hub as the fallback. A direct connection to a device always beats every relay, since a request to a directly connected device never touches the hub session at all. A relay whose dial fails, or which drops the session, is passed over for about a minute before it is tried again.
 
@@ -461,7 +461,7 @@ The store holding its machine's elected coordinator role serves the relay role w
 
 The relay takes the connection of its own hub session as its uplink and fronts its clients over it, so a store behind its machine's relay stays reachable by devices that reach it only through the configured hub, and can reach them, each end seen under its own device-id rather than the relay's. An advert for one of the relay's own clients that comes back round through the hub never displaces the client's registration, and a device that has only just moved onto the relay is routable once its first advert has been accepted, which can take until its next gossip.
 
-A device known only through the hub, not directly connected to this mesh, is reported at whatever presence its last gossiped advert carried. Nothing tells the rest of the mesh when such a device disconnects, so `list_agents` stops trusting a stale advert and reports the device offline once it has gone unrefreshed for a few re-advertise intervals, rather than showing it active indefinitely.
+A device known only through the hub, not directly connected to this mesh, is reported at whatever presence its last gossiped advert carried. Its working directory, rooms and tags list as not shared, since the hub session carries only the summary; a bridge this machine has chosen to trust is asked for them directly, over the end-to-end session the two already have, and `list_agents` shows what came back from the next listing on. The ask is refused unless the answering bridge also trusts the asker, so the details never travel to a device the operator has not pinned. Nothing tells the rest of the mesh when such a device disconnects, so `list_agents` stops trusting a stale advert and reports the device offline once it has gone unrefreshed for a few re-advertise intervals, rather than showing it active indefinitely.
 
 Two devices on different machines can only relay traffic through each other's hub once each side explicitly trusts the other's device-id — a deny-by-default, pin-the-key model with no directory lookup, deliberately mirroring how an ordinary peer connection is already pinned.