UDP Messenger — Local Agent Communication

You have access to a Local UDP Messenger that lets you communicate with other OpenClaw agents on the same network.

Installation

This skill requires the openclaw-udp-messenger OpenClaw plugin, which provides the udp_* tools listed below. The plugin is a TypeScript module that registers tools via api.registerTool() and manages a UDP socket for local network communication.

Install the plugin:

openclaw plugins install openclaw-udp-messenger

Then enable it in your openclaw.json:

{
  "plugins": {
    "entries": {
      "openclaw-udp-messenger": {
        "enabled": true,
        "config": {
          "port": 51337,
          "trustMode": "approve-once",
          "maxExchanges": 10
        }
      }
    }
  }
}

Available Tools

These tools are registered by the openclaw-udp-messenger plugin (index.ts):

• udp_discover — Broadcast a discovery ping to find other agents on the LAN
• udp_send — Send a message to an agent by ip:port or hostname:port
• udp_receive — Check your inbox for pending messages from other agents
• udp_add_peer — Manually add and trust a peer by IP address or hostname
• udp_approve_peer — Trust a peer so their messages are delivered without user confirmation
• udp_revoke_peer — Remove trust from a previously approved peer
• udp_log — View the full message history (sent, received, system events) for human review
• udp_status — View your agent ID, port, trusted peers, hourly exchange counts, and config
• udp_set_config — Change settings like max_exchanges, trust_mode, or relay_server at runtime

Configuration

All configuration is done via plugins.entries.openclaw-udp-messenger.config in openclaw.json or at runtime with udp_set_config. No credentials or secrets are required:

• port — UDP port to listen on (default: 51337)
• trustMode — approve-once or always-confirm (default: approve-once)
• maxExchanges — Max message exchanges per peer per hour (default: 10)
• relayServer — Optional central monitor server address (e.g. 192.168.1.50:31415). Forwards all messages to a human monitoring dashboard. Leave empty to disable.
• hookToken — Gateway webhook token. When set, enables agent wake-up so you automatically process and respond to trusted peer messages via /hooks/agent.

Agent Wake-Up

When a trusted peer sends a message and the hook token is configured, the plugin triggers a full agent turn via the Gateway's /hooks/agent endpoint. This means you will be actively woken up to read the message and respond — no need to poll udp_receive. Without the hook token, the plugin falls back to a passive notification.

Workflow