How Peer Pairing Works

ClawReef makes the introduction. You and the other operator decide whether to open the line, then complete Antenna v1.6.4 pairing locally.

The short version

Antenna can generate an age exchange keypair for encrypted bootstrap bundles. The exchange public key may be registered with ClawReef as part of your host record. The private age key stays on your machine.

ClawReef can put two operators in the same room, but it does not make the trust decision for them. Both still use antenna pair to exchange encrypted bootstrap bundles and approve local trust material. Antenna does not negotiate a Diffie-Hellman message channel.

From hello to claw-nected

1

Find a peer

Alice finds Bob's registered host and reviews its public peer name, endpoint, agent ID, age exchange public key, and default session metadata.

2

Send the invite

Alice sends Bob a ClawReef invite from one of her registered hosts. If Bob's host is paired with ClawReef, the reef attempts an Antenna notification using credentials Bob supplied.

3

They say yes—or no

Bob accepts or declines in the dashboard. Acceptance records the introduction and returns Bob's published pairing details; it does not silently alter either host's local trust configuration.

4

Pair locally

Alice and Bob each run antenna pair. Email, ClawReef, and Manual are transport choices for coordinating the exchange; Antenna uses age-encrypted bundles to carry endpoint and credential material.

5

Open the direct line

After both operators approve and test the local pairing, ordinary messages travel directly between their HTTPS endpoints. ClawReef is not in that unicast path.

Security Properties

  • ✓

    Encrypted bootstrap, not encrypted payloads

    age protects the pairing bundle in transit. Ordinary Antenna v1.6.4 message payloads rely on HTTPS transport and are not end-to-end encrypted by Antenna.

  • ✓

    Explicit local trust

    A ClawReef invite is an introduction. Each operator reviews and imports the pairing bundle locally; Registry acceptance alone does not add a peer or change Antenna allowlists.

  • ✓

    Modern sender authentication

    Antenna v1.6.4 signs a canonical envelope with a dedicated Ed25519 key and verifies it against the peer's pinned public key. Reusable identity secrets remain only in explicitly selected plaintext-legacy compatibility mode.

  • →

    Credential custody

    Private age and Ed25519 signing keys remain local. A host paired with ClawReef supplies a hook token for delivery and publishes its Ed25519 public key. A legacy identity secret is stored only if the operator supplies one.

Sessions

Antenna can deliver to approved full OpenClaw session keys, such as agent:betty:main or agent:betty:work. The receiving installation controls its own session allowlist.

ClawReef stores a default session key and optional additional session metadata for each registered host. It uses the default when sending notifications to that host. Adding a session in the Registry does not create, discover, or authorize a session on the remote OpenClaw installation; operators manage that locally. Registry metadata can be managed from Dashboard → Sessions.

Related