Chat Channels

Connect PicoClaw to messaging platforms through its gateway mode.

picoclaw gateway

Supported Channels

Channel	Difficulty	Notes
Telegram	Easy	Recommended. Supports voice transcription with Groq.
Discord	Easy	Bot token + intents. Supports group trigger.
Slack	Easy	Socket mode, no public IP needed.
QQ	Easy	Official QQ bot API (AppID + AppSecret).
DingTalk	Medium	Stream mode, no public IP needed.
WeCom	Easy	Unified WebSocket-based WeCom integration via AI Bot API. QR login supported.
Feishu	Hard	Enterprise collaboration platform.
LINE	Hard	Webhook via shared gateway port.
OneBot	Medium	Compatible with NapCat/Go-CQHTTP.
Matrix	Easy	Open, decentralized protocol. Supports typing, placeholder, media.
WhatsApp	Medium	Bridge mode or native (whatsmeow).
MaixCam	Easy	Hardware-integrated AI camera.
VK	Easy	VKontakte community bot via Long Poll API.
Pico	Easy	Native WebSocket channel for custom clients.

How It Works

1. Configure one or more channels in ~/.picoclaw/config.json under the channels key
2. Set "enabled": true for each channel you want to use
3. Run picoclaw gateway to start listening
4. The gateway handles all channels concurrently

Access Control

All channels support the allow_from field to restrict access to specific users:

{
  "channels": {
    "telegram": {
      "enabled": true,
      "token": "YOUR_TOKEN",
      "allow_from": ["123456789"]
    }
  }
}

Set allow_from to an empty array [] to allow all users. You can also set allow_from: ["*"] to explicitly allow all users (a warning will be logged at startup).

Common Channel Fields

All channels support these optional fields:

Field	Description
reasoning_channel_id	Route reasoning/thinking output to a separate channel
group_trigger	Control bot behavior in group chats (mention-only, prefixes)

Shared Gateway

All webhook-based channels (LINE, DingTalk, etc.) share the single gateway HTTP server on port 18790. Per-channel webhook_host/webhook_port fields are no longer needed — just configure webhook_path to differentiate endpoints. WeCom now uses outbound WebSocket and does not require a public-facing webhook.

Log verbosity is controlled by gateway.log_level (default: warn). Supported values: debug, info, warn, error, fatal.