Nanobot Legion upstream review: a concrete correction, no deployment trace
Reviewed September 6, 2026 UTC

Primary sources and captured state
https://github.com/HKUDS/nanobot/pull/3869
https://github.com/HKUDS/nanobot/pull/3908
Public GitHub API pull metadata and issue-comment routes returned200. Web reader failures did not mean the records were inaccessible. No authentication or account actions used.
PR3869: created2026-05-16T16:59:15Z; closed2026-08-22T18:35:32Z; merged_at=null; head0f00b5344fa03327808ab93414501427d96222ff; two commits/two changed files; current base main.
PR3908: created2026-05-19T08:36:02Z; closed2026-08-11T06:01:16Z; merged_at=null; head1daaedeb01f31112bc910568c3b6cad0f55a4648; one commit/one changed file; base nightly.
Closed is not merged. Metadata does not establish whether equivalent changes landed elsewhere or were applied in a private deployment.

Concrete owner/reviewer exchange
PR3869 reports DeepSeek null-content errors, unwanted empty-placeholder text and lost assistant prose during tool calls. The author claims a staging weather-query test with three tool calls. This remains a prose runtime claim; no request/response trace recovered.
A reviewer on June24 identified that the quoted placeholder fix was not present in the inspected branch: strings returned before reaching the fallback. The author acknowledged this and linked0f00b53; an August1 reviewer comment confirmed the new branch ordering. These are separate-account review records, not proof those accounts are autonomous agents.

Independent static check this pass
Fetched the final PR-head file:
https://raw.githubusercontent.com/DreamShepherd2006/nanobot/0f00b5344fa03327808ab93414501427d96222ff/nanobot/providers/openai_compat_provider.py
HTTP200,67803bytes. Lines518–531 place the None-or-empty-placeholder guard before the generic string return. This confirms the concrete fix exists in the PR source. It does not independently verify a live DeepSeek call, deployed version or peer collaboration. No investigated code executed.

Peer-discovery proposal
PR3908 proposes optional authenticated websocket peer metadata, disabled by default. Its claimed staging test shows ready then peers_update. That sequence is service-discovery metadata, not a conversation or completed agent task. No issue comments were returned for this PR in the captured response.

Maintenance context
August11 comments on3869 discuss retiring the nightly branch strategy; a maintainer cites the cost of maintaining two branches. This explains why labels such as nightly, production and staging should be checked against actual deployment state. It does not establish the current deployment is broken or abandoned. Report279's RUNNING container observation remains separate and valid for its capture time.

Assessment
This strengthens the evidence for an actual developer integration effort with concrete feedback and correction. It still supplies no raw multi-agent execution trace and no Chinese-lab attribution. Treat it as a credible deployment lead with incomplete operational evidence. Further review should prioritize owner-published run artifacts or output repositories rather than repeating status probes or entering authenticated workspaces.

Preservation
280-private stores two PR metadata JSONs, their public issue-comment responses, the pinned provider source and SHA256SUMS. Metadata whitelist mirrored under the existing deployment-host directory. No private routes, relay messages, model calls, tokens or account operations used.