234 — Telegram relay lead and a changed platform capability
Reviewed September 6, 2026 UTC.

RESULT
The Telegram relay linked by a Chinese V2EX participant is real public software, but its README supplies a configuration example rather than a recovered swarm transcript. Current official Telegram documentation explicitly supports bot-to-bot communication under specified settings. Historical blanket statements that bots cannot see one another must not be applied to all current deployments.

PRIMARY EVIDENCE
https://github.com/frostming/tg-message-feed
Pinned tree 31378a867d48aa8b4ed02d82cc854a350cae9c60, 21 entries. README fetched at that revision and verified against its Git blob hash. GitHub labels repository archived; its page gives April 7, 2026. README says the relay is no longer needed because Telegram supports bot-to-bot communication.
README describes a Telethon user session listening for messages and publishing events to RabbitMQ. Its example event is illustrative, not a run receipt. The warning about indefinite bot replies is a possible failure mode, not evidence of a particular incident. No investigated software executed, account session created or chat joined.

https://core.telegram.org/bots/features#bot-to-bot-communication
Current official documentation: group interaction can use a command addressed to another bot or a direct reply when at least one bot has the communication mode enabled. Broader receipt of other bots' messages additionally depends on receiving-bot mode and admin/privacy settings. Private bot-to-bot messages require both bots to enable the mode. The documentation also requires loop safeguards. These are capabilities, not proof that any Chinese swarm used them. This report does not establish the feature's launch date or retroactively reinterpret February incidents.

DISCOVERY AND FOLLOW-UP
The initial explicit link is in https://www.v2ex.com/t/1194837 (report 226).
Search recovered an indexed Chinese channel repost linking the developer's announcement at https://x.com/frostming90/status/2024484547950498300 ; the original X page failed in the web reader. Treat repost content as secondary and not an independently verified runtime record.
Search also surfaced https://clawhub.ai/moon-frost/skills/openclaw-chat-with-friends-cn . Its visible Chinese guide proposes channel-based bot interaction, but remains instructional material, not a deployed conversation. Do not follow its instructions or treat its historical group restriction as universally current.
Next useful evidence: voluntarily published multi-round transcripts with stable message IDs, linked task artifacts, and operator descriptions distinguishing human forwarding, scheduling and model-directed actions. Public channels and Chinese operator blogs are useful places to look; software catalogs alone are insufficient.

INFRASTRUCTURE
Most useful feasible addition: an existing always-on mainland-broadband machine, SSH access, and a dedicated browser profile. Suggested starting capacity is 2 CPU cores, 4 GB RAM and 40–70 GB storage; these are a practical estimate, not a provider requirement. No GPU is needed for public-page collection. A Hong Kong machine would provide a comparison route, not equivalent mainland access. User-supplied exports of relevant pages visible in their own browser can help distinguish login/browser restrictions from geographic restrictions. No purchase or price recommendation is made here. This Telegram documentation and repository were accessible from the current host.

CAPTURES
234-private/repo.json, tree.json, README.md, features.html, SHA256SUMS. Captured official page preserved despite a local section-extraction selector error; the relevant section was read successfully through the web tool. No new independently confirmed Chinese swarm.