185 — Agents Radar: generated digest joined to a public bot post
Updated 2026-09-06 UTC

Conclusion
A Chinese/English news-digest project provides a concrete publication chain: a dated committed report, a matching GitHub issue authored by github-actions[bot], and code that explains the transformation between them. The inspected program is a scheduled collection/summarization/publication pipeline. Parallel model calls do not establish an independently coordinating swarm. This is a useful known-publication example and discovery source, not a confirmed escaped actor.

Source and preservation
https://github.com/duanyytop/agents-radar
Default branch is master; an initial assumed main-tree request returned404, then repository metadata resolved the branch. Repository metadata reports creation February23,2026.
Pinned full tree: d097a2e4ae12ff3407aec4c67b426b185d40bfb9, 3,501 entries, nontruncated.
Private evidence: investigation/china/185-private/.
Four retrieved files match the tree's Git blob hashes:
.github/workflows/daily-digest.yml — 4,730 bytes
src/index.ts — 23,769 bytes
src/github.ts — 15,450 bytes
digests/2026-07-16/ai-arxiv.md — 11,285 bytes
No investigated code or workflow was run. Only public GET requests were used.

Observed publication
https://github.com/duanyytop/agents-radar/issues/2158
GitHub API metadata records creation 2026-07-16T01:32:55Z by github-actions[bot]. The body is a Chinese AI research digest.
https://github.com/duanyytop/agents-radar/blob/d097a2e4ae12ff3407aec4c67b426b185d40bfb9/digests/2026-07-16/ai-arxiv.md
API path history lists commit fbaac1032ec7ea2babf0e223372e61b6b7722c54 at 2026-07-16T01:33:30Z, with the daily-digest commit message. Thus the recorded issue creation precedes the matching file commit by35 seconds.
The issue body has6,549 characters; file text has6,548. They become exactly equal after deleting U+200B zero-width space from the issue body. The current src/github.ts neutralizeGitHubRefs function inserts precisely this character into github.com links to suppress unwanted references. createGitHubIssue applies that function before sending the issue-creation request. This is stronger evidence than matching report titles alone.

Mechanism and limits
Current src/index.ts collects source data, calls summarization functions in parallel, generates English reports, translates to Chinese, and saves/publishes results. Current workflow has cron37 22 * * * and runs pnpm start, then commits outputs; this is present configuration, not proof of the exact July schedule or historical runtime version. No credentials or secret values were read.
The code explains public posting as a programmed output stage. There is no need to infer that the model itself chose GitHub as improvised memory. This pass did not inspect every source file or all hosted Actions logs, and does not authenticate which model served the sampled historical run.
Chinese content and owner namespace do not prove Chinese-lab ownership. The GitHub bot identity establishes the publishing account; it is not a unique underlying agent identity.

Research consequence
Treat these digests as leads pointing to original projects and papers, not independent corroboration of the claims they summarize. The verified zero-width-character transformation also shows why exact byte comparisons across public surfaces can miss an otherwise identical output. Normalize only documented transformations and preserve the originals.
Next: follow linked projects with concrete role histories or output repositories. Avoid confusing news articles about agents with posts authored by an unexplained agent fleet.