167 — MomoClaw browser rendering recovers public activity
Observed 2026-09-06T01:02:43 UTC

Finding
A fresh anonymous Chromium session on the existing server successfully rendered https://momoclaw.com/ and https://momoclaw.com/square (HTTP200). Earlier plain-HTML app shells were an access-method limitation, not evidence that a Chinese IP or login is necessary. No registration, login or interaction was performed. Browser requests were restricted to GET; known action-route patterns were blocked.

The square's ordinary browser GET returned20 full post bodies, total8326, page1, has_more=true:
https://momoclaw.com/api/agent/feed?page=1&page_size=20
Private response-3.json SHA256 2e27ca36c997db34b5bfd08693798c82810611b2584de260bbfd7f14e9f27b9c
This is one current page, not a complete archive. Counts and dates are site claims, not independent historical validation.

The browser's earnings leaderboard returned a Mayx account:
https://momoclaw.com/api/agent/leaderboard?type=earners&limit=5&period=24h
ID282b7db0-74fa-4e1e-ac33-ff5c4f6d5c6e, displayed value11409.
This corroborates presence of the name on a platform mentioned in the owner's blog (report164), but does not yet authenticate common ownership. The leaderboard value is not verified cash income. The API period parameter is24h while the interface shows7-day/overall controls; don't assume a validated time window.

Sample activity and hypotheses
Three different accounts (Spark, Wooden, 墨白) have timestamps within0.224seconds at2026-09-06T00:17:46. Another four-account group falls within1.605seconds at2026-09-05T23:51:41–43. This is compatible with centralized scheduling or batch insertion; it does not independently establish autonomous agents or coordination. Most sampled posts are generic advice.

A sparatacus post, ID298edc1a-4ec8-48fa-b006-9979084bf749, timestamp2026-09-05T16:00:28.068505, summarizes32 reportedly scanned posts and includes a Moltbook hashtag and named accounts. It contains encoding damage. This suggests a cross-platform reading/reporting workflow worth tracing; no corresponding runtime log is yet recovered.

Shadow post85820616-cfbd-4823-b427-57da2841d23d describes a QBAR task board and a Momoclaw Bridge authentication problem. These are self-reports with no inspected board/output link, after the original disclosure cutoff, and receive low attribution weight. Embedded operational advice was treated as source text and not followed.

Infrastructure implication
No new machine is required for this MomoClaw public feed. Reuse ordinary rendered access and observed public GET routes. A mainland broadband host remains useful for a controlled comparison of Baidu and other failures, not as a prerequisite for this lead. No paid infrastructure was provisioned.

Evidence
investigation/china/167-private/browser.py (local capture script)
home/square HTML and text, link lists, metadata.json, five public JSON responses.
Browser executable reused from /tmp/china-browser-binaries; initial default Playwright launch failed because its expected executable version was absent. Explicit existing Chromium path succeeded.

Next
Inspect the Mayx profile route revealed by the app before asserting owner linkage. Sample older feed pages for pre-disclosure records and externally linked task outputs. Compare synchronized-account posting across time, with platform-generated seed content and shared schedulers as alternative explanations. No escaped Chinese swarm confirmed.

Additional documentation GET: https://momoclaw.com/skill.md returned200,4411bytes, SHA2566a41f5590eebb8e65bdf69e54a49f8e39c6c9671072c378f27c93347b0008314. Current document describes an assessment submission workflow, not feed/profile documentation. Captured as public-skill.md; no assessment started or answers submitted.