WeCom Channel CLI Get started
Open source · WeCom channelsv0.4.2

Built for agents.
Designed for humans.

Connect your agents to the conversation.
Watch threads and channels. No public endpoint required.

Install the CLI Explore the interface
Open sourceSelf-hostedGo + JSONPublished
#
engineeringWeCom channel
AAlex Team member
@Assistant Can you summarize the release discussion?
A conversation becomes an event
channel / event.jsonWATCH
❯ wecom-channel-cli event watch --whole-channel
Structured. Scoped. Ready for your agent.UTF-8
Credentials stay with the broker
Awaiting review

A draft.
Your decision.

Approve the exact message
before it leaves the broker.

See the approval boundary
ILLUSTRATIVE FLOWreceive → inspect → propose → approve
A small interface.
A deliberate architecture.01 One channel per context02 Credentials off-agent03 Reviewed writes
THE INTERFACE, EXPLAINED

Every request has
a place to belong.

Switch contexts. Inspect the data. Try crossing a boundary. The rules live in the broker, outside the model’s decisions.

Context explorer
Local simulation
REQUEST / RESPONSEengineering/agent.sock
❯wecom-channel-cli --use-context engineering event list

  
Illustrative requests. No connection to a live channel.Explore every command 

 





 
ISOLATION BY DESIGN
#engineeringcontext 01
 agent.sock ledger
separate scope
#securitycontext 02
 agent.sock ledger
 Shared bot. Independent channel boundaries.

 
 INTENTIONALLY CONNECTED
Context is more
than a name.
Each channel gets its own policy, sockets, inbox, and approval ledger. Start with polling. React with native emoji. Keep writes under operator control.
  • 01
    The broker holds the credentials.
    Agents receive curated records with clear provenance.
  • 02
    The operator controls the send.
    Every proposal binds the exact target and action.
  • 03
    Uncertainty never becomes a retry.
    Interrupted writes wait for reconciliation.
Look inside the architecture 




Host isolation still matters. Run the agent with a separate identity and restricted filesystem, network, and tools. The CLI is one part of that boundary.
Security model ↗


 BUILT TO BE UNDERSTOOD
Go as deep as you need.
From the first command to the trust model.
The implementation has a paper trail.
START BUILDING
A clear path to
your first context.
Install the CLI, provision the broker,
and connect your agent.
Operator guide ↗FIND THE DETAILS
Every command.
Every flag.
A searchable reference generated
from the command tree.
Command reference ↗CHECK THE EVIDENCE
The protocol,
without the guesswork.
Official API sources, authentication
findings, and deliberate limits.
API research ↗


YOUR NEXT CONNECTION
Give your agent
a channel.
Start with bot credentials. Discover a channel.
Then configure its context.
Set up a channel 
INSTALL FROM NPM
npm install -g @angelmsger/wecom-channel-cli@0.4.2
wecom-channel-cli auth guide

wecom-channel-cli config get-contexts
wecom-channel-cli --use-context engineering event list
Configure a broker and context before reading events.
Node.js 20+ · Linux and macOS.