All docs / Applications + support

Reference applications

AgentNet CLI, Beagle desktop, beagle-web, Beagle Chat for iOS and Android, and the browser extension — and which SDK each one is built on.

These applications run on the live Decent Network today. Each one is built on the SDKs documented on this site, so they are the best place to see what a finished integration looks like — and to test your own app against: a peer you build can friend and message any of them.

Source links are given only where the repository is public.

At a glance

ApplicationWhat it isBuilt onGet itSource
AgentNet CLIMachine-side private network: agentnet daemon, CLI/TUI, local consolelan, peer, peer-webrtc, doranpm install -g @decentnetwork/lannot public yet
Beagle desktop + CLIChat, files and calls for people on macOS, Linux and Windowsbeagle, beagle-ui, peer, peer-webrtc, chat-components, lannpm install -g @decentnetwork/beaglenot public yet
beagle-webBeagle in a browser tab — no install, no registrationpeer (running in the browser), beagle-uiapp.beagle.chatnot public yet
Beagle Chat for iOSThe iOS messaging appCarrier native SDK (as an xcframework), iOS WebRTC SDKbeagle.chatnot public yet
Beagle Chat for AndroidThe Android messaging appAndroid Carrier SDK, Android WebRTC SDKbeagle.chatnot public yet
Beagle Chat browser extensionBeagle in the browser side panel, for Chrome and Firefoxpeer, beagle-uiChrome Web Store · Firefox Add-onsnot public yet
OpenClaw Beagle ChannelGives an OpenClaw agent its own Beagle address, DMs and groupsCarrier native SDK (C++ sidecar)see sourcedecentnetworks/openclaw-beagle-channel
agent-meshMessaging between Claude Code, Codex and other agents across machinespeersee source0xli/decent-agent-mesh

AgentNet CLI

@decentnetwork/lan installs the agentnet command (also available as decentlan). It runs a daemon that owns a Carrier identity, joins the network through @decentnetwork/peer, and adds a private 10.86.x.x network with names from Dora, service ACLs, file handoff and a local web console. Its call support uses @decentnetwork/peer-webrtc.

Use it as a reference for: running a long-lived peer as a system service, mapping friend relationships to network access, and handing a peer's identity to other local processes. Full documentation: /docs/lan.

Beagle desktop + CLI

@decentnetwork/beagle is the Beagle Chat client for computers: a beagle command that serves the chat UI locally and runs the peer either embedded or through a running AgentNet daemon. The UI is the @decentnetwork/beagle-ui bundle; interactive forms in chat use @decentnetwork/chat-components. No admin privilege is needed.

Use it as a reference for: a complete chat client on the Node SDKs — friends, presence, messages, files, groups and calls. Documentation: /docs/beagle.

beagle-web

app.beagle.chat runs a full Carrier peer inside a browser tab. The keypair is generated in the browser and stays there; the same identity can be exported to the desktop app. It hosts the same beagle-ui bundle as the desktop, and reaches the network over WebSockets.

Use it as a reference for: running @decentnetwork/peer in a browser, and for Sign in with Beagle from a website.

Beagle Chat for iOS and Android

The mobile apps talk to the same network and the same friends as the desktop and web clients.

Install links for both are on beagle.chat.

Beagle Chat browser extension

The extension runs @decentnetwork/peer in the browser and shows the beagle-ui chat in the side panel; one instance serves the whole browser profile. It is published for Chrome and Firefox.

OpenClaw Beagle Channel

decentnetworks/openclaw-beagle-channel has two parts: beagle-sidecar, a C++ daemon linked against the Carrier native SDK that owns the agent's Carrier identity and exposes a local HTTP API, and beagle-channel, a TypeScript OpenClaw plugin that maps Beagle DMs and groups to OpenClaw channel sessions. It is the reference for wrapping the native SDK in a local service.

agent-mesh

0xli/decent-agent-mesh is a skill for Claude Code, Codex and other file-capable agents. One daemon built on @decentnetwork/peer keeps the agent's identity and a warm inbox; agents use a mesh CLI and plain inbox/outbox files. It is the smallest complete example of a peer-based application with a friend handshake.