Channels Overview

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

Platform	Protocol	Status	Notes
Telegram	Bot API (polling/webhook)	Stable	Recommended starting point
Discord	Gateway + REST API	Stable	Supports servers and DMs
WhatsApp	WhatsApp Web bridge	Beta	Requires QR code pairing
Slack	Slack App (Events API)	Stable	Workspace install required
Signal	signal-cli (D-Bus)	Beta	Requires linked device
iMessage	macOS Messages.app	Alpha	macOS only

Adding a Channel

argent channels add <platform>

The CLI wizard walks you through platform-specific setup (API tokens, bot creation, etc.) and writes the configuration to your 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 under channels in your argent.json:

{
  "channels": {
    "telegram": {
      "enabled": true,
      "token": "your-bot-token"
    },
    "discord": {
      "enabled": true,
      "token": "your-bot-token",
      "intents": ["GUILDS", "GUILD_MESSAGES", "DIRECT_MESSAGES"]
    }
  }
}

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.

See Channel Pairing for how ArgentOS links platform users to agent sessions.