From d12c233378bd0401d42179eb758876f84a5e09d0 Mon Sep 17 00:00:00 2001
From: Teknium <127238744+teknium1@users.noreply.github.com>
Date: Thu, 4 Jun 2026 05:57:01 -0700
Subject: [PATCH] docs(wecom): stop implying live streaming and typing support
 (#38990)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The WeCom adapter delivers each response as a single complete message
via aibot_respond_msg / aibot_send_msg — it does not stream tokens
incrementally (no edit_message override) and send_typing is a no-op.
Reword the 'Reply-mode streaming' feature bullet to 'Reply correlation',
retitle the section to 'Reply-Mode Responses', and add a note clarifying
that neither token streaming nor typing indicators are supported.
---
 website/docs/user-guide/messaging/wecom.md | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/website/docs/user-guide/messaging/wecom.md b/website/docs/user-guide/messaging/wecom.md
index aa98b6b30..2ac5bddb1 100644
--- a/website/docs/user-guide/messaging/wecom.md
+++ b/website/docs/user-guide/messaging/wecom.md
@@ -92,9 +92,16 @@ hermes gateway
 - **AES-encrypted media** — automatic decryption for inbound attachments
 - **Quote context** — preserves reply threading
 - **Markdown rendering** — rich text responses
-- **Reply-mode streaming** — correlates responses to inbound message context
+- **Reply correlation** — responses are correlated to the inbound message context
 - **Auto-reconnect** — exponential backoff on connection drops
 
+:::note Streaming and typing indicators
+The WeCom adapter delivers each response as a single complete message — it does
+**not** stream responses token-by-token, and it does **not** show a typing
+indicator. "Reply correlation" (below) only threads a response to its inbound
+request; it is not live streaming.
+:::
+
 ## Configuration Options
 
 Set these in `config.yaml` under `platforms.wecom.extra`:
@@ -226,11 +233,11 @@ No configuration is needed — decryption happens transparently when encrypted m
 
 Files exceeding the absolute 20 MB limit are rejected with an informational message sent to the chat.
 
-## Reply-Mode Stream Responses
+## Reply-Mode Responses
 
-When the bot receives a message via the WeCom callback, the adapter remembers the inbound request ID. If a response is sent while the request context is still active, the adapter uses WeCom's reply-mode (`aibot_respond_msg`) with streaming to correlate the response directly to the inbound message. This provides a more natural conversation experience in the WeCom client.
+When the bot receives a message via the WeCom callback, the adapter remembers the inbound request ID. If a response is sent while the request context is still active, the adapter uses WeCom's reply-mode (`aibot_respond_msg`) to correlate the response directly to the inbound message. This provides a more natural conversation experience in the WeCom client.
 
-If the inbound request context has expired or is unavailable, the adapter falls back to proactive message sending via `aibot_send_msg`.
+The full response is delivered as a single message — the adapter does not stream tokens incrementally. If the inbound request context has expired or is unavailable, the adapter falls back to proactive message sending via `aibot_send_msg`.
 
 Reply-mode also works for media: uploaded media can be sent as a reply to the originating message.