212 — Chinese Discord team screenshot and a separate Hermes loop incident Reviewed September 6, 2026 UTC. Public, read-only evidence review. RESULT A March-dated Chinese forum post includes a readable Discord screenshot of role-labelled coordination around a server-maintenance task. It is stronger than a product description but shows a plan awaiting human action, not completed autonomous work. Separately, a Hermes bug report supplies a timestamped two-profile acknowledgement loop; Chinese affiliation is not established for that deployment. Neither establishes an escaped Chinese-lab swarm. CHINESE FIRST-PERSON THREAD AND SCREENSHOT https://linux.do/t/topic/1754871/18 https://linux.do/t/topic/1754871/20 March 14–18 thread compares bot channels. Post 18 claims firsthand bot-to-bot use and supplies a Discord screenshot. It shows a team-discussion channel and an APP-labelled participant addressing another named persona. They discuss a recurring server-maintenance job, acknowledge agreement, and wait for the human to register an Azure application. The upper speaker header is cropped, so two separately authenticated bot identities cannot be counted from this image alone. No dated raw log, deployed script, completion receipt or model identifier is visible. The screenshot also contains an account address: keep the original private and do not republish that address. Post 20 describes firsthand Slack/Discord mention-routing experiments and a manual-thread workaround. Other replies disagree about Telegram; treat their platform claims as dated anecdotes, not verified current behavior. Qwen appears in the opening post's separate setup for a friend, not as proof of the screenshot's models. Screenshot URL: https://cdn3.ldstatic.com/original/4X/7/5/1/7514c344dbb0960f483b152d8f3a2b221b42b638.png Image fetched successfully and visually inspected; web-tool image fetch initially failed. Original capture: 522,675 bytes. Site dates and screenshots are publisher-supplied, not independent historical archives. SECOND CHINESE OPERATOR ACCOUNT https://linux.do/t/topic/2050998/12 April 25 reply describes multiple roles separated by Feishu groups/session IDs, later migrated from OpenClaw to Hermes. It claims the migration bypassed the old messaging path and left little communication during execution of fixed tasks. No linked run artifact was recovered. This cautions against equating many roles with an actively collaborating swarm. HERMES LOOP: PRIMARY REPORT FOUND https://github.com/NousResearch/hermes-agent/issues/32791 Created May 26, 2026 at 19:57:36 UTC. The operator reports thirteen profiles and a May 26 09:18 EDT loop between Ghost/default and Syn/syn. Seven selected timestamped messages span 09:18:55–09:19:23 and repeatedly acknowledge unchanged state. A human stop request at 09:19:38 allegedly did not stop replies; the operator says host intervention was required. Version claimed: Hermes 0.14.0 (2026.5.16), macOS, Discord. These are issue-body excerpts selected by the reporter, not the full gateway log; logs were offered on request but not published in the inspected body/comments. No request for private logs was sent. CAUSAL DISPUTE AND CLOSURE Two comments were retrieved. A May 26 clarification notes that the adapter had changed since the reported version; its HTML contains an autocontrib worker marker, so do not assume that comment was manually authored. The June 28 closing comment says bot-to-bot operation is unsupported, disputes the proposed guard-bypass cause on then-current main, and instead attributes recurrence to Discord reply auto-mentions satisfying the opt-in bot filter. It says proposed PR 33985 was also closed. We did not verify that PR or execute a reproduction. Closure is not proof of a shipped circuit breaker. Distinguish the observed-loop claim from the disputed explanation. DISCOVERY CORRECTION https://github.com/duanyytop/agents-radar/issues/1311 The Chinese OpenClaw ecosystem digest links this incident to NousResearch/hermes-agent, not openclaw/openclaw. The latter repository's 32791 is an unrelated Groq reasoning-parameter pull request. Report 211 called it an OpenClaw issue based on discovery metadata; that wording is corrected. This was a repository-attribution mistake during our triage, not a demonstrated bad link in the digest. Digest language is not evidence that the incident operator is Chinese. HERMES STUDIO FOLLOW-UP https://github.com/EKKOLearnAI/hermes-studio/issues/1547 Created June 14 at 06:08:50 UTC; open with four comments at capture. Requests configurable room/agent automatic replies and mutual-mention permission. Comments through August 18 ask for progress. The body says mutual mentions are unavailable while quoting routing code that permits certain agent replies under a depth cap. This tension calls for version/reproduction evidence; a feature request alone does not prove absent code, a deployed fix, or an operational swarm. No new raw dialogue recovered here. NEXT INVESTIGATION The Chinese Discord screenshot is an actual public visual artifact worth retaining as a comparison example. Seek other voluntarily published team dialogues with uncropped speakers, timestamps, model requests and linked task outputs. Search role/channel and task descriptions rather than attributing all Chinese-labelled bots to Chinese models. The Hermes incident supplies a concrete non-Chinese-attributed control example of how ordinary configured bot loops can look swarm-like. CAPTURES 212-private contains six GitHub API responses, the privately retained screenshot, and SHA256SUMS. Forum text was inspected through web retrieval; full forum HTML was not locally mirrored. No account registration, messages, credential use, or investigated code execution occurred.