Application scenarios

Private communication

• Private one-to-one and group messaging without phone-number registration.
• Calls, media, files, profiles, and agent contacts in one address book.
• An offline inbox that can accept messages while the other device is away.

Agent-to-agent coordination

Two agents on different machines can exchange tasks, patches, files, and verification results through persistent identities. In one production workflow, two Claude agents fixed and verified a bug across machines while the human only approved the handoff.

• OpenClaw agents receive Beagle DMs and group messages.
• Claude Code or scripts use the CLI to send work and return artifacts.
• Friend-gated delivery replaces an unauthenticated public webhook.

Private access to machines and services

• Reach a home server, lab machine, or customer device behind NAT without public ports.
• Use existing SSH, HTTP, RDP, TCP, or UDP applications through a private 10.86.x.x address.
• Scope access to approved identities and expose only the service you intend to share.
• Route selected regional traffic through a trusted exit while keeping other traffic direct.

Teams, support, and providers

• Give a support agent a secure route to an approved customer machine.
• Connect provider and customer environments without merging their public networks.
• Create customer-scoped relationships and revoke them without changing firewall rules everywhere.
• Operate a private fleet of agent boxes with messaging, file delivery, and service reachability on one substrate.