Channels Overview
ChemAgent supports multiple messaging channels. The Web console is enabled by default and can run in parallel with other configured channels, while workspace, memory, knowledge, modes, and tool policy remain consistent.
Capability matrix
| Channel | Text | Image | File | Voice | Group chat |
|---|---|---|---|---|---|
| ✓ | ✓ | ✓ | ✓ | ||
| Web Console | ✓ | ✓ | ✓ | ✓ | |
| Feishu | ✓ | ✓ | ✓ | ✓ | ✓ |
| DingTalk | ✓ | ✓ | ✓ | ✓ | ✓ |
| WeCom Bot | ✓ | ✓ | ✓ | ✓ | ✓ |
| ✓ | ✓ | ✓ | ✓ | ||
| WeCom App | ✓ | ✓ | ✓ | ✓ | |
| Official Account | ✓ | ✓ | ✓ | ||
| WeChat Customer Service | ✓ | ✓ | ✓ | ✓ | |
| Telegram | ✓ | ✓ | ✓ | ✓ | ✓ |
| Slack | ✓ | ✓ | ✓ | ✓ | |
| Discord | ✓ | ✓ | ✓ | ✓ |
Connection models
The Web console provides conversation and administration without an external messaging account.
Feishu, WeCom Bot, QQ, Telegram, Slack, and Discord can operate without a public callback address in their documented modes.
WeCom App, Official Account, and WeChat Customer Service require a correctly protected public callback.
The Channels console supports adding, configuring, activating, monitoring, and disconnecting connectors.
Message behaviour
- ✓Media depends on two layers
The connector must support the message type and the selected model must support the required understanding or generation capability.
- ✓Group triggers vary
Mentions, replies, privacy modes, and bot visibility follow platform-specific rules.
- ✓Sessions remain isolated
Sender and group identifiers are mapped into channel sessions without merging unrelated conversation state.
- ✓Delivery limits vary
File size, supported formats, streaming presentation, and rate limits are controlled by each platform.
Consistent agent policy
The same deployment policy, workspace boundary, memory, knowledge, mode, and review requirements apply regardless of where a request originates. Credentials and callback keys remain private deployment data.