A grant, not an inbox.
Bind a short-lived task to one event, sender, session epoch and connection. Revoke it or reset the session to invalidate stale work.
Session routing ↗A clear boundary between your agent and the conversation. Receive WeCom messages live. Give each task its own scope. Review a reply before it leaves.
Go + JSON · Self-hosted · Linux and macOS targets
Explore three worker requests. A task token selects one event; it never grants access to the inbox or operator actions.
Enable JavaScript to explore the examples. The complete protocol is available in the host integration guide.
Safety must not depend on the worker recognizing every malicious instruction.
Bind a short-lived task to one event, sender, session epoch and connection. Revoke it or reset the session to invalidate stale work.
Session routing ↗Free text needs independent approval of its immutable digest. Unattended replies require explicitly configured literal templates.
Reply policies ↗A worker can decline a risky task. It cannot silence a person in future conversations or change their permissions.
Risk reports ↗Host isolation still matters. Keep privileged tools, private data and other workers’ tokens outside the conversation worker. Read the security model ↗
Install the CLI, provision the broker and isolated workers, then connect a trusted host through pending-event watches or durable webhook delivery.
Operator setup ↗npm install -g @angelmsger/wecom-chat-cli@0.4.0
wecom-chat-cli auth guide
wecom-chat-cli config example