XiaPost: concrete collaboration request, but no recovered joint build
Reviewed 2026-09-06 UTC

Finding
New public Chinese agent-community surface: https://xiapost.com/ . A specific game-development request supplies a better trail than generic agent-swаrm advertising, but the inspected posts do not establish completed collaboration, autonomous authorship, or Chinese-lab attribution.

Primary evidence
https://xiapost.com/post/k8t2ib45
Profile 秉珠 #q47v9m, site timestamp 2026-07-29 05:25:21 UTC, asks other agents to build/test a Cocos Creator WeChat H5 idle game. It claims research, economic simulation, database/API design and TypeScript core code are complete, but its 1.9 GB RAM host cannot run the build/browser tests. This detail is the poster's claim, not a verified hardware measurement. Detail page shows zero comments.

https://xiapost.com/agents/q47v9m
Three visible posts: the first request, a shorter request at 05:27:27, and a development document at 05:41:23 on July29. Similar wording alone does not authenticate an automated publisher.

https://xiapost.com/post/g4zxur7y
The development document has one visible reply, by 司空谷 at 2026-08-05 10:34:26 UTC. It asks whether the stated package-size restriction was empirically tested. No answer, build artifact or testing receipt is displayed. This is a real visible cross-profile exchange, not evidence the requested work happened. Business statistics and platform limits in the post were not independently checked.

Workspace limitation
The text calls LikeClawByOpenCode/workspace/cuibingzhu/idle_game/ a GitHub location. Interpreting its first two components as owner/repository, unauthenticated GET https://api.github.com/repos/LikeClawByOpenCode/workspace returned404. Public repository listing https://api.github.com/users/LikeClawByOpenCode/repos?per_page=100 also returned404. This could be an incorrect/local path, renamed/deleted/private location or inaccurate claim; the response cannot distinguish these. No private workspace was pursued.

Mechanism / alternate explanation
https://xiapost.com/skill.md is public documentation (v2.0.0), reviewed as data and not installed. It explicitly prescribes daily 09:00 dashboard visits and subsequent actions, with date state in memory/xiapost-state.json. It describes posting/commenting APIs and an optional caller-supplied model-name header. Thus recurring participation has a published owner-installable mechanism, while model labels are self-reported. No credentials or registration were used. This is not evidence of a training agent escaping its intended environment.

Discovery / coverage
https://xiapost.com/circles/gd2ito supplied the lead. Its direct HTML included September3 content while the web-reader cached version was older. The header displayed zero discussions despite visible posts; counters should not be used as a completeness measure. Only this circle and the named profile/posts/documentation were examined, not the full community.

Next useful checks
Follow other concrete project posts and their public deliverables; inspect the replying profile's ordinary public activity for exact artifact links. Search the unusual workspace token and game title on independent public indexes. A missing GitHub location is an unresolved join, not a reason to infer a hidden swarm.

Infrastructure
All these XiaPost pages and GitHub responses were accessible from the existing server. This lead needs artifact provenance, not extra compute. For other blocked Chinese sources, an owned mainland broadband machine with SSH and a dedicated browser is the most useful comparison point: suggested 2 CPU cores, 4 GB RAM, 40-70 GB disk, no GPU. Browser exports of public pages also help. A small Hong Kong VPS is an optional comparison, not guaranteed mainland-equivalent access. Alibaba's current documentation explicitly distinguishes mainland and international routing:
https://www.alibabacloud.com/help/en/simple-application-server/product-overview/regions-and-network-connectivity
No new price quote or purchase was made. Compare identical URLs and meaningful page content before scaling.

Preservation
Raw captures: investigation/china/260-private/{circle.html,collaboration.txt,profile.txt,document.txt,skill.txt,repo.txt,github-user.txt}; SHA256SUMS covers these captures. Public mirror contains reviewed metadata only. No site mutations or investigated code execution.