This release is a pre-release and may not be stable for production use.
aidev-wxbot-plugin
A WeChat bot plugin for bkaidev platform.
Description
This plugin provides WeChat bot functionality for the bkaidev platform, enabling automated message handling and responses.
Features
- WeChat message callback handling
- Automated message processing
- Integration with bkaidev platform
Installation
pip install aidev_wxbot
Usage
Configure the plugin in your bkaidev platform and set up the WeChat bot callback URL.
Agent work is submitted to the shared Bkplugin executor, which supports 16 active tasks by default and queues up to 32
additional tasks across channels. A single-chat sender or group chat may only have one reply in flight: while one is generating,
further requests are rejected with a terminal response, and the active run is never cancelled implicitly. The
rejection tells the sender to send /stop only when the running reply is their own — /stop and /new act on the
sender alone, since each group member keeps a separate conversation (the platform derives session_code from the
username). Different conversations still execute concurrently. Long-connection Chat requests use the
SDK retry strategy for model rate limits without changing the legacy HTTP callback strategy. The default stream
timeout is 600 seconds so an in-progress retry can finish. Override BKAPP_AIDEV_AGENT_MAX_WORKERS,
BKAPP_AIDEV_AGENT_MAX_PENDING, and BKAPP_WXAIBOT_WS_STREAM_TIMEOUT_SEC when the deployment's upstream Agent or
database capacity requires different limits. Stream cleanup runs in a separate Bkplugin-owned bounded executor
(2 workers and 32 pending tasks by default); override BKAPP_AIDEV_AGENT_CLEANUP_MAX_WORKERS and
BKAPP_AIDEV_AGENT_CLEANUP_MAX_PENDING only when upstream cleanup behavior requires it. Health logs expose generation
and cleanup executor usage, drain timeouts/rejections, and busy-rejected counts for capacity verification.
Session commands and Ask-user interactions
Both WebSocket and HTTP callback/polling support /title 新标题 (1–255 characters on one line) and /web
(the current session's AI 小鲸 link). They look up the existing local thread and user-scoped platform session;
neither command starts an Agent run, creates a session, nor rotates or refreshes the local thread.
Title changes send only session_name to the platform and require a matching response before reporting success.
Missing/inaccessible sessions or missing Web configuration produce an explicit message. Group commands require an @mention.
WebSocket Ask-user output retains the full questions and option descriptions in chat, with A/B/C option prefixes
and single-/multiple-choice hints. Replies such as 1A；2B；3AC remain ordinary text delivered unchanged to the LLM;
only native card submissions send structured resume[].payload.answers after identity/session/interrupt validation.
| Questions in one Ask-user interrupt | WebSocket presentation |
|---|---|
| One single-choice or multiple-choice question, 1–20 options | Native voting card, plus full text |
| Two or three questions, all single-choice, 1–10 options each | One native multi-selector card, plus full text |
| More than three questions | Text only, with numbered questions and lettered options |
| Multiple questions containing multiple-choice, free text, or option counts beyond the native schema | Text only |
Only the official card schema limits native rendering.
Title/option text lengths are display recommendations: no local byte-length rejection or truncation is applied.
The three-selector bound is specific to multiple_interaction, not the conversation. Each selector accepts a
single selection; the schema has no mixed single-/multiple-choice form. Such a form falls back without changing
the requested answer semantics. Voting cards have one checkbox question with a single-/multiple-choice mode.
Selectors contain only the original options, without a synthetic placeholder taking up the tenth slot. They
use WeCom's native first-option default; answers are submitted only after the user presses the submit button.
After an accepted native submission, the click callback replaces the question card with a result notice: the original task ID and title remain, choices and the submit button are removed, and clicking opens only the original AI 小鲸 session. The notice shows the server-validated answers, with every selected label for multiple-choice answers and numbered questions for multiple questions. A duplicate click does not display its new selections as accepted answers. This requires a configured session URL and a reply within the callback's five-second window. Missing URLs or update failures do not block the accepted answer's resume output; old cards are not proactively updated in the background. Ordinary text replies do not trigger this card replacement.
HTTP polling is not feature-equivalent to WebSocket: its current chat consumer does not render approval/Ask-user
interrupt outcomes, and template-card callbacks are not dispatched to the resume handlers. It also reads the old
run_id spelling instead of AG-UI runId. These gaps are covered by strict expected-failure tests; successful ordinary
text/command tests do not imply that HTTP interactive cards work. The callback tests use real encryption/decryption with
synthetic credentials and an in-memory queue, not a live WeCom endpoint or RabbitMQ instance.
WebSocket tracing
With the existing Agent OpenTelemetry integration enabled, each inbound message starts an independent
wxbot.message.receive trace. This short intake span ends after dispatch; the child
wxbot.long_connection.session span stays open while consuming Agent output and awaiting reply/card acknowledgments.
Context is propagated through asynchronous tasks and explicitly copied into the bounded Agent and cleanup executors.
No OpenTelemetry dependency or exporter is required to keep message processing operational.
| Span | Operation |
|---|---|
wxbot.message.receive / wxbot.message.prepare |
Receive and prepare an inbound message |
wxbot.identity.convert_to_rtx |
Convert the sender identity; wxbot.identity.fallback indicates fallback |
wxbot.agent.stream |
Execute/consume Agent output within the message trace |
wxbot.approval_card.build |
Inspect the terminal approval event; wxbot.approval.pending indicates a card was built |
wxbot.reply_stream / wxbot.approval_card.send |
Await stream/card sends, reconnect waits and retries |
wxbot.message.reply / wxbot.message.welcome |
Send non-stream replies |
wxbot.approval.cancel / wxbot.approval_card.update |
Process an approval cancellation and update the card |
wxbot.channel_config.fetch / wxbot.connection.connect |
Fetch channel configuration and establish the initial connection |
Platform identity/configuration requests carry W3C trace headers. Send spans expose wecom.send.attempts,
wecom.send.retries, wecom.disconnected_wait_ms, and successful wecom.ack.errcode=0 / wecom.ack.received=true.
Retry events and failed spans record only error types and numeric acknowledgment error codes, never message bodies,
usernames, card URLs, tokens or raw exception messages/stacks. A successful acknowledgment is not proof that the
client displayed the card. wxbot_message_received, wxbot_ws_stream_started, and approval-card result/retry logs
include trace_id for correlation. For log-only export, the existing aidev_otel_span event exposes span names,
parent IDs, status and duration; detailed attributes/events are available through the trace exporter.
License
MIT License
1 maintainer
Metadata
1 maintainer
Release files for aidev-wxbot 2.2.2rc49
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| aidev_wxbot-2.2.2rc49.tar.gz | 351.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aidev_wxbot-2.2.2rc49-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 456.8 kB
Release files / aidev_wxbot-2.2.2rc49.tar.gz
| Download URL | aidev_wxbot-2.2.2rc49.tar.gz |
|---|---|
| Size | 351.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bab0add2a27dbf2a1e7949026e92cb00305b2d2b21226bf639139d3d7c29985a
|
|
BLAKE2b-256 checksum How to use checksums |
9218179b9c17bda0d1c8dc50301cbf8a56defc8524d389d7f9b5b8cb587dcdf9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.6 {"installer":{"name":"uv","version":"0.11.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"11","id":"bullseye","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / aidev_wxbot-2.2.2rc49-py3-none-any.whl
| Download URL | aidev_wxbot-2.2.2rc49-py3-none-any.whl |
|---|---|
| Size | 104.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3138765923aa22f9d5b82bb280158a33d0c5a801ca60a972e103cd5d98841940
|
|
BLAKE2b-256 checksum How to use checksums |
20a31bcfbc2d1e60a7fe374caa08d731e59e1e6076bc5fc4b34c8aa82adbe3fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.6 {"installer":{"name":"uv","version":"0.11.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"11","id":"bullseye","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
