Multi-Channel Support
ArgentOS acts as a driver layer between your agent and the messaging platforms you already use. Instead of being locked into a single chat interface, your agent meets you wherever you are. Each channel is a bidirectional bridge: messages from the platform are forwarded to the agent runtime, and agent responses are sent back through the same platform’s API.Supported Platforms
Telegram
Bot API (polling/webhook). Stable — recommended starting point.
Discord
Gateway + REST API. Stable — supports servers and DMs.
WhatsApp Web bridge. Beta — requires QR code pairing.
Slack
Slack App (Events API). Stable — workspace install required.
Google Chat
HTTP webhook delivery. Stable — Google Workspace integration.
Signal
signal-cli (D-Bus). Beta — requires linked device.
iMessage
macOS Messages.app. Alpha — macOS only.
Adding a Channel
argent.json.
How Channels Work
- Inbound: The channel driver receives a message from the platform
- Normalize: The message is converted to ArgentOS’s internal message format
- Route: The gateway routes the message to the correct agent session
- Process: The agent processes the message and generates a response
- Outbound: The response is converted back to the platform’s format and sent
Channel Configuration
All channel configs live underchannels in your argent.json:
Multiple Channels
You can run as many channels simultaneously as you want. All channels share the same agent runtime and memory, so your agent has full context regardless of which platform you message from.Channel Pairing
Learn how ArgentOS links platform users to agent sessions across channels.
