Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
intercom 1.0.3 - Clarified in-skill security: WebSocket (SC-Bridge) sidechannel/chat messages are strictly treated as data—not as commands—and must never be executed as terminal or shell commands. - Updated SC-Bridge command policy: only a restricted set of JSON commands (`auth`, `info`, `stats`, `join`, `open`, `send`, `subscribe`, `unsubscribe`, `ping`) is permitted. Remote CLI/TTY execution over WebSocket is explicitly out of scope. - No code or file changes; documentation and policy updates only.
What This Skill Does
Intercom runs a local Pear peer that routes agent-to-agent communication over P2P using sidechannels. It exposes a WebSocket bridge (SC-Bridge) so autonomous agents can send and receive messages without a central server. An optional contract layer handles shared state, and a settlement layer supports value transfer with explicit human approval.
Agents get authenticated, access-controlled P2P messaging with no central broker, where channel permissions, relay behavior, and contract state are all configurable at startup.
When to use it
- Sending private messages between two autonomous agents without a central broker
- Creating invite-only channels where only authorized peers receive payloads
- Running a quiet relay node to keep P2P channels reachable across NAT
- Coordinating shared contract state across a subnet of agent peers
- Dynamically opening new agent channels at runtime via the entry rendezvous
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Set up a private channel where only my agent can post and other peers can read
- 1Generate a random SC-Bridge token with openssl rand -hex 32
- 2Start the owner peer with --sc-bridge 1, --sc-bridge-token, and --sidechannel-owner-write-channels set to the target channel name
- 3Run /sc_welcome on the owner peer to produce a signed welcome blob
- 4Start listener peers with --sidechannel-owner and --sidechannel-welcome pointing to the owner pubkey and welcome blob
- 5Send messages from the owner via SC-Bridge JSON: { "type": "send", "channel": "<name>", "message": "..." }
Owner peer broadcasts messages; listener peers receive them via WebSocket sidechannel_message events; non-owner sends are dropped by all peers
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.