Skip to main content
PicoClaw supports multiple chat platforms so you can interact with your AI assistant wherever you prefer. All channels use a shared Gateway server architecture for efficient resource usage.

​
Supported Channels

PicoClaw integrates with the following chat platforms:
ChannelSetup DifficultyFeatures
TelegramEasyBot token only, recommended for beginners
DiscordEasyBot token + intents configuration
WhatsAppEasyQR code scan or bridge URL
QQEasyAppID + AppSecret from QQ Open Platform
DingTalkMediumApp credentials required
LINEMediumWebhook URL + credentials
WeComMediumMultiple integration options available

​
Gateway Server Architecture

All webhook-based channels share a single HTTP Gateway server that listens on gateway.host:gateway.port (default 127.0.0.1:18790). This unified architecture provides:
  • Resource Efficiency: Single server handles all webhook channels
  • Simplified Configuration: No per-channel port management
  • Easy Deployment: One gateway process for all integrations
Telegram, Discord, WhatsApp (native), and QQ use polling/WebSocket connections and don’t require webhook configuration. LINE and WeCom use webhooks served on the shared Gateway port.

​
Starting the Gateway

To enable chat channels, start the Gateway server: 
picoclaw gateway
The Gateway will:
  1. Load channel configurations from ~/.picoclaw/config.json
  2. Start enabled channels automatically
  3. Handle incoming messages from all platforms
  4. Route responses back to users

​
Setup Comparison

ChannelAuthenticationNetwork RequirementsGroup Chat Support
TelegramBot token from @BotFatherOutbound HTTPS✅ Yes
DiscordBot token + intentsOutbound WebSocket✅ Yes (configurable)
WhatsAppQR code or bridgeDepends on mode✅ Yes
QQAppID + AppSecretOutbound HTTPS✅ Yes
DingTalkClient ID + SecretOutbound HTTPS✅ Yes
LINEChannel credentialsInbound HTTPS webhook✅ Yes (@mention)
WeComToken + AES keyInbound HTTPS webhook✅ Yes (varies by mode)

​
Access Control

All channels support allow_from configuration to restrict who can interact with your bot: 
{
  "channels": {
    "telegram": {
      "enabled": true,
      "token": "YOUR_BOT_TOKEN",
      "allow_from": ["123456789"]
    }
  }
}
  • Empty array []: Allow all users (public bot)
  • With IDs: Only specified users can interact
  • User ID format: Varies by platform (numeric for Telegram/QQ, string for Discord/LINE)

​
Quick Start Recommendations

​
First Time Setup

If you’re new to PicoClaw, we recommend starting with Telegram:
1

Create bot with @BotFather

Takes less than 2 minutes, no technical configuration needed
2

Add token to config

Single token field, no webhook or server setup required
3

Start gateway

Run picoclaw gateway and start chatting

​
For Enterprise

If you’re deploying in a corporate environment:

​
Configuration Location

All channel configurations are stored in ~/.picoclaw/config.json under the channels section: 
{
  "gateway": {
    "host": "127.0.0.1",
    "port": 18790
  },
  "channels": {
    "telegram": { "enabled": false },
    "discord": { "enabled": false },
    "whatsapp": { "enabled": false },
    "qq": { "enabled": false },
    "dingtalk": { "enabled": false },
    "line": { "enabled": false },
    "wecom": { "enabled": false }
  }
}

​
Next Steps

Choose a channel to get started:

Telegram

Easiest setup, recommended for beginners

Discord

Popular for communities and teams

WhatsApp

Native integration or bridge mode

QQ

Popular in China, easy setup

DingTalk

Enterprise messaging for businesses

LINE

Popular in Japan and Southeast Asia

WeCom

Enterprise WeChat with multiple modes

Build docs developers (and LLMs) love

Get started for freeTalk to us