215 — AgentRob forum/robot bridge and two community-access leads Reviewed September 6, 2026 UTC. No investigated software executed. RESULT A Peking University-associated project explicitly designs robot agents to read and reply on a NodeBB forum. Two pinned client files implement the command-to-result loop and expose useful identifiers. No live forum address, public result post, or raw multi-agent execution was recovered. Two unrelated agent-marketplace leads remain access-limited. PRIMARY RESEARCH https://arxiv.org/abs/2602.13591 https://arxiv.org/html/2602.13591v1 Submitted February 14, 2026. AgentRob describes forum-mediated agents controlling Unitree robots and reporting results. The paper supports a Chinese university research connection, but a supported architecture is not proof of an exposed deployment. Its claimed metadata-based loop prevention cannot be verified from prose alone. PROJECT AND SOURCE https://github.com/PKULab1806/AgentRob The README identifies NodeBB and Volcengine/Doubao, while saying the MCP server and forum deployment are maintained separately. The recursive tree at 386f2d28e2f883262c8afa011c377ac8606e612c contains 11 entries and is non-truncated. go2_mcp_agent.py and g1_mcp_agent.py were downloaded and verified against Git blob hashes (73,408 and 70,503 bytes respectively). No install or execution. Pinned URLs: https://github.com/PKULab1806/AgentRob/blob/386f2d28e2f883262c8afa011c377ac8606e612c/go2_mcp_agent.py https://github.com/PKULab1806/AgentRob/blob/386f2d28e2f883262c8afa011c377ac8606e612c/g1_mcp_agent.py OBSERVED GO2 CLIENT LOGIC Default identity is go2-mcp-agent with display name Go2机器狗（MCP）. It recognizes @quadruped and @机器狗, fetches topic content when necessary, extracts a command, invokes the robot execution helper, summarizes the result, optionally uploads a result image, then calls reply_to_topic with topic ID and agent_id. G1 defaults to g1-mcp-agent. The Go2 processed-topic set is initialized in memory. In the inspected processing function it marks a topic before command extraction; a failed extraction leaves it marked, while a failed reply removes it for retry. Restart persistence was not established. Repeated or missing replies can therefore have application-level causes, without independent autonomous task planning. The function logs reply success and returns True after awaiting the client call, without validating a concrete post ID there. Consequently a success log alone needs checking against the client response and destination before being counted as an observed publication. The test-mode branch bypasses mention selection but the early return that would send only a canned test reply is commented out. Processing continues through command extraction/execution. Do not infer that a test-labelled invocation is inert; no invocation was made. The Go2 constructor uses literal placeholder API/model values despite accepting configuration arguments. This limits reproducibility of the published snapshot and prevents reading its README model label as runtime proof. NodeBB image-upload paths mentioned in comments are relative examples, not a recovered deployment address. No request to a robot, MCP service, authenticated forum or guessed endpoint was attempted. BOUNDED SEARCH Exact searches for go2-mcp-agent outside GitHub and the Go2 display name recovered no matching live forum post in returned results. AgentRob forum-address searches returned project publicity and the repository. This does not exclude unindexed or private operation. Preserve these fingerprints; seek a voluntarily public forum URL or task receipt before further attribution. OTHER COMMUNITY LEADS https://www.missraus.com/ Search results describe an agent task/credit-sharing marketplace. Direct homepage GET returned HTTP 200 with a 644-byte app shell naming /assets/main-B1qHpNxi.js. That referenced asset returned HTTP 403 to the tested direct request. No task, team or work output was retrieved; an empty shell is not a verified empty marketplace. https://www.skillscowork.com/forum Search results show agent-labelled forum discussions. Web retrieval failed and a direct request timed out. No live post body or work artifact was verified. These failures do not establish geographic blocking or prove a mainland machine will work. No new verified activity surface was added to the activity inventory on the strength of search snippets alone. NEXT AgentRob offers a distinctive forum/robot fingerprint, but prioritize finding its explicitly published forum destination over deeper implementation review. Missraus could benefit from a normal-browser comparison of the same public asset; avoid private API discovery. Continue searching other communities for public tasks with cross-site outputs. CAPTURES 215-private/: Missraus homepage, AgentRob tree and two Git-verified source files, access-observations.json and SHA256SUMS. No live credentials were acquired or used. Missing community captures reflect failed fetches, not stored successful pages.