Hub relay mode: connect agents through a wire-mesh relay hub - #152
Merged
Merged
Conversation
A hub connection (wss URL) is a RELAY, not a coordinator: no connect_request or introduce approval applies. The session self-advert is forwarded by the hub to every other connected agent, and the hub answers with a catch-up of everyone already there, so peers discover each other purely through gossip. Messages ride relay-connect pairings via sendManageRequest targetDevice routing. Inbound relayed manage-requests are dispatched keyed by the SENDING device (request.fromDevice), never the hub itself, and replies ride respond() routing back. The integration test runs a real createRelayHub over local WebSockets and proves the full stack: two transports discover each other via the hub gossip and exchange a message through a relay pairing. Closes #151
Mearman
marked this pull request as ready for review
September 17, 2026 00:25
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
🎉 This PR is included in version 3.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #151.
The hub relay mode: a hub connection (e.g. wss://mesh.exadev.io/) is a RELAY, not a coordinator -- no connect_request/introduce approval applies. Discovery is pure gossip (the hub forwards each agent's self-advert and answers new connections with a catch-up of everyone already there), and messages ride relay-connect pairings via
sendManageRequest's owntargetDevicerouting.src/core/hub-session.ts--HubSession, owning the connection model (split from wire-mesh-transport.ts under the max-lines cap, the same collaborator pattern as connection-approval.ts and siblings).transport.hub-- public:connect(url),peers(),ownDeviceHex(),sendToPeer(deviceHex, message).request.fromDevice), never the hub itself; replies riderespond()'s own relay routing back.The integration test runs a real
createRelayHub-- the same domain logic the production mesh.exadev.io Durable Object runs -- served over local WebSockets, and proves the full stack: two real transports discover each other via the hub's gossip and exchange a message through a relay pairing.The earlier PR #150's fake-hub test remains valid: it pins the coordinator-approval protocol shape (connect_request answered manage-ok); this PR adds the relay shape (no approval at all).