How does embedded chat decide which workflow to run?

It is bound when the channel is configured, rather than inferred per session at runtime, so a channel behaves predictably.

Do all message channels work out of the box?

No. Each depends on application configuration and approval on the other platform. See the documentation site for the steps.

Integrations and message channels

One workflow can be triggered from several places. This page lists the entry points that exist today and what each requires — planned capabilities are not listed here.

Web, H5 and PWA

The platform ships a web interface that works on desktop and mobile browsers and can be added to the home screen as a PWA. No client installation required.

Embedded chat

The chat interface can be embedded in your own pages, with a gateway mapping external apps, channels and sessions. Which workflow a channel runs is bound in the channel configuration.

CLI

The command-line entry point suits connecting to a workspace from a terminal, talking to an agent, and wiring runs into scripts.

Message channels

Channels such as WeCom and DingTalk can be connected. Each one needs an application and callback configured on that platform first, so check what that platform allows before planning around it.

Questions people ask

How does embedded chat decide which workflow to run?: It is bound when the channel is configured, rather than inferred per session at runtime, so a channel behaves predictably.
Do all message channels work out of the box?: No. Each depends on application configuration and approval on the other platform. See the documentation site for the steps.

Evidence for the claims on this page

Last verified: 2026-09-18

支持 MCP 的 Stdio、SSE 与 HTTP 三种传输方式。: Scope: ChengOS 平台侧 MCP 客户端。; Source: ChengOS MCP 传输实现 · 2026-09-18
ChengID / Hosted Coordinator 支持跨网络的用户与用户、用户与 Agent 通信。: Scope: 独立的服务器通信模式，不是局域网直连失败后的降级；不承担文件数据面。; Source: ChengApp Hosted Coordinator 实现 · 2026-09-18