225 — Feishu debate guide: human relay qualification and feature-request closure
Reviewed September 6, 2026 UTC.

GUIDE AND SCREENSHOT
https://datawhalechina.github.io/hello-claw/cn/university/group-debate/
The introduction promises autonomous discussion among three isolated OpenClaw bots. Section 3.7 instead says bot messages do not trigger peers' receive events, describes a plugin conflict, and recommends human relaying. Section 4 explicitly shows a human forwarding each turn. Later advice again describes automatic relay. Treat this as internally inconsistent documentation, not a verified autonomous deployment.
The linked chat screenshot shows one human member, three bots, a human addressing everyone, a three-reply indicator and one visible product-role response. It does not show a multi-round bot-to-bot chain or completed consensus. The illustrative dialogue in the article is not a raw run transcript.
Image source: https://datawhalechina.github.io/hello-claw/assets/lark-group-chat.BpWnVOZv.jpg

RELATED PRIMARY ISSUE
https://github.com/openclaw/openclaw/issues/43563
Created March 12, 2026; currently closed, closed_at May 10. The reporter describes five Feishu bot accounts on an Azure VM and proposes synthetic cross-bot events with a turn limit. That environment is a reporter claim, not provider/operator attribution evidence.
The two public comments include a stale notice and an April 27 response directing the feature to plugins/community scope. The latter explicitly says no patch is proposed. Closure therefore does not establish that the relay was implemented or merged. The review comment's assertions about source and an existing skill were not independently verified here; it supplies no inspected runtime receipt.

ASSESSMENT
This is another concrete case where an autonomous-sounding title overstates what the accompanying evidence establishes. A screenshot of several bot identities responding to a human is compatible with independent replies; it does not prove peer-triggered execution. The issue provides a specific proposed transport mechanism, but neither source supplies a joined send/receive trace from an actual run.
Do not generalize this documentation's limitations into a claim that all Feishu agent coordination is impossible today. External relays could exist, and the guide does not pin a tested implementation version. Investigate particular public implementations and their evidence.

NEXT
Search the explicitly named community relay and its public development history for actual run artifacts. Prefer a bot-originated send plus a matching peer receipt/task output. No need to obtain private group access or deploy a new bot merely to assess this public evidence.

CAPTURES
225-private/page.html, chat.jpg (viewed), issue43563.json and comments43563.json; SHA256SUMS preserved. Screenshot remains private; only reviewed description published. All requests read-only; no prompts/configuration instructions from the investigated guide were followed and no plugin was installed.