FastClaw
Feature · Channels

Put your AI agent in every chat app your users already use

Bind any FastClaw agent to Telegram, Discord, Slack, Feishu, WeCom, WeChat, WhatsApp, LINE or iMessage — with per-chat session isolation and owner pairing.

01

Nine IM channels, one agent

Telegram, Discord, Slack, Feishu, WeCom, WeChat, WhatsApp, LINE and iMessage. Attach as many as you like to the same agent.

02

QR-code connect

WeChat, Feishu, WeCom and WhatsApp connect by scanning a QR code from the console — no developer portal round-trips.

03

Isolated sessions

Every channel + chat ID gets its own session, so a user’s Telegram thread and Discord thread never bleed into each other.

04

Owner pairing

Send /pair <code> from your own account to claim the bot. Only the paired owner gets host access; everyone else is a guest.

05

Tokens checked before save

Telegram getMe, Discord /users/@me and Slack auth.test run before a token is stored, so a typo never ships a dead bot.

06

Scales past one pod

Turn on Redis and channel leases plus a shared message stream keep exactly one replica answering each bot.

localhost:18953/console/agents/…/channels
Put your AI agent in every chat app your users already use

How it works

Open an agent in the console, go to Channels, and pick a platform. Token-based bots (Telegram, Discord, Slack, LINE) take a token that FastClaw validates before saving. QR-based channels (WeChat, Feishu, WeCom, WhatsApp) connect by scanning a code. iMessage answers direct messages to the Mac FastClaw runs on.

Once connected, send /pair <code> from your own account. Until a channel is paired it replies with a "not paired" notice and routes nothing to the agent.

One agent, many front doors

The agent behind a channel is the same agent you chat with on the web: same personality and memory, same skills, same model. Replies can include images and files, and long answers are split into several messages where the platform allows it.

Sessions are keyed by channel and chat, so group chats, DMs and different platforms each keep their own history. In groups, agents reply when they are mentioned.

Built for real traffic

On a single machine nothing extra is needed. When you run several replicas, set FASTCLAW_REDIS_ADDR: channel leases guarantee one replica owns each bot connection, and a Redis stream carries inbound and outbound messages between pods.

Frequently asked questions

Try it on your own agents

Start free in FastClaw Cloud, or self-host the single binary in a minute.