WeCom WorkBuddy Interface — HW-Bot-WB¶
Live status of the WorkBuddy ↔ WeCom posting channel. Decision record: ADR-0004.
HW-Bot-WB (B1 — live)¶
| Property | Value |
|---|---|
| Role | Primary WorkBuddy ↔ WeCom interface |
| Driven by | WorkBuddy via wecom-cli |
| Knowledge set | None (session context only) |
| Messaging permission | Granted 2026-09-27 |
| Groups | Dept: Software 软件工程 (joined 2026-09-27) |
Posting pipeline (proven 2026-09-27)¶
- Group invite (one-time, WeCom UI: 群设置 → 群机器人).
wecom-cli message aibot sessions list— group appears after recent traffic.- Match group by name; copy the target from the current listing.
wecom-cli message aibot sendwith markdown content (20 KB limit; bold/bullets/italics render —#headers do not).
Automation: the post-to-wecom-group skill wraps this flow, with a
known-groups shorthand table ("Software group" → Dept: Software 软件工程).
Bot roster¶
| # | Bot | Purpose | Status |
|---|---|---|---|
| B1 | HW-Bot-WB | Posting agent (primary interface) | Live |
| B2 | OVES Product Expert | Product Q&A (ADR-0001/0002) | Design |
| B3 | Software Dept Assistant | Dev conventions, ADR index | Proposed |
| B4 | Africa Ops Assistant | TZ rollout, swap pricing | Proposed |
| B5 | Trading Desk Assistant | DP framework (sensitivity TBD) | Proposed |
Quota: 20 bots per member / 300 per company.
KB upload workflow¶
Single-instruction knowledge upload: "Upload these [files] as [Bot]'s KB" (omitted bot = all company bots). Spec: KB → Bot Upload Workflow.
Open questions¶
- Multi-bot management from WorkBuddy (per ADR-0004): per-bot CLI authorization vs WorkBuddy-as-single-brain with API-mode frontends.
- B5 sensitivity decision before creation.