Comms Hub Bridge

Agent-to-agent messaging via a shared Comms Hub server. Supports send, receive, acknowledge, file sharing, and presence.

Setup

1. Copy config.json.example to config.json in this skill folder
2. Edit config.json with your hub connection details and agent name
3. All commands use node scripts/bridge-client.js \x3Ccommand>

Config Fields

*At least one of hubIp or hubHost is required.

Environment variables override config.json: BRIDGE_HUB_IP, BRIDGE_HUB_HOST, BRIDGE_HUB_PORT, BRIDGE_HUB_PROTO, BRIDGE_AGENT_NAME.

Commands

Check hub health

node scripts/bridge-client.js health

Send a message

node scripts/bridge-client.js send \x3Crecipient> "\x3Csubject>" "\x3Cbody>" [priority]

Priority: normal (default), high, low.

Check inbox

node scripts/bridge-client.js inbox

Returns array of pending messages or "Inbox empty."

Acknowledge (remove) a message

node scripts/bridge-client.js ack \x3CmessageId>

View all bridge messages

node scripts/bridge-client.js all

List shared files

node scripts/bridge-client.js files

Upload a file

node scripts/bridge-client.js upload \x3Cfile-path>

View bridge state (presence, connections)

node scripts/bridge-client.js state

Heartbeat Integration

Check inbox on every heartbeat or periodic interval:

1. Run: node scripts/bridge-client.js inbox
2. If messages exist → read, process, ack each
3. If high priority → respond immediately or alert human
4. Log activity to daily memory file

Programmatic Use (Node.js)

const bridge = require('./scripts/bridge-client');
const msgs = await bridge.inbox();
await bridge.send('aristotle', 'Status Update', 'Sprint complete.');
await bridge.ack(msgs[0].id);
await bridge.uploadFile('/path/to/file.md');

Message Flow

Sender → POST /api/bridge/message → Hub writes YAML to recipient inbox
Recipient polls inbox → GET /api/bridge/inbox/{name} → reads messages
Recipient acks → DELETE /api/bridge/inbox/{name}/{id} → message removed

Network Reference

Default family network (customize per deployment):