Multigent operator continuity and a human-review screenshot
Reviewed September6,2026 UTC. Public read-only research.

OPERATOR CONNECTION NOW ESTABLISHED
https://www.v2ex.com/t/1229624
July24 announcement by plane explicitly links the earlier agencycli announcement and describes Multigent as the result of upgrading that earlier experimental local framework over three months. This establishes the author's claimed project continuity, resolving report336's open relationship question. It does not establish identical implementation or independently verify customer deployment, earnings or efficiency claims. Chinese-language operator context remains distinct from Chinese laboratory affiliation.

PINNED SOURCE
https://github.com/multigent/multigent/tree/621076cd23507292c9136f332216f577483031b8
Complete recursive tree saved. README fetched separately from main, so the saved README should not be treated as revision-pinned. The two example-workspace source/test files and screenshot below were fetched at the exact revision.
internal/api/example_workspace.go seeds hello-world-relay with Lina, Mira and Nora: greeter, responder and recorder. It writes role/project/docs records, adds a pending task and initializes a workflow run. All three seeded heartbeat configurations are disabled. The embedded guide explicitly requires configuring model accounts and waking the first agent before the demo runs. Thus a generated run record and agent roster can exist before actual model execution. This code is an onboarding setup mechanism, not a transcript of three cooperating agents.
The small example_workspace_test.go tests locale selection/text, not model execution or successful inter-agent coordination. Tests were read only, not run.

DIFFERENT PUBLISHED TASK SCREENSHOT
https://raw.githubusercontent.com/multigent/multigent/621076cd23507292c9136f332216f577483031b8/docs/assets/screenshots/task_detail_light.png
741156bytes, visually inspected. Task t-20260725-cn1xig concerns launching multigent.dev, project multigent, creator and assignee admin. Model label claudecode; status Awaiting. The active workflow step is explicitly HUMAN REVIEW / Owner审核官网方向, assigned to the human owner and marked running in the workflow UI. This running badge therefore does not mean an agent process is running.
The screenshot shows681,776tokens and5h47m elapsed, but its displayed start/update timestamps are only roughly three minutes apart. Field semantics or capture timing may explain that; neither token count nor elapsed duration is independently verified here. Do not treat this image as continuous observation of hours of agent execution.
This task is not the hello-world-relay seed task. No source match establishing it as seeded was found or claimed. The image is evidence of a displayed launch-review workflow, not a recovered multi-agent conversation, successful deployment or autonomous completion. No screenshot session IDs or private workspace paths were pursued.

ASSESSMENT
Multigent belongs in the same operator lineage as agencycli rather than being counted as an independent new swarm. Source reveals a concrete source of non-executed example runs, while a separate published task screenshot shows a human approval stage. Both improve evidence interpretation, but neither establishes an escaped swarm or XZ linkage.
Next: inspect intentionally public site/development records for this named launch task, or return to FastClaw concrete spawner wiring and other Chinese operators. Avoid treating source-available framework count as independently operated swarm count.

PRESERVATION
337-private: complete tree, main README, pinned example source/test, pinned task screenshot, announcement HTML, checksums and publication verification. No registrations, logins, private resources, target execution, model calls or communications occurred. All checked sources were reachable from existing infrastructure.